Just bought a MT chateau lte7. (has LTE, wifi, 5 eth)
I thought: default config is probably running dhcp on wifi and ethernet ports. (also suggested by quickstart text).
But on ethernet my PC’s don’t get an IP address. On Wifi they do. I have no clue why not. Also winbox with MAC address over ETH has issues. One moment it seemed working, but when I disabled wifi on the PC with winbox, to make sure it was indeed over ETH, connection got lost.
(so over wifi I can connect, I can configure etc, I can configure LTE and get LTE network access, but ethernet ports: I don’t get them working)
Updated routeros to 7.22.2.
Factory reset done already more than 10 times.
Bottom line: I have no clue why this is not working. Default config has wifi and eth interfaces all on the one and only default bridge. Routeros DHCP working fine on the wifi interface.
/queue type
add fq-codel-ecn=no kind=fq-codel name=fq-codel-ethernet-default
/queue interface
set ether1 queue=fq-codel-ethernet-default
set ether2 queue=fq-codel-ethernet-default
set ether3 queue=fq-codel-ethernet-default
set ether4 queue=fq-codel-ethernet-default
set ether5 queue=fq-codel-ethernet-default
Is that default config ?
It also happens to be the difference between ethernet (included on interface queue) and wireless ports (not included), since otherwise all ports should be connected to bridge.
And the wireless ports do work as expected.
Tried the offbridge config on ether5 as suggested by jaclaz (but just the minimum for MAC winbox, no DHCP because I think mac should work fine, right?): but still no winbox connect on ether5. Discovery works, the device is listed, but on connect Winbox says ERR: Could not connect, MacConnection syn timeout.
(good suggestion anyhow, I should do this on my Mikrotik Hex as well in order to have access at all times)
Tried then to change ether5 queue settings to default (in which case the config shows it as queue=default), and also to hardware-only queue type (in which case the config shows it as removed from queue settings, as in attached config)
Same issue: cannot connect winbox via eth5. Wireshark shows that RouterOS sends MNDP messages, and the Winbox tries to initiate MAC-Telnet protocol. But RouterOS doesn't respond to MAC-Telnet.
Then I tried to set fixed IP on eth5 and on the PC connected to it. Still no Winbox connection. On wireshark the behaviour is different: no ARP response, but maybe I made a mistake in configuring IP. (this last test is not in the attached config)
Some questions I have:
Is it supposed to work at all? Anybody in the forum who has a Chateau LTE7?
Are there detailed logs possible in routerOS that could help me?
Of course other suggestions welcome, preferably based on a working theory of what could be wrong.
Spent many hours trying to understand what was happening, and … it turned out that the following hardware setup has problems (no DHCP, no winbox on L2, …):
my laptop ↔ USB-C ethernet dongle ↔ UTP cable ↔ Chateau eth port
Whereas:
adding an ethernet switch in between the setup: all is working fine.
using a laptop with built-in ethernet: all is working fine.
Anybody who can explain why an ethernet dongle triggers these problems?
Setting eth speed fixed to 100Mbps on both sides and the dongle works with the Chateau, putting back to auto/negotation and the link has problems even though it's reported as “OK”. Seems OS independent, same problem happens on windows/linux/mac laptop.
I have been punished for being cheap on eth-usb dongles (< 5 euro), haha.
Maybe that dongle is a 100 Mbit one that suffers from delusions of grandeur and believes to be a Gbit one .
But don't be too harsh against these low cost devices.
Anecdotally, a few years ago I setup for a friend a workaround to connect his (smart) TV and some other stuff related to his modem (only a few meters away but with a very thick stone wall between the router and the TV) through a couple powerline adapters and - I don't remember the exact details - there was one of those USB to ethernet adapters involved.
I got all the stuff from a "reliable" local shop, the adapter labeled 1 Gb.
There was no way to have that stuff work reliably.
My suspects were on the powerline adapters, so I got another couple of them (reknown brand) but same issues.
I had by pure chance a no-name/no-brand/el-cheapo 100 Mb adapter that I had bought on Aliexpress only to reach the minimum for free shipping, so I must have paid it less than or around 2 Euro, and out of disperation I used it in that setup and lo and behold everything started working just fine (and continued working for at least a couple of years.
.