Upgrade to 2.3.2_1 kills WAN link



  • Upgraded to 2.3.2_1 this morning and everything seemed to go OK by the logs and console except I have no connection on the WAN, it shows offline.  Since this is just a home system, I keep an old Linksys e3000 on the rack for testing and maintenance.  It comes online just fine (I'm able to leave this message).  I suspected maybe the onboard NIC I use for the WAN connection had crapped out so I disabled it and installed another Intel NIC.  I reassigned the new NIC to the WAN and it still fails to negotiate with the TA and get an IP address.  Go back to the plastic box router and all is fine.

    Terminal adapter to the Provider (Suddenlink) is an Arris model TM822.

    Ideas?  or just go back to 2.3.2?

    Rick



  • You DID reboot the (cable) modem, right?

    @Ramosel:

    Upgraded to 2.3.2_1 this morning and everything seemed to go OK by the logs and console except I have no connection on the WAN, it shows offline.  Since this is just a home system, I keep an old Linksys e3000 on the rack for testing and maintenance.  It comes online just fine (I'm able to leave this message).  I suspected maybe the onboard NIC I use for the WAN connection had crapped out so I disabled it and installed another Intel NIC.  I reassigned the new NIC to the WAN and it still fails to negotiate with the TA and get an IP address.  Go back to the plastic box router and all is fine.

    Terminal adapter to the Provider (Suddenlink) is an Arris model TM822.

    Ideas?  or just go back to 2.3.2?

    Rick



  • @pppfsense:

    You DID reboot the (cable) modem, right?

    Yep, several times. 
    Observation: As the power comes on to the pfSense machine, the link light on the Arris box goes valid (green).  As the boot progresses and the drivers load, the link light goes out.  Boot finishes with no WAN IP negotiation.

    Been busy with other projects but just may do a clean reload today and pull a restore.

    Rick



  • Doesn't make sense.

    If the NIC was working with a previous version, a new version would not have killed the NIC.
    Plus you do see the link on the modem coming up as pfsense boots right? (i.e. NIC works).

    Reboot modem, reboot pfsense.
    Check Status - Interfaces and try to get a new DHCP address.

    You can also try assigning the MAC address of the Linksys router to the WAN interface so you don't have to reboot the modem.
    Last resource, just for testing, assign the given DHCP address to the WAN interface (no DHCP).

    (You can also try connecting the pfsense WAN to the Linksys router and see if pfsense gets a DHCP address).

    @Ramosel:

    @pppfsense:

    You DID reboot the (cable) modem, right?

    Yep, several times. 
    Observation: As the power comes on to the pfSense machine, the link light on the Arris box goes valid (green).  As the boot progresses and the drivers load, the link light goes out.  Boot finishes with no WAN IP negotiation.

    Been busy with other projects but just may do a clean reload today and pull a restore.

    Rick