Pfsense ignoring DHCP offer on WAN



  • Hi all,

    I've got a perplexing problem with a new pfsense setup.  The box seems to be ignoring the WAN IP assignment from an SB6141 modem on Cox Internet.

    Cox is seeing the IP request and it is sending an IP but the box is not picking it up.

    I testing the setup with a Macbook Pro and it picks up the IP just fine.

    In addition, I mac address spoofed on the pfsense box (using the mac from the Macbook Pro).  Cox saw the DHCP request with the spoofed mac and issued an IP.  Again, the pfsense box didn't pick it up.

    I'm just at a loss here.  Need another set of eyes and a clear head to give me some suggestions please.

    thanks,
    Dave



  • Hmm… SB6141 is a plain DOCSIS modem that should work by default with pfSense, did you  check pfSense logs for errors?



  • @w0w:

    Hmm… SB6141 is a plain DOCSIS modem that should work by default with pfSense, did you  check pfSense logs for errors?

    I've come to the conclusion that the ethernet ports are toast.  This started happening right after a power cycle.  I can't communicate with the box via a hardwired laptop.

    Odd that ethernet ports can talk but not hear….



  • Is it possible you have your Ethernet cables reversed?



  • @coxhaus:

    Is it possible you have your Ethernet cables reversed?

    Not at all.


  • Netgate

    Realtek NICs?



  • @Derelict:

    Realtek NICs?

    Sorry for the late reply.  Yes, they are Realtek NICs.


  • Netgate

    I had to replace the realtek daughtercard in my old jetway because of the same sort of thing. It would seemingly go deaf and would manifest itself as failed DHCP renewals from the cable modem.

    Same router, same slot, but an intel daughtercard and I never saw it again.

    One of those anecdotal stories about realtek.

    (I did packet capture prior to swapping it out and the modem/isp were doing everything they should be doing.)



  • @Derelict:

    I had to replace the realtek daughtercard in my old jetway because of the same sort of thing. It would seemingly go deaf and would manifest itself as failed DHCP renewals from the cable modem.

    Same router, same slot, but an intel daughtercard and I never saw it again.

    One of those anecdotal stories about realtek.

    (I did packet capture prior to swapping it out and the modem/isp were doing everything they should be doing.)

    Ugh….  Since your post I've done a lot more research and now see that Realtek NICs are a major issue.  Unfortunately, I've got a small single-board computer with NICs on the board.....



  • @vronp:

    @Derelict:

    I had to replace the realtek daughtercard in my old jetway because of the same sort of thing. It would seemingly go deaf and would manifest itself as failed DHCP renewals from the cable modem.

    Same router, same slot, but an intel daughtercard and I never saw it again.

    One of those anecdotal stories about realtek.

    (I did packet capture prior to swapping it out and the modem/isp were doing everything they should be doing.)

    Ugh….  Since your post I've done a lot more research and now see that Realtek NICs are a major issue.  Unfortunately, I've got a small single-board computer with NICs on the board.....

    Just to cap off this thread…..I've found some mention of a v1.93 driver that may have improved things....