[Solved] WAN no longer comes up by itself in 2.4.2-RELEASE-p1

piperspace · Dec 29, 2017, 11:47 PM

On Reboot I consistently see DHCP = DOWN for the WAN in Status => Interfaces. If I click Renew I then get IP(s) and processing resumes normally.

If I set IPV6 Configuration Type = None in my WAN configuration I lose IPV6 support but I then get an IPV4 address normally on reboot.

My set up is Comcast <=> Cisco DCP3008 Modem <=> Netgate SG-4860 <=> LAN.

This behavior began immediately after upgrading from 2.4.2 to 2.4.2-p1. Nothing else has changed.

I can live without IPV6 for now but something does not seem right with the DHCP client on reboot.

piperspace · Dec 29, 2017, 11:56 PM

Turns out I had an evil cable connecting Modem <=> Router.

This apparently slowed speed and duplex negotiation during boot enough that the dhclient process was exiting with an error.

I have no idea why the DHCP6 setting had an influence.

Swapping out the evil cable fixed my issue.

Raul Ramos · Dec 29, 2017, 11:57 PM

Thanks for share the solution.