Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WAN link going down

    Problems Installing or Upgrading pfSense Software
    9
    62
    14.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Q
      q54e3w
      last edited by

      I have the same issue and posted some logs in another thread yesterday. I've seen a few posts like this recently do possibly something needs tweaking. I'll add a link to my logs tomorrow when I get back to my desk. I've tried setting static address, disabling monitoring but every 3-7 days my line drops and needs s reboot of wan or box to resolve.

      Edit: here's the link to my logs… https://forum.pfsense.org/index.php?topic=88236.msg491251#msg491251

      1 Reply Last reply Reply Quote 0
      • T
        TieT
        last edited by

        In System -> general settings i added 127.0.0.1 as first dns server without any gateway
        then on the second line:
        8.8.8.8 with the gateway from my provider 84.192.192.1
        on the third:
        8.8.4.4 with 84.192.192.1

        the option to automatically find the gateway seems to f*ck the wan link sometimes…

        I didn't make any changes otherwise to the network config.

        Only updated LCDProc and used your guide to set it up because it kept crashing badly.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Interesting, thanks.

          1 Reply Last reply Reply Quote 0
          • X
            xtofh
            last edited by

            Hi,

            Are you sure this is resolved? I find it strange that changing dns settings solves this.

            Looking at your IP gateway, we're using the same internet provider and I'm having the same issue. (only updated yesterday, noticed the link going down today)

            I had a similar issue a few years back: https://forum.pfsense.org/index.php?topic=51420.0

            It was solved by using the 2.1 release. But now the problem returned after updating to 2.2.

            I'll keep an eye on it (it only happened once now) and will collect logs in case it returns.

            Regards,
            Kristof.

            1 Reply Last reply Reply Quote 0
            • X
              xtofh
              last edited by

              Okay, just had this happen again, here's the logs from that time.

              All VPNs going down..

              Feb 25 13:53:01 pfsense kernel: ovpns23: link state changed to DOWN
Feb 25 13:53:01 pfsense php-fpm[89891]: /rc.newwanip: rc.newwanip: Info: starting on ovpns19.
Feb 25 13:53:01 pfsense php-fpm[89891]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.250.17) (interface: []) (real interface: ovpns19).
Feb 25 13:53:01 pfsense php-fpm[89891]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection -  ->  192.168.250.17 - Restarting packages.
Feb 25 13:53:01 pfsense check_reload_status: Starting packages
Feb 25 13:53:02 pfsense php-fpm[21603]: /rc.openvpn: OpenVPN: Resync server24 [CUST26] S2S
Feb 25 13:53:02 pfsense kernel: ovpns23: link state changed to UP
Feb 25 13:53:02 pfsense check_reload_status: rc.newwanip starting ovpns23
Feb 25 13:53:02 pfsense kernel: ovpns24: link state changed to DOWN
Feb 25 13:53:02 pfsense check_reload_status: Reloading filter

              Our WAN interface.. (em1)

              Feb 25 13:53:02 pfsense kernel: em1: Watchdog timeout -- resetting
Feb 25 13:53:02 pfsense kernel: em1: Queue(0) tdh = 801, hw tdt = 770
Feb 25 13:53:02 pfsense kernel: em1: TX(0) desc avail = 31,Next TX to Clean = 801

              The rest of the VPNs going down. (we've got 30 or so)

              Feb 25 13:53:02 pfsense php-fpm[21603]: /rc.openvpn: OpenVPN: Resync server25 [CUST25] S2S
Feb 25 13:53:02 pfsense kernel: ovpns24: link state changed to UP
Feb 25 13:53:02 pfsense check_reload_status: rc.newwanip starting ovpns24
Feb 25 13:53:02 pfsense kernel: ovpns25: link state changed to DOWN
Feb 25 13:53:02 pfsense kernel: em1: link state changed to DOWN
Feb 25 13:53:02 pfsense check_reload_status: Linkup starting em1
Feb 25 13:53:02 pfsense php-fpm[21603]: /rc.openvpn: OpenVPN: Resync server26 [CUST26] S2S
Feb 25 13:53:02 pfsense kernel: ovpns25: link state changed to UP
Feb 25 13:53:02 pfsense check_reload_status: rc.newwanip starting ovpns25
Feb 25 13:53:02 pfsense kernel: ovpns26: link state changed to DOWN
Feb 25 13:53:03 pfsense php-fpm[21603]: /rc.linkup: DEVD Ethernet detached event for wan
Feb 25 13:53:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 25 13:53:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 25 13:53:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 25 13:53:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1

              And then it continues with the can't allocate llinfo.

              I tried disconnecting and re-connecting the network cable: no result.
              I tried rebooting the cable modem: no result.

              It did try getting a new DHCP address:

              
$ tcpdump -i em1 -n
14:04:25.808903 IP 81.82.209.44.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:27.003202 IP 81.82.209.44.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:31.003925 IP 81.82.209.44.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:40.009358 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:41.009469 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:42.000206 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300
14:04:44.001156 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:0d:88:cc:fa:2f, length 300

              But that's it, never got any.

              Final step we took (because it was taking us +5 minutes already) was reboot the pfsense. After the reboot connection was good..

              I will probably take a 2.1.5 to temporarily switch this one out (luckily it's in our building) but will leave the 2.2 in place so I can switch easily.

              So I there's anything I can/should try, let me know, no problem.

              Regards,
              Kristof

              1 Reply Last reply Reply Quote 0
              • Q
                q54e3w
                last edited by

                Id love to share with you a solution but Im seeing exactly the same thing here and can confirm its not fixed for me by manipulating DNS as TieT suggested fixed his. My issue is triggered by my ISP WAN dhcp address expiring every seven days. Rebooting the firewall is the easiest way to fix it, I spent a couple of hours last time it went down capturing packets and what not and it appears in my situation to be related to DHCP queries not syncing. It could be specific to my ISP and I'll keep capturing and investigating if/when it continues. Thanks for sharing your logs.

                1 Reply Last reply Reply Quote 0
                • X
                  xtofh
                  last edited by

                  I've put my 2.1.5 back in place. let's see how this goes. (I'm pretty sure this will stay up)

                  I also suspect it has something to do with the dhcp renewal.

                  2.1 solved it in 2012 for me :-) - https://forum.pfsense.org/index.php?topic=51420.0

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by 

                    Feb 25 13:53:02 pfsense kernel: em1: Watchdog timeout -- resetting

                    That is a pretty bad sign.

                    You might try looking at sysctl dev.em.1
                    There may be some error couters there that show something nasty happened.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • X
                      xtofh
                      last edited by

                      Ok, put a switch in between modem<->pfsense , recorded the current state of sysctl dev.em.1 (attached)

                      Currently it's good  :o (lol)  but if the problem returns I'll redo the sysctl dev.em.1 and won't reboot. (I'll just use a 2.1.5 device so can grab any logs needed of the 2.2)

                      Thanks, I'll keep you posted.

                      Kristof

                      devem1.txt

                      1 Reply Last reply Reply Quote 0
                      • J
                        JWTech
                        last edited by

                        I'm getting the same issue.

                        Seems my external IPv4, which is set by DHCP, is randomly disconnecting while the IPv6 address is fine.

                        No clue what's the cause, but I'm running the latest version on a Nano USB.

                        1 Reply Last reply Reply Quote 0
                        • X
                          xtofh
                          last edited by

                          Ok, not resolved yet :(

                          My current configuration is Modem <-> Switch <-> pfsense.

                          I did see some bad things in the sysctl.em.1 :

                          dev.em.1.mac_stats.collision_count: 0
dev.em.1.mac_stats.symbol_errors: 4294967295
dev.em.1.mac_stats.sequence_errors: 0
dev.em.1.mac_stats.missed_packets: 28403

                          My log was already full (I will make it bigger or use remote syslog) but I did see this:

                          .. first a ton of these messages:
Feb 28 11:21:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:04 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:05 pfsense kernel: em1: Watchdog timeout -- resetting
Feb 28 11:21:05 pfsense kernel: em1: Queue(0) tdh = 0, hw tdt = 993
Feb 28 11:21:05 pfsense kernel: em1: TX(0) desc avail = 31,Next TX to Clean = 0
Feb 28 11:21:05 pfsense kernel: em1: link state changed to DOWN
Feb 28 11:21:05 pfsense check_reload_status: Linkup starting em1
Feb 28 11:21:06 pfsense php-fpm[43360]: /rc.linkup: DEVD Ethernet detached event for wan
Feb 28 11:21:06 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:06 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:09 pfsense check_reload_status: Linkup starting em1
Feb 28 11:21:09 pfsense kernel: em1: link state changed to UP
Feb 28 11:21:10 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:10 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:11 pfsense php-fpm[43360]: /rc.linkup: Shutting down Router Advertisment daemon cleanly
Feb 28 11:21:11 pfsense php-fpm[54180]: /rc.linkup: DEVD Ethernet attached event for wan
Feb 28 11:21:11 pfsense php-fpm[54180]: /rc.linkup: HOTPLUG: Configuring interface wan
Feb 28 11:21:13 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:13 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
Feb 28 11:21:14 pfsense kernel: arpresolve: can't allocate llinfo for 81.82.192.1 on em1
.. and then more of these

                          This only happens on 2.2, the same configuration with 2.1.5, no problem. It took about 30 hours before it occured the first time.

                          Anything else I might try to resolve/further pinpoint this?

                          Regards,
                          Kristof.

                          1 Reply Last reply Reply Quote 0
                          • DerelictD
                            Derelict LAYER 8 Netgate
                            last edited by

                            New hardware?

                            Chattanooga, Tennessee, USA
                            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                            Do Not Chat For Help! NO_WAN_EGRESS(TM)

                            1 Reply Last reply Reply Quote 0
                            • X
                              xtofh
                              last edited by

                              @Derelict:

                              New hardware?

                              No, only diiference: 2.1.5 -> 2.2.

                              1 Reply Last reply Reply Quote 0
                              • DerelictD
                                Derelict LAYER 8 Netgate
                                last edited by

                                @man:

                                arpresolve: can't allocate llinfo for %d.%d.%d.%d The route for the ref-
                                    erenced host points to a device upon which ARP is required, but ARP was
                                    unable to allocate a routing table entry in which to store the host's MAC
                                    address.  This usually points to a misconfigured routing table.  It can
                                    also occur if the kernel cannot allocate memory.

                                What's in netstat -rn when it's failing?

                                Chattanooga, Tennessee, USA
                                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                                1 Reply Last reply Reply Quote 0
                                • J
                                  JWTech
                                  last edited by

                                  Just resolved my issue by disabling the local DNS resolution. Changed it to just use Google's DNS servers instead (8.8.8.8, 8.8.4.4) and it's working fine.

                                  Not sure if it's the exact same issue as what everyone else has had, but that's what did it for me.

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    TieT
                                    last edited by

                                    Test it for a few days, it worked for me for a few days, but then the gateway was lost again.
                                    It seems when I create a vpn to my fw the issue begins…

                                    @JWTech:

                                    Just resolved my issue by disabling the local DNS resolution. Changed it to just use Google's DNS servers instead (8.8.8.8, 8.8.4.4) and it's working fine.

                                    Not sure if it's the exact same issue as what everyone else has had, but that's what did it for me.

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      xtofh
                                      last edited by

                                      @Derelict:

                                      @man:

                                      arpresolve: can't allocate llinfo for %d.%d.%d.%d The route for the ref-
                                          erenced host points to a device upon which ARP is required, but ARP was
                                          unable to allocate a routing table entry in which to store the host's MAC
                                          address.  This usually points to a misconfigured routing table.  It can
                                          also occur if the kernel cannot allocate memory.

                                      What's in netstat -rn when it's failing?

                                      Tnx for the suggestion, will try this and the sysctl dev.em.1 on next problem.

                                      I'm waiting for it to occur again (it can take several hours but it might as well take 48 hours) and report back.

                                      Kristof

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        I find it odd that in both cases here the actual physical link is going down. If that was a modem issue I would expect the switch to as least show a different result. I guess in a watchdog time-out scenario the link is probably brought down when the NIC is reset.  Hmmm.

                                        Steve

                                        1 Reply Last reply Reply Quote 0
                                        • Q
                                          q54e3w
                                          last edited by

                                          I had my line go down this morning at 6:50am. I spent a couple of hours over breakfast debugging but this is beyond my level of knowledge to understand fully whats happening. I captured a ton of log material and tcpdump of my WAN interface during the initial outage and also during various reboots of pfsense and later my modem. I'll try and summarise this here but if needed I can zip this lot up and pass eton to a dev or something if that helps? Excuse me if I break this into a few posts to make it easy to write.

                                          Notes
                                          I'm using virgin media in the UK with their Superhub in modem mode
                                          igb4 is my WAN port and I've set its MAC address to 00:22:68:1f:74:81.

                                          this is what i recorded when I got to my desk and found the WAN had dropped.

                                          
[2.2-RELEASE][admin@pfsense.irj972.local.lan]/var/log: netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags      Netif Expire
0.0.0.0/8          link#7             U          igb4
127.0.0.1          link#13            UH          lo0
192.168.10.0/24    link#1             U          igb0
192.168.10.1       link#1             UHS         lo0
192.168.50.0/24    link#8             U          igb5
192.168.50.1       link#8             UHS         lo0
192.168.60.0/24    link#9             U          igb6
192.168.60.1       link#9             UHS         lo0
192.168.70.0/24    link#10            U          igb7
192.168.70.1       link#10            UHS         lo0
192.168.101.0/24   link#5             U           ix0
192.168.101.1      link#5             UHS         lo0
192.168.110.0/24   link#6             U           ix1
192.168.110.1      link#6             UHS         lo0
192.168.210.0/24   192.168.210.2      UGS      ovpns2
192.168.210.1      link#15            UHS         lo0
192.168.210.2      link#15            UH       ovpns2

Internet6:
Destination                       Gateway                       Flags      Netif Expire
::1                               link#13                       UH          lo0
fe80::%igb0/64                    link#1                        U          igb0
fe80::a236:9fff:fe2d:eba8%igb0    link#1                        UHS         lo0
fe80::%ix0/64                     link#5                        U           ix0
fe80::92e2:baff:fe37:fba4%ix0     link#5                        UHS         lo0
fe80::%ix1/64                     link#6                        U           ix1
fe80::92e2:baff:fe37:fba5%ix1     link#6                        UHS         lo0
fe80::%igb4/64                    link#7                        U          igb4
fe80::222:68ff:fe1f:7481%igb4     link#7                        UHS         lo0
fe80::%igb5/64                    link#8                        U          igb5
fe80::ec4:7aff:fe07:d551%igb5     link#8                        UHS         lo0
fe80::%igb6/64                    link#9                        U          igb6
fe80::ec4:7aff:fe07:d552%igb6     link#9                        UHS         lo0
fe80::%igb7/64                    link#10                       U          igb7
fe80::ec4:7aff:fe07:d553%igb7     link#10                       UHS         lo0
fe80::%lo0/64                     link#13                       U           lo0
fe80::1%lo0                       link#13                       UHS         lo0
fe80::a236:9fff:fe2d:eba8%ovpns2  link#15                       UHS         lo0
ff01::%igb0/32                    fe80::a236:9fff:fe2d:eba8%igb0 U          igb0
ff01::%ix0/32                     fe80::92e2:baff:fe37:fba4%ix0 U           ix0
ff01::%ix1/32                     fe80::92e2:baff:fe37:fba5%ix1 U           ix1
ff01::%igb4/32                    fe80::222:68ff:fe1f:7481%igb4 U          igb4
ff01::%igb5/32                    fe80::ec4:7aff:fe07:d551%igb5 U          igb5
ff01::%igb6/32                    fe80::ec4:7aff:fe07:d552%igb6 U          igb6
ff01::%igb7/32                    fe80::ec4:7aff:fe07:d553%igb7 U          igb7
ff01::%lo0/32                     ::1                           U           lo0
ff01::%ovpns2/32                  fe80::a236:9fff:fe2d:eba8%ovpns2 U        ovpns2
ff02::%igb0/32                    fe80::a236:9fff:fe2d:eba8%igb0 U          igb0
ff02::%ix0/32                     fe80::92e2:baff:fe37:fba4%ix0 U           ix0
ff02::%ix1/32                     fe80::92e2:baff:fe37:fba5%ix1 U           ix1
ff02::%igb4/32                    fe80::222:68ff:fe1f:7481%igb4 U          igb4
ff02::%igb5/32                    fe80::ec4:7aff:fe07:d551%igb5 U          igb5
ff02::%igb6/32                    fe80::ec4:7aff:fe07:d552%igb6 U          igb6
ff02::%igb7/32                    fe80::ec4:7aff:fe07:d553%igb7 U          igb7
ff02::%lo0/32                     ::1                           U           lo0
ff02::%ovpns2/32                  fe80::a236:9fff:fe2d:eba8%ovpns2 U        ovpns2

                                          and this is the dhcpd.log which is basically full of repeating sections of this
                                          Same old pattern Ive been seeing for a few weeks now which I think syncs with my virgin modems 7 day DHCP expiry

                                          
Mar  2 08:29:25 pfsense dhclient: PREINIT
Mar  2 08:29:25 pfsense dhclient: EXPIRE
Mar  2 08:29:25 pfsense dhclient: Deleting old routes
Mar  2 08:29:25 pfsense dhclient: PREINIT
Mar  2 08:29:25 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2
Mar  2 08:29:25 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4
Mar  2 08:29:29 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 7
Mar  2 08:29:36 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 14
Mar  2 08:29:50 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 17
Mar  2 08:30:07 pfsense dhclient[25776]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 14
Mar  2 08:30:21 pfsense dhclient[25776]: No DHCPOFFERS received.
Mar  2 08:30:21 pfsense dhclient[25776]: Trying recorded lease 86.5.163.20
Mar  2 08:30:21 pfsense dhclient: TIMEOUT
Mar  2 08:30:21 pfsense dhclient: Starting add_new_address()
Mar  2 08:30:21 pfsense dhclient: ifconfig igb4 inet 86.5.163.20 netmask 255.255.255.0 broadcast 255.255.255.255 
Mar  2 08:30:21 pfsense dhclient: New IP Address (igb4): 86.5.163.20
Mar  2 08:30:21 pfsense dhclient: New Subnet Mask (igb4): 255.255.255.0
Mar  2 08:30:21 pfsense dhclient: New Broadcast Address (igb4): 255.255.255.255
Mar  2 08:30:21 pfsense dhclient: New Routers (igb4): 86.5.163.1
Mar  2 08:30:22 pfsense dhclient: New Routers (igb4): 86.5.163.1
Mar  2 08:30:23 pfsense dhclient: Deleting old routes
Mar  2 08:30:23 pfsense dhclient[25776]: bound: renewal in 244840 seconds.
Mar  2 08:30:26 pfsense dhcpd: Received signal 15, initiating shutdown.
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24
Mar  2 08:30:26 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24
Mar  2 08:30:27 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Mar  2 08:30:27 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Mar  2 08:30:27 pfsense dhcpd: All rights reserved.
Mar  2 08:30:27 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar  2 08:30:27 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6
Mar  2 08:30:27 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.
Mar  2 08:30:27 pfsense dhcpd: All rights reserved.
Mar  2 08:30:27 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Mar  2 08:30:27 pfsense dhcpd: Wrote 0 deleted host decls to leases file.
Mar  2 08:30:27 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.
Mar  2 08:30:27 pfsense dhcpd: Wrote 45 leases to leases file.
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24
Mar  2 08:30:27 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24
Mar  2 08:30:27 pfsense dhcpd: Sending on   Socket/fallback/fallback-net
Mar  2 08:30:27 pfsense dhclient[26757]: connection closed
Mar  2 08:30:27 pfsense dhclient[26757]: exiting.

                                          sysctl igb.4 related info. Nothing that jumped out to me like excessive interrupts, packet collisions etc….just looks like a dead NIC

                                          
dev.igb.4.%desc: Intel(R) PRO/1000 Network Connection version - 2.4.0
dev.igb.4.%driver: igb
dev.igb.4.%location: slot=20 function=0 handle=\_SB_.PCI0.D01B
dev.igb.4.%pnpinfo: vendor=0x8086 device=0x1f41 subvendor=0x15d9 subdevice=0x1f41 class=0x020000
dev.igb.4.%parent: pci0
dev.igb.4.nvm: -1
dev.igb.4.enable_aim: 1
dev.igb.4.fc: 3
dev.igb.4.rx_processing_limit: 100
dev.igb.4.dmac: 0
dev.igb.4.eee_disabled: 0
dev.igb.4.link_irq: 403
dev.igb.4.dropped: 0
dev.igb.4.tx_dma_fail: 0
dev.igb.4.rx_overruns: 0
dev.igb.4.watchdog_timeouts: 0
dev.igb.4.device_control: 1477706305
dev.igb.4.rx_control: 67141634
dev.igb.4.interrupt_mask: 4
dev.igb.4.extended_int_mask: 2147484159
dev.igb.4.tx_buf_alloc: 0
dev.igb.4.rx_buf_alloc: 0
dev.igb.4.fc_high_water: 33168
dev.igb.4.fc_low_water: 33152
dev.igb.4.queue0.no_desc_avail: 0
dev.igb.4.queue0.tx_packets: 2546184
dev.igb.4.queue0.rx_packets: 202589
dev.igb.4.queue0.rx_bytes: 0
dev.igb.4.queue0.lro_queued: 0
dev.igb.4.queue0.lro_flushed: 0
dev.igb.4.queue1.no_desc_avail: 0
dev.igb.4.queue1.tx_packets: 3569953
dev.igb.4.queue1.rx_packets: 122795
dev.igb.4.queue1.rx_bytes: 0
dev.igb.4.queue1.lro_queued: 0
dev.igb.4.queue1.lro_flushed: 0
dev.igb.4.queue2.no_desc_avail: 0
dev.igb.4.queue2.tx_packets: 995675
dev.igb.4.queue2.rx_packets: 31067808
dev.igb.4.queue2.rx_bytes: 0
dev.igb.4.queue2.lro_queued: 0
dev.igb.4.queue2.lro_flushed: 0
dev.igb.4.queue3.no_desc_avail: 0
dev.igb.4.queue3.tx_packets: 3674232
dev.igb.4.queue3.rx_packets: 88985
dev.igb.4.queue3.rx_bytes: 0
dev.igb.4.queue3.lro_queued: 0
dev.igb.4.queue3.lro_flushed: 0
dev.igb.4.queue4.no_desc_avail: 0
dev.igb.4.queue4.tx_packets: 4509460
dev.igb.4.queue4.rx_packets: 80735
dev.igb.4.queue4.rx_bytes: 0
dev.igb.4.queue4.lro_queued: 0
dev.igb.4.queue4.lro_flushed: 0
dev.igb.4.queue5.no_desc_avail: 0
dev.igb.4.queue5.tx_packets: 3015023
dev.igb.4.queue5.rx_packets: 95970
dev.igb.4.queue5.rx_bytes: 0
dev.igb.4.queue5.lro_queued: 0
dev.igb.4.queue5.lro_flushed: 0
dev.igb.4.queue6.no_desc_avail: 0
dev.igb.4.queue6.tx_packets: 2100212
dev.igb.4.queue6.rx_packets: 114919
dev.igb.4.queue6.rx_bytes: 0
dev.igb.4.queue6.lro_queued: 0
dev.igb.4.queue6.lro_flushed: 0
dev.igb.4.queue7.no_desc_avail: 0
dev.igb.4.queue7.tx_packets: 4101655
dev.igb.4.queue7.rx_packets: 105344
dev.igb.4.queue7.rx_bytes: 0
dev.igb.4.queue7.lro_queued: 0
dev.igb.4.queue7.lro_flushed: 0
dev.igb.4.mac_stats.excess_coll: 0
dev.igb.4.mac_stats.single_coll: 0
dev.igb.4.mac_stats.multiple_coll: 0
dev.igb.4.mac_stats.late_coll: 0
dev.igb.4.mac_stats.collision_count: 0
dev.igb.4.mac_stats.symbol_errors: 0
dev.igb.4.mac_stats.sequence_errors: 0
dev.igb.4.mac_stats.defer_count: 0
dev.igb.4.mac_stats.missed_packets: 0
dev.igb.4.mac_stats.recv_no_buff: 0
dev.igb.4.mac_stats.recv_undersize: 0
dev.igb.4.mac_stats.recv_fragmented: 0
dev.igb.4.mac_stats.recv_oversize: 0
dev.igb.4.mac_stats.recv_jabber: 0
dev.igb.4.mac_stats.recv_errs: 0
dev.igb.4.mac_stats.crc_errs: 0
dev.igb.4.mac_stats.alignment_errs: 0
dev.igb.4.mac_stats.coll_ext_errs: 0
dev.igb.4.mac_stats.xon_recvd: 0
dev.igb.4.mac_stats.xon_txd: 0
dev.igb.4.mac_stats.xoff_recvd: 0
dev.igb.4.mac_stats.xoff_txd: 0
dev.igb.4.mac_stats.total_pkts_recvd: 31875273
dev.igb.4.mac_stats.good_pkts_recvd: 31875273
dev.igb.4.mac_stats.bcast_pkts_recvd: 183
dev.igb.4.mac_stats.mcast_pkts_recvd: 0
dev.igb.4.mac_stats.rx_frames_64: 56499
dev.igb.4.mac_stats.rx_frames_65_127: 118706
dev.igb.4.mac_stats.rx_frames_128_255: 4268691
dev.igb.4.mac_stats.rx_frames_256_511: 308408
dev.igb.4.mac_stats.rx_frames_512_1023: 456179
dev.igb.4.mac_stats.rx_frames_1024_1522: 26666790
dev.igb.4.mac_stats.good_octets_recvd: 40798660342
dev.igb.4.mac_stats.good_octets_txd: 11294455422
dev.igb.4.mac_stats.total_pkts_txd: 24517003
dev.igb.4.mac_stats.good_pkts_txd: 24517003
dev.igb.4.mac_stats.bcast_pkts_txd: 6105
dev.igb.4.mac_stats.mcast_pkts_txd: 443
dev.igb.4.mac_stats.tx_frames_64: 282372
dev.igb.4.mac_stats.tx_frames_65_127: 291318
dev.igb.4.mac_stats.tx_frames_128_255: 17645482
dev.igb.4.mac_stats.tx_frames_256_511: 373380
dev.igb.4.mac_stats.tx_frames_512_1023: 166562
dev.igb.4.mac_stats.tx_frames_1024_1522: 5757889
dev.igb.4.mac_stats.tso_txd: 0
dev.igb.4.mac_stats.tso_ctx_fail: 0
dev.igb.4.interrupts.asserts: 48596954
dev.igb.4.interrupts.rx_pkt_timer: 31874824
dev.igb.4.interrupts.rx_abs_timer: 0
dev.igb.4.interrupts.tx_pkt_timer: 0
dev.igb.4.interrupts.tx_abs_timer: 0
dev.igb.4.interrupts.tx_queue_empty: 24512231
dev.igb.4.interrupts.tx_queue_min_thresh: 34287030
dev.igb.4.interrupts.rx_desc_min_thresh: 0
dev.igb.4.interrupts.rx_overrun: 0
dev.igb.4.host.breaker_tx_pkt: 0
dev.igb.4.host.host_tx_pkt_discard: 0
dev.igb.4.host.rx_pkt: 273
dev.igb.4.host.breaker_rx_pkts: 0
dev.igb.4.host.breaker_rx_pkt_drop: 0
dev.igb.4.host.tx_good_pkt: 161
dev.igb.4.host.breaker_tx_pkt_drop: 0
dev.igb.4.host.rx_good_bytes: 40798644311
dev.igb.4.host.tx_good_bytes: 11291998600
dev.igb.4.host.length_errors: 0
dev.igb.4.host.serdes_violation_pkt: 0
dev.igb.4.host.header_redir_missed: 0

                                          packet capture during failure to obtain address (this repeats etc)…...

                                          
[2.2-RELEASE][admin@pfsense.irj972.local.lan]/root: tcpdump -i igb4 -n -e\
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode\
listening on igb4, link-type EN10MB (Ethernet), capture size 65535 bytes\
capability mode sandbox enabled\
09:57:35.418721 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:57:43.603163 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:57:58.628668 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:10.300655 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:18.123653 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:23.094394 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
09:58:24.173118 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
09:58:35.209295 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:35.209350 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:38.615139 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:44.051533 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:58:57.754659 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:06.751717 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:13.412166 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:18.731217 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
09:59:26.140115 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:31.140733 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
09:59:32.223387 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
09:59:43.099670 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:43.099728 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:44.077917 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:46.088837 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:49.509144 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
09:59:57.149148 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:06.264730 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:19.273645 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:19.351130 0c:c4:7a:07:d3:4c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 86.6.30.1 tell 86.6.31.151, length 46\
10:00:19.359733 0c:c4:7a:07:d3:4c > 00:21:55:cb:93:da, ethertype IPv4 (0x0800), length 60: 86.6.31.151.445 > 88.245.242.252.51368: Flags [R.], seq 0, ack 1015706558, win 0, length 0\
10:00:19.965117 0c:c4:7a:07:d3:4c > 00:21:55:cb:93:da, ethertype IPv4 (0x0800), length 60: 86.6.31.151.445 > 88.245.242.252.51368: Flags [R.], seq 0, ack 1, win 0, length 0\
10:00:35.208162 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:39.237932 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:00:40.269642 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:00:51.191110 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:51.191172 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:00:56.973637 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:01:03.394341 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:01:15.448021 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:01:21.341961 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:01:29.763758 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:01:47.534392 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:01:48.616219 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:01:59.638511 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:01:59.638551 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:02:01.667631 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:02:06.584692 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:02:19.586637 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:02:39.337677 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:02:56.233386 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:02:57.305638 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:03:08.335765 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:08.335819 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:10.351151 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:11.922575 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:03:13.305153 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:21.435318 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:33.726134 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:03:52.614881 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:00.458869 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:05.499490 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:04:06.578226 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
plug\
10:04:32.843841 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:32.843897 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:33.201847 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:35.327642 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:36.352665 0c:c4:7a:07:d3:4c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c, length 548\
10:04:36.452722 0c:c4:7a:07:d3:4c > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 590: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 0c:c4:7a:07:d3:4c, length 548\
10:04:36.823898 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:04:37.792892 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:04:37.802532 0c:c4:7a:07:d3:4c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 86.6.30.1 tell 86.6.31.151, length 46\
10:04:37.809831 0c:c4:7a:07:d3:4c > 00:21:55:cb:93:da, ethertype IPv4 (0x0800), length 98: 86.6.31.151 > 86.6.30.1: ICMP echo request, id 15952, seq 0, length 64\
10:04:39.662854 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:04:40.149097 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:04:43.492885 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:04:51.112925 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:04:53.403180 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:01.454914 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:06.433017 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:05:16.568944 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:31.006009 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:05:32.084215 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:05:36.763168 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:05:42.991497 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:42.991550 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:46.123125 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:05:54.073136 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:05.435315 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:25.476416 0c:c4:7a:07:d3:4c > 00:21:55:cb:93:da, ethertype IPv4 (0x0800), length 60: 86.6.31.151.8090 > 85.25.103.50.48863: Flags [R.], seq 0, ack 2944169830, win 0, length 0\
10:06:26.950954 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:30.473116 0c:c4:7a:07:d3:4c > 00:21:55:cb:93:da, ethertype ARP (0x0806), length 60: Request who-has 86.6.30.1 tell 86.6.31.151, length 46\
10:06:34.705132 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:35.403556 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:06:39.277953 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:06:40.359274 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:06:51.435339 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:51.435393 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:06:56.447039 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:07:04.150797 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:07:15.495195 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:07:32.669738 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:07:48.579671 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:07:49.658274 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:08:00.441290 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:00.441346 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:02.588120 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:06.757112 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:17.938616 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:31.434178 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:08:31.636630 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:52.910109 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:08:57.189611 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:08:58.206293 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:09:09.252909 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:09.252965 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:12.441116 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:21.008108 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:31.759107 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:47.408872 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:09:59.455601 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:05.158687 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.20 tell 86.5.163.20, length 28\
10:10:06.240233 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: Request who-has 86.5.163.1 tell 86.5.163.20, length 28\
10:10:17.329407 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:17.329464 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:22.501600 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:23.884892 0c:c4:7a:07:d3:4c > 33:33:00:01:00:02, ethertype IPv6 (0x86dd), length 98: fe80::ec4:7aff:fe07:d34c.546 > ff02::1:2.547: dhcp6 inf-req\
10:10:27.418331 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:37.353627 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
10:10:46.575595 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
^X10:11:02.327114 00:22:68:1f:74:81 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:22:68:1f:74:81, length 300\
^X^C\
128 packets captured\
128 packets received by filter\
0 packets dropped by kernel}

                                          so none of this brought my WAN interface back up so I REBOOTED pfsense,

                                          the netstat upon reboot….
                                          igb4 has disappeared completely....
                                          igb5 seems to have acquired the 10.10.10.1 address pfBlockerNG is using for DNSBL filtering (still in beta)

                                          [2.2-RELEASE][admin@pfsense.irj972.local.lan]/root: netstat -rn\
Routing tables\
\
Internet:\
Destination        Gateway            Flags      Netif Expire\
10.10.10.1         link#8             UHS         lo0\
10.10.10.1/32      link#8             U          igb5\
127.0.0.1          link#13            UH          lo0\
192.168.10.0/24    link#1             U          igb0\
192.168.10.1       link#1             UHS         lo0\
192.168.50.0/24    link#8             U          igb5\
192.168.50.1       link#8             UHS         lo0\
192.168.60.0/24    link#9             U          igb6\
192.168.60.1       link#9             UHS         lo0\
192.168.70.0/24    link#10            U          igb7\
192.168.70.1       link#10            UHS         lo0\
192.168.101.0/24   link#5             U           ix0\
192.168.101.1      link#5             UHS         lo0\
192.168.110.0/24   link#6             U           ix1\
192.168.110.1      link#6             UHS         lo0\
192.168.210.0/24   192.168.210.2      UGS      ovpns2\
192.168.210.1      link#15            UHS         lo0\
192.168.210.2      link#15            UH       ovpns2\
\
Internet6:\
Destination                       Gateway                       Flags      Netif Expire\
::1                               link#13                       UH          lo0\
fe80::%igb0/64                    link#1                        U          igb0\
fe80::a236:9fff:fe2d:eba8%igb0    link#1                        UHS         lo0\
fe80::%ix0/64                     link#5                        U           ix0\
fe80::92e2:baff:fe37:fba4%ix0     link#5                        UHS         lo0\
fe80::%ix1/64                     link#6                        U           ix1\
fe80::92e2:baff:fe37:fba5%ix1     link#6                        UHS         lo0\
fe80::%igb4/64                    link#7                        U          igb4\
fe80::222:68ff:fe1f:7481%igb4     link#7                        UHS         lo0\
fe80::%igb5/64                    link#8                        U          igb5\
fe80::ec4:7aff:fe07:d551%igb5     link#8                        UHS         lo0\
fe80::%igb6/64                    link#9                        U          igb6\
fe80::ec4:7aff:fe07:d552%igb6     link#9                        UHS         lo0\
fe80::%igb7/64                    link#10                       U          igb7\
fe80::ec4:7aff:fe07:d553%igb7     link#10                       UHS         lo0\
fe80::%lo0/64                     link#13                       U           lo0\
fe80::1%lo0                       link#13                       UHS         lo0\
fe80::%ovpns2/64                  link#15                       U        ovpns2\
fe80::a236:9fff:fe2d:eba8%ovpns2  link#15                       UHS         lo0\
fe80::%ovpnc1/64                  link#16                       U        ovpnc1\
fe80::a236:9fff:fe2d:eba8%ovpnc1  link#16                       UHS         lo0\
ff01::%igb0/32                    fe80::a236:9fff:fe2d:eba8%igb0 U          igb0\
ff01::%ix0/32                     fe80::92e2:baff:fe37:fba4%ix0 U           ix0\
ff01::%ix1/32                     fe80::92e2:baff:fe37:fba5%ix1 U           ix1\
ff01::%igb4/32                    fe80::222:68ff:fe1f:7481%igb4 U          igb4\
ff01::%igb5/32                    fe80::ec4:7aff:fe07:d551%igb5 U          igb5\
ff01::%igb6/32                    fe80::ec4:7aff:fe07:d552%igb6 U          igb6\
ff01::%igb7/32                    fe80::ec4:7aff:fe07:d553%igb7 U          igb7\
ff01::%lo0/32                     ::1                           U           lo0\
ff01::%ovpns2/32                  fe80::a236:9fff:fe2d:eba8%ovpns2 U        ovpns2\
ff01::%ovpnc1/32                  fe80::a236:9fff:fe2d:eba8%ovpnc1 U        ovpnc1\
ff02::%igb0/32                    fe80::a236:9fff:fe2d:eba8%igb0 U          igb0\
ff02::%ix0/32                     fe80::92e2:baff:fe37:fba4%ix0 U           ix0\
ff02::%ix1/32                     fe80::92e2:baff:fe37:fba5%ix1 U           ix1\
ff02::%igb4/32                    fe80::222:68ff:fe1f:7481%igb4 U          igb4\
ff02::%igb5/32                    fe80::ec4:7aff:fe07:d551%igb5 U          igb5\
ff02::%igb6/32                    fe80::ec4:7aff:fe07:d552%igb6 U          igb6\
ff02::%igb7/32                    fe80::ec4:7aff:fe07:d553%igb7 U          igb7\
ff02::%lo0/32                     ::1                           U           lo0\
ff02::%ovpns2/32                  fe80::a236:9fff:fe2d:eba8%ovpns2 U        ovpns2\
ff02::%ovpnc1/32                  fe80::a236:9fff:fe2d:eba8%ovpnc1 U        ovpnc1}

                                          this is the dhcpd.log upon reboot, DHCP seems to be working fine on LANs, just WAN still dead.
                                          (I recall the LED's on pfsense and my modem are on but steady and not blinking at this stage. )

                                          
Mar  2 10:15:02 pfsense dhclient: PREINIT\
Mar  2 10:15:02 pfsense dhclient: EXPIRE\
Mar  2 10:15:02 pfsense dhclient: Deleting old routes\
Mar  2 10:15:02 pfsense dhclient: PREINIT\
Mar  2 10:15:02 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 1\
Mar  2 10:15:02 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:15:04 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:15:06 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:15:08 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:15:12 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:15:16 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 11\
Mar  2 10:15:27 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 7\
Mar  2 10:15:35 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 9\
Mar  2 10:15:44 pfsense dhclient[17672]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 14\
Mar  2 10:15:58 pfsense dhclient[17672]: No DHCPOFFERS received.\
Mar  2 10:15:58 pfsense dhclient[17672]: Trying recorded lease 86.5.163.20\
Mar  2 10:15:58 pfsense dhclient: TIMEOUT\
Mar  2 10:15:58 pfsense dhclient: Starting add_new_address()\
Mar  2 10:15:58 pfsense dhclient: ifconfig igb4 inet 86.5.163.20 netmask 255.255.255.0 broadcast 255.255.255.255\
Mar  2 10:15:58 pfsense dhclient: New IP Address (igb4): 86.5.163.20\
Mar  2 10:15:58 pfsense dhclient: New Subnet Mask (igb4): 255.255.255.0\
Mar  2 10:15:58 pfsense dhclient: New Broadcast Address (igb4): 255.255.255.255\
Mar  2 10:15:58 pfsense dhclient: New Routers (igb4): 86.5.163.1\
Mar  2 10:15:59 pfsense dhclient: New Routers (igb4): 86.5.163.1\
Mar  2 10:16:00 pfsense dhclient: Deleting old routes\
Mar  2 10:16:00 pfsense dhclient[17672]: bound: renewal in 238503 seconds.\
Mar  2 10:16:16 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:16:16 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:16:16 pfsense dhcpd: All rights reserved.\
Mar  2 10:16:16 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:16:16 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:16:16 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:16:16 pfsense dhcpd: All rights reserved.\
Mar  2 10:16:16 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:16:16 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:16:16 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:16:16 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:16:16 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:16:16 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:16:17 pfsense dhcpd: DHCPDISCOVER from 88:1f:a1:28:e5:db (irj-extreme) via igb7\
Mar  2 10:16:18 pfsense dhcpd: DHCPDISCOVER from 90:e2:ba:38:2e:3c via ix1\
Mar  2 10:16:18 pfsense dhcpd: DHCPOFFER on 192.168.110.10 to 90:e2:ba:38:2e:3c via ix1\
Mar  2 10:16:18 pfsense dhcpd: DHCPOFFER on 192.168.70.154 to 88:1f:a1:28:e5:db (irj-extreme) via igb7\
Mar  2 10:16:18 pfsense dhcpd: DHCPREQUEST for 192.168.70.154 (192.168.70.1) from 88:1f:a1:28:e5:db (irj-extreme) via igb7\
Mar  2 10:16:18 pfsense dhcpd: DHCPACK on 192.168.70.154 to 88:1f:a1:28:e5:db (irj-extreme) via igb7\
Mar  2 10:16:20 pfsense dhcpd: DHCPREQUEST for 192.168.110.10 (192.168.110.1) from 90:e2:ba:38:2e:3c via ix1\
Mar  2 10:16:20 pfsense dhcpd: DHCPACK on 192.168.110.10 to 90:e2:ba:38:2e:3c via ix1\
Mar  2 10:16:20 pfsense dhcpd: DHCPDISCOVER from 28:37:37:41:a0:f3 (ae111) via igb5\
Mar  2 10:16:21 pfsense dhcpd: DHCPOFFER on 192.168.50.135 to 28:37:37:41:a0:f3 (ae111) via igb5\
Mar  2 10:16:21 pfsense dhcpd: DHCPREQUEST for 192.168.50.135 (192.168.50.1) from 28:37:37:41:a0:f3 (ae111) via igb5\
Mar  2 10:16:21 pfsense dhcpd: DHCPACK on 192.168.50.135 to 28:37:37:41:a0:f3 (ae111) via igb5}

                                          that didn't fix it, so I rebooted the modem, leaving pfsense up…..

                                          1 Reply Last reply Reply Quote 0
                                          • Q
                                            q54e3w
                                            last edited by

                                            that didn't fix it, so I rebooted the modem, leaving pfsense up, at least this gets a DHCPACK back now.

                                            The virgin modem appears to boot in router mode, assigns itself 192.168.100.1 and then transitions at some point shortly after to routing mode and passes through the public IP (something like a 213.81.x.x… or 85.3.x.x...)
                                            I wonder if this 100.1 assignment is causing some DHCP weirdness as the modem goes through its initialisation and various boot up addresses?

                                            
Mar  2 10:27:36 pfsense dhclient: ARPSEND\
Mar  2 10:27:38 pfsense dhclient: ARPCHECK\
Mar  2 10:27:38 pfsense dhclient[98982]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:27:39 pfsense dhclient[98982]: DHCPACK from 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: BOUND\
Mar  2 10:27:39 pfsense dhclient: Starting add_new_address()\
Mar  2 10:27:39 pfsense dhclient: ifconfig igb4 inet 192.168.100.2 netmask 255.255.255.0 broadcast 192.168.100.255\
Mar  2 10:27:39 pfsense dhclient: New IP Address (igb4): 192.168.100.2\
Mar  2 10:27:39 pfsense dhclient: New Subnet Mask (igb4): 255.255.255.0\
Mar  2 10:27:39 pfsense dhclient: New Broadcast Address (igb4): 192.168.100.255\
Mar  2 10:27:39 pfsense dhclient: New Routers (igb4): 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: Adding new routes to interface: igb4\
Mar  2 10:27:39 pfsense dhclient: /sbin/route add default 192.168.100.1\
Mar  2 10:27:39 pfsense dhclient: Creating resolv.conf\
Mar  2 10:27:39 pfsense dhclient[98982]: bound to 192.168.100.2 -- renewal in 30 seconds.\
Mar  2 10:28:09 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:11 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:14 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:17 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:24 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 192.168.100.1 port 67\
Mar  2 10:28:35 pfsense dhcpd: Received signal 15, initiating shutdown.\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling output on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:35 pfsense dhcpd: Disabling input on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhclient[40839]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:28:36 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:28:36 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:28:36 pfsense dhcpd: All rights reserved.\
Mar  2 10:28:36 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:28:36 pfsense dhcpd: Internet Systems Consortium DHCP Server 4.2.6\
Mar  2 10:28:36 pfsense dhcpd: Copyright 2004-2014 Internet Systems Consortium.\
Mar  2 10:28:36 pfsense dhcpd: All rights reserved.\
Mar  2 10:28:36 pfsense dhcpd: For info, please visit https://www.isc.org/software/dhcp/\
Mar  2 10:28:36 pfsense dhcpd: Wrote 0 deleted host decls to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Wrote 0 new dynamic host decls to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Wrote 45 leases to leases file.\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb0/a0:36:9f:2d:eb:a8/192.168.10.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/ix1/90:e2:ba:37:fb:a5/192.168.110.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/ix0/90:e2:ba:37:fb:a4/192.168.101.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb6/0c:c4:7a:07:d5:52/192.168.60.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb7/0c:c4:7a:07:d5:53/192.168.70.0/24\
Mar  2 10:28:36 pfsense dhcpd: Listening on BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   BPF/igb5/0c:c4:7a:07:d5:51/192.168.50.0/24\
Mar  2 10:28:36 pfsense dhcpd: Sending on   Socket/fallback/fallback-net\
Mar  2 10:28:36 pfsense dhclient[1281]: connection closed\
Mar  2 10:28:36 pfsense dhclient[1281]: exiting.\
Mar  2 10:28:42 pfsense dhclient: PREINIT\
Mar  2 10:28:42 pfsense dhclient[80861]: DHCPREQUEST on igb4 to 255.255.255.255 port 67\
Mar  2 10:28:43 pfsense dhclient: EXPIRE\
Mar  2 10:28:43 pfsense dhclient: Deleting old routes\
Mar  2 10:28:43 pfsense dhclient: PREINIT\
Mar  2 10:28:43 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 1\
Mar  2 10:28:44 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 1\
Mar  2 10:28:45 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 2\
Mar  2 10:28:47 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 4\
Mar  2 10:28:51 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 8\
Mar  2 10:28:59 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 17\
Mar  2 10:29:16 pfsense dhclient[80861]: DHCPDISCOVER on igb4 to 255.255.255.255 port 67 interval 16}

                                            again still no joy, so I disconnected the coastal line, waited a few minutes and reconnected….

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.