Hello, there is a serious bug on firmware 13.20.26 of internet box 3 (I imagine it is the same on 4)
Upon switching to this firmware, certain devices no longer receive an IP address via DHCP, in particular and all those behind a Wifi2Ethernet gateway type IOGear GWU637
if I go back to 13.01.24 everything works perfectly
>… DHCP problem with Firmware 13.20.26…
this problem has not been noted in this current version on IB3 or IB4
as indicated by @Prelude a logical restart of the internet-box should solve the problem 😀
Release Notes (Version 13.20.26)
New:
- Security improvements and various stability improvements related to Internet connection, WiFi and telephony.
- Added IKEv2 VPN support for MAC, Linux, iOS and Android.
- The Internet Mobile Connect feature is enabled by default and cannot be disabled from the web portal.
- Introduction of a new version of the WLAN driver (IB3, IB4).
- New version 46v1 of DSL Datapump with stability improvements introduced (IB3).
- Optimization of the WEB portal for use from mobile devices (responsive design).
- New version of the DECT base with optimized calibration.
Resolved:
- WiFi: SSID sometimes changes after a reboot (IB4).
- Disabling WiFi 6 (802.11ax) from the web portal has no effect.
- Web portal: improvements to the topological view.
If there is a serious bug on firmware 13.20.26 there would be an outcry here on the forum. No discussion of this problem on the 4 languages of the forum, rather an isolated problem because no known problem
Optionally check the configuration of your WiFi2EthernetWifi2 IOGear GWU637 gateway
Personally I tested on my gateway of another brand by introducing 3 devices all ended up with the IPs in DHCP without problem.
Cordialement Doremi
The problem is not frequent, it is normal that there is no feedback on the forums, all my devices normally recover an IP fortunately.
Only the one behind my wifi2ethernet converter no longer recovers any after the upgrade
In fact I lost access to my device some time ago and it took me a while to make the link with firmware 13.20.26 initially.
I really did a lot of testing and analysis.
I completely reset my adapter, tried everything config level
It was only after a few days that I understood that it was the firmware of the internet box.
Since it’s been identified, it’s very easy to prove, the device works, I switch to 13.20.26, the device is still visible over wifi but it no longer takes an IP
I downgrade to 13.01.24 it works immediately, I upgrade again to 13.20.26 no more IP
There is absolutely no doubt, believe me
I found a workaround:
you have to go to 13.20.26
there we immediately lose the device (no more IP via DHCP)
make a backup of the IB3 (save the configuration in a file)
you must restore the default settings of the IB3
And restore the saved configuration
And there strangely the device finally recovers an IP in DHCP
Good news, I finally regain access to my boiler 😉 But it’s still not very normal, there is a problem with this 13.20.26
Good morning,
I’m digging this topic up because I ran into the same issue again of DHCP not distributing IPs, and I found out some stuff
I understood why it works after restoring the default settings + restoring the saved config:
In fact the restore resets the encryption!
The encryption which was in WPA2/WPA3 switches back to WPA2, and incidentally the WPS is restored even though I had disabled it
And obviously my device works correctly in WPA2 mode but not in WPA2/WPA3, which I don’t understand since for non-WPA3 compatible devices it should be the same thing.
but in my case the device connects correctly, validates the key but DHCP does not give it an IP
By restoring the internet box configuration I switch back to WPA2 and it works again.
Any ideas?
- Why does the backup reset the choice of encryption and WPS?
- And above all, how is it possible that a device compatible with WPA2/AES works with WPA2 encryption but not with WPA2/WPA3?
