- no mtu change possible
- no interface queue listed in winbox but present in CLI
regards
Ros
no interface queue listed in winbox but present in CLI
- this is already known.
It was mentioned here:
http://forum.mikrotik.com/t/7-0beta3-available-in-testing/134139/1
Winbox does not show all features, use CLI for most functionality
the moment I add an EoIP interface to a fresh installed CHR it boots and keeps rebooting for ever.
It reaches the login prompt and in 1 second it reboots.
I tried to install from scratch and add with only the remote ip address removing also the allow fast path option but same results
version used 7.0beta3 using the raw image
I had v7beta2 installed on a CHR and had only ether1 interface connected to our LAN.
When I updated to v7beta3 via system->packages->check for updates (development channel) it updated OK but after this update a new bridge1 was created with IP address 192.168.88.1/24.
Please do not perform such magic reconfiguration unless it is a fresh install or a “reset to defaults”!
In the past there also often was such magic addition of a DHCP client to ether1 but this has not happened this time. the bridge does not cause immediate issues but the addition of DHCP client caused real problems for me in the past!
Please understand that every customer may have their own particular configuration and often is not helped when it is changed underneath them.
I write this here too, it seems in ros v7.0beta3 the 2.4GHz radios drops off some dBm of its tramsit signal level and client can’t connect to it while 5GHz radio is working fine.