I’ve just upgraded ROS 4.0RC1 to 4.1 and the DHCP Client stop working, it’s all the time searching and doesn’t acquire IP.
To solve this I made a downgrade to ROS 4.0RC1 and DHCP Client start working again.
Does anyone have the same problem?
My router: RB433UAH
I had lots of syslog messages from my main DHCP server (routeros 3.30):
dhcp,warning 0-inside offering lease 10.xx.xx.118 for 00:01:03:31:70:58 without success
The DHCP client (4.1 x86 3com nic) could not get DHCP address. A simple reboot fixed it (without downgrading). I’m not sure if this will continue to happen or if it was an odd occurance. If it happens again I will pcap it.
Not only client has problems. We have router with couple of vlans with 2 dhcp server on 2 of them. One is working ok, second is dead (is not giving addresses). Yesterday we had 4.0 version - one of dhcp servers was in red without reason. All this happend after upgrade from 3.30 to 4.0.
the same problem here. RB 433 AH, upgraded from ROS 3.30 to 4.1 (bootloader from 2.20 to 2.23).
After the upgrade the DHCP client hangs up on “searching” status, ports 2 and 3. Port 1 (the one with POE) works.
The only solution for me was to downgrade back to 3.30, just restarting the router didn’t help. Now I’m running fine on 3.30 (fw 2.23) and everything is working fine
I can confirm that on rb133c and rb411 with ROS4.3 the dhcp-client is not working.
Installed the new packages on rb3.24 and rb3.28 versions and after that dhcp-client stays empty in winbox (just no ´client, and thus not searching) and in terminal the terminal session hangs after I put any command after the IP / dhcp-client prompt..
All other normal basic functions are fine and working…