@strods, for your attentionnuffrespect - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
Ticket#2018020522000654, Ticket#2018013122002471
DiM
@strods, for your attentionnuffrespect - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
There is no Netinstall service available. Im making reset from CLI.feris - Do you see such behavior on single unit? Are you sure that default configuration on this device is not replaced with another one by using Netinstall;
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/system routerboard mode-button
set enabled=no on-event=""
Done! In fact, several supouts attached to it evenNetflashTechnical - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
Yeah that's probably a good idea. My last AP was a hAP ac lite, and it had a static IP. Might as well set a static on this one.This just happened to me on a hAP lite RB941-2nD configured a similar way, but on 6.39.3. So problem appears to be older than 6.41.1.
It is configured as a wireless client (station pseudobridge) with all Ethernet ports configured as a switch, a bridge with wlan1, with dhcp-client configured on the bridge. DHCP server would see mac of wlan1 or sometimes mac of bridge/ether1. No admin mac set on the bridge. I recall a reboot would often make it change but not always. It would get a different IP from the DHCP server. I set a static IP on ether1 and disabled the dhcp-client to get around it.
The update resets the hotspot files! I have the login customized and it's now gone!
We are sorry for any inconvenience caused. We will fix this problem in 6.41.2 RouterOS release;
*) ovpn - fixed resource leak on systems with high CPU usage;
Use Wireshark or tcpdump to see whether the machine sends bootp packets after restart. If it does, use netinstall to reinstall the software.While updating to 6.41.1 from 6.41 my HAP did not make it, it was powered on port 1 with PoE.
...
Any other suggestions what to do next?
Done: Ticket#2018020622006647NetflashTechnical, ithierack, theq, Clauu, freemannnn, nuffrespect - Please generate supout file on your router while you see such behavior and send this file to support@mikrotik.com
SendSirPrikol - Did you downgrade to 6.41 routes where working and upgrade to 6.41.1 and they are not working again? Can you provide supout file to support@mikrotik.com which would be generated while there are such routes on router;
You may use any - they have similar interface and functionality.In case of WinBox vs. Browser as interface to ROS ..., what is next to Terminal ( I would like to avoid to install WinBox on my MacBook) ?
Yes and yes. I've already had it confirmed by support as a bug - [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-client.Is this a bug ?
Anybody else seeing this ?
sid5632 - thanks for your prompt input/reply.Yes and yes. I've already had it confirmed by support as a bug - [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-client.Is this a bug ?
Anybody else seeing this ?
After initially telling me it was correct, I argued my case and then they said:
"This client indeed is created by mistake. We will try to fix this in upcoming RouterOS versions."
I found that creating a bridge and adding ether1 as a bridge port stopped it from doing this, because you can't have a DHCP client on a slave interface.
junior18 , I think this translated is: "password could help me with this mikrotik"podrian ayudarme con la password de este mikrotic
There must be a little more to it, as on my CHR (which has ether1 and ether2 both with static address and no DHCP) I cannot reproduce it.I think I found a bug
The problem is on every reboot, the Mikrotik CHR auto injects a dhcp-client option.
Can not reproduce it either. It does however create a DHCP client on ether1 when deploying the CHR with the use of the ova template even when you use 'static IP' in the wizard without actually entering an IP-address.There must be a little more to it, as on my CHR (which has ether1 and ether2 both with static address and no DHCP) I cannot reproduce it.I think I found a bug
The problem is on every reboot, the Mikrotik CHR auto injects a dhcp-client option.
But why?DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.
Not quite. It's more like "could you help me with this mikrotik password?"junior18 , I think this translated is: "password could help me with this mikrotik"podrian ayudarme con la password de este mikrotic
Not sure I understand your question/statement
North Idaho Tom Jones
I was upgrading some routers from previous versions to 6.41, when all of a sudden I notice the most recent version is now 6.41.1.
I noticed that on 6.41.1 I am unable to change the neighbor discover-setting. Shown below are console output from a 6.41 router and a 6.41.1 router. They are the same router. I performed the first neighbor discovery setting change from !dynamic to all, then upgraded the router from 6.41 to 6.41.1. When the router came back online, the neighbor discovery setting was reset from all to !dynamic, and I am unable to get it to change at all now, even after multiple reboots. This occurs from the console and winbox. Interesting...
Code: Select all# running v6.41 - can make changes to neighbor discovery-settings [user@router] > /ip neighbor discovery-settings [user@router] /ip neighbor discovery-settings> print discover-interface-list: !dynamic [user@router] /ip neighbor discovery-settings> set discover-interface-list=all [user@router] /ip neighbor discovery-settings> print discover-interface-list: all [user@router] /ip neighbor discovery-settings> /system package update install # now running v6.41.1 - after reboot - can NOT make changes to neighbor discovery-settings from cli or winbox [user@router] /ip neighbor discovery-settings> /ip neighbor discovery-settings [user@router] /ip neighbor discovery-settings> print discover-interface-list: !dynamic [user@router] /ip neighbor discovery-settings> set discover-interface-list=all [user@router] /ip neighbor discovery-settings> print discover-interface-list: !dynamic [user@router] /ip neighbor discovery-settings>
ditto on the why question ?DHCP client on CHR reappears on purpose. You can not delete it. It is intended behavior.
Hello Sindy,The "special" bridge solution brings some advantages (namely, hardware switching where possible and a possibility to run MSTP protocol and better operation of other flavours of STP).
The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problemsHello Sindy,
thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?
Thanks !
@coliflower, @LIV2 has put in another words what I've already written: the new way of bridging won't bring anything useful to you until you decide to deploy more than one Ethernet port, as it unites "bridge" and "switch" configuration into one and lets the RouterOS itself decide which functionality to execute in hardware and which in software. But you can change the settings if you want, so if the documentation is not clear enough, try to read the same in another wording in this post.The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problemsHello Sindy,
thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?
Thanks !
Can you share your config?
Because device canot stable so I tried to Netinstall but doesnt work.Splash
mla, minhcoi - Have you tried to Netinstall your device;
Yes, can do it if I am back from my business-trip.The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problemsHello Sindy,
thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?
Thanks !
Can you share your config?
Thank you Sindy,@coliflower, @LIV2 has put in another words what I've already written: the new way of bridging won't bring anything useful to you until you decide to deploy more than one Ethernet port, as it unites "bridge" and "switch" configuration into one and lets the RouterOS itself decide which functionality to execute in hardware and which in software. But you can change the settings if you want, so if the documentation is not clear enough, try to read the same in another wording in this post.The change in bridging is to do with hardware switching I thought, and since the wAP-ac doesn't use a switch chip you shouldn't be having any problemsHello Sindy,
thank you !
In this case, maybe I should to got the way of future und to adapt my configuration on both wAP-ac to the new bridge ... any recommendation how to start, what to read, etc. ?
Thanks !
Can you share your config?
Please look at my comments on [Ticket#2018012422000218] [MT Support] CHR keeps recreating unwanted ether1 dhcp-clientTomjNorthIdaho, sid5632, pe1chl, SPKA16, XaTTa6bl4 - This is intended behavior, because it is required in order to access CHR (when used on cloud services not hosted by yourself and you do not have access to the console).
It looks good. At the first connection establishment the connection will be established.onlineuser - It might affect your situation, however, we can not give you precise yes or no answer. If the problem that you have is caused by delayed/slow responses to/from OVPN server, then this might help and your problem might go away;
Can you winbox to MAC address?After update 6.41.1 my RB951Ui 2HnD has alway reboot, and i cant winbox to interface address. How can I fix this?