The pfSense Store

Author Topic: [Solved] WAN no longer comes up by itself in 2.4.2-RELEASE-p1  (Read 255 times)

0 Members and 1 Guest are viewing this topic.

Offline piperspace

  • Newbie
  • *
  • Posts: 6
  • Karma: +2/-0
    • View Profile
[Solved] WAN no longer comes up by itself in 2.4.2-RELEASE-p1
« on: December 27, 2017, 04:52:29 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.   

 
« Last Edit: December 29, 2017, 05:47:04 pm by piperspace »

Offline piperspace

  • Newbie
  • *
  • Posts: 6
  • Karma: +2/-0
    • View Profile
Re: [Solved] WAN no longer comes up by itself in 2.4.2-RELEASE-p1
« Reply #1 on: December 29, 2017, 05:56:04 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.
 

Offline mais_um

  • Full Member
  • ***
  • Posts: 245
  • Karma: +4/-0
    • View Profile
Re: [Solved] WAN no longer comes up by itself in 2.4.2-RELEASE-p1
« Reply #2 on: December 29, 2017, 05:57:43 pm »
Thanks for share the solution.
pfSense:
ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)