New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3048 - Kernel 5.4 no wan connection on Netgear R6850 #7919
Comments
eaforlife: Update: Until I changed the physical interface of the WAN to eth0 instead of 'wan' until I get an error via Luci interface. Once I get the error "Connection attempt error", I would switch the physical interface back to 'wan' interface and I got a connection. I did another reboot to try my workaround. This time it took like around 4 attempts of switch the physical interface until I get an IP on the WAN interface. Attached are the following:
|
Nicarim: I'm having same issue on Asus RT-AC85P which seems to be same processor as yours. I choose to keep settings when flashing the new image - might that be a reason? Did you wipe yours when applying new firmware? |
eaforlife: Hey! The first time I compiled the new commit, coming from 4.14.172, I have upgraded it to keep the settings before flashing it. I realized maybe the commits meant mediatek devices as I assumed that my device was still under ramips. Right now it's under Mediatek MIPS. Keeping the settings will make me not able to connect to the router using LAN connections. Only via WiFi 2.4G and 5G. So had to grab a laptop and revert the router to my previously compiled firmware to boot and tried again. This time by flashing it without retaining any settings since I saw the Kernel is now 5.4.x. I am now able to connect via luci and ssh to the router, however WAN is not working correctly. I figured a workaround that might have fixed it, which is via luci (since I was only able to re-produce it there), is to change the physical wan interface to something else like eth0. Wait 1 minute then revert it back to WAN interface. Had to do it atleast 3 times for it to work. DHCP, Static and PPPoE were the ones I tested. Works even after you restart the router. You just have to keep on doing those steps until you get an IP (PPPoE and DHCP) or Static IP is pingable. Currently on my 2nd day with kernel 5.4.35 and rebooted it twice already. |
eaforlife: Hello, Want to provide an update. This bug no longer persist and WAN interface is working as expected. Build: r13527-61307544d1 |
eaforlife:
Affected Device - Netgear R6850
Software Versions:
Issue:
Step to reproduce:
//PS: Can provide detailed logs if requested as I am back to kernel 4.14.172 commit. Since this router serves as gateway to our home internet with multiple clients.//
The text was updated successfully, but these errors were encountered: