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

    WAN interfaces fail to return after power outage

    Scheduled Pinned Locked Moved
    General pfSense Questions
    4
    49
    6.5k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      I up-voted enough of your posts that you should not get hit by Akismet again.

      Do you see anything logged showing it getting the 0.0.0.0 address? It looks like the WAN doesn't come back up because it sees that as a valid address. If something giving that to it you can exclude a particular DHCP server as a source.

      Steve

      1 Reply Last reply Reply Quote 1
      • P
        peter_richardson
        last edited by

        Thanks Stephen!

        So you're saying that it appears that pfSense is giving the WWAN interface the address of 0.0.0.0?

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

          No, more likely it's something upstream giving it that before the connection comes up. Cable modems do that with monotonous regularity. 🙄 But I'm not sure what sort of hand-off you have. I know NBN can be several different things.
          If that is the case though you should see something logged in the DHCP logs as the dhclient pulls the bad address.

          Steve

          1 Reply Last reply Reply Quote 0
          • P
            peter_richardson
            last edited by

            I see. No, the WWAN isn't NBN, the WWAN is 4G with a Telstra SIM card, using a Netgear Nighthawk M1.

            So changing the WWAN interface from DHCP to static with an IP address that is in the M1's usual DHCP range should fix this. IE: set the IP to 192.168.0.50 but alas, it just shows on the dashboard as "gateway down". So it looks like this isn't the issue. In fact, once I set the IP to static, it didn't work at all, which makes me wonder what is going on since previously, any changes to the WWAN connection would make the connection come back online, and giving it a static address shouldn't prevent it from working under normal conditions, so long as the address is within the M1's normal DHCP range. 😕

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

              Hmm, well the DHCP logs should still show if the bad address is coming from somewhere upstream. If it's coming from a different DHCP server you can block it as a source and the client will continue to look for other servers. That works well with cable modems that do this.
              Anyway check the logs for 0.0.0.0 messages.

              Steve

              1 Reply Last reply Reply Quote 0
              • P
                peter_richardson
                last edited by peter_richardson

                I can't see anything in the DHCP logs for 0.0.0.0 I even lengthened the log to 1,000 entries, which took me back to about 11am today, should I go back further?
                Here's what's in there, I can't make much sense of it, can you?
                what's the "fail" all about?

                Nov 16 13:20:13	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 16 13:20:14	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:20:16	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 3
Nov 16 13:20:19	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 16 13:20:24	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 16 13:20:37	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 16 13:20:51	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 16 13:21:03	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 16 13:21:11	dhclient	99656	No DHCPOFFERS received.
Nov 16 13:21:11	dhclient	99656	No working leases in persistent database - sleeping.
Nov 16 13:21:11	dhclient		FAIL
Nov 16 13:21:26	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 16 13:21:27	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 16 13:21:28	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:21:30	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:21:32	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 16 13:21:38	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 16 13:21:52	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 16 13:22:03	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 16 13:22:11	dhcpd		DHCPREQUEST for 10.20.63.134 from 80:5e:c0:07:7f:9c (W60B) via igb3
Nov 16 13:22:11	dhcpd		DHCPACK on 10.20.63.134 to 80:5e:c0:07:7f:9c (W60B) via igb3
Nov 16 13:22:19	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 16 13:22:27	dhclient	99656	No DHCPOFFERS received.
Nov 16 13:22:27	dhclient	99656	No working leases in persistent database - sleeping.
Nov 16 13:22:27	dhclient		FAIL
Nov 16 13:22:42	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 16 13:22:43	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:22:45	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 16 13:22:49	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 16 13:22:58	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 21
Nov 16 13:23:19	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 16 13:23:36	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 7
Nov 16 13:23:43	dhclient	99656	No DHCPOFFERS received.
Nov 16 13:23:43	dhclient	99656	No working leases in persistent database - sleeping.
Nov 16 13:23:43	dhclient		FAIL
Nov 16 13:23:58	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:24:00	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 16 13:24:05	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 16 13:24:13	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 16 13:24:29	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 19
Nov 16 13:24:48	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 16 13:24:59	dhclient	99656	No DHCPOFFERS received.
Nov 16 13:24:59	dhclient	99656	No working leases in persistent database - sleeping.
Nov 16 13:24:59	dhclient		FAIL
Nov 16 13:25:14	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 16 13:25:16	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 16 13:25:21	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 16 13:25:30	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 16 13:25:40	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 16 13:25:52	dhclient	99656	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 15
                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Hmm, disappointing. The fail simply indicates the dhcp client failed to get get a lease from a server after completing its sequence and starts again after a pause.

                  Does the Nigthhawk log anything for this connection or is it entirely bridging?

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • P
                    peter_richardson
                    last edited by

                    I will have a look but I'm not holding my breath for any decent logging in a Netgear piece of equipment. I don't think this is a Netgear problem though, it doesn't happen with any other device such as a laptop. You can restart the laptop and it gets an IP address just fine. It's only when pfSense is restarted that this happens. And it's not just isolated to the Netgear device, it also happens with the WAN connection - so both connections fail to come back when the router is restarted. If the power goes off or I need to reboot the router for any reason, I have to go into the router, disable the interfaces and then re-enable the interfaces for them to work again.

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

                      Had to re-read the thread as I'd assumed it was a powerfailure on the upstream devices the prevented it connecting. Not connecting to either WAN after rebooting pfSense is even more weird.

                      Can you restore the connection by pulling the cable and reconnecting it? Or does it need logically disabled while remaining connected?

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • P
                        peter_richardson
                        last edited by

                        Unplugging and replugging also works the same as disabling and re enabling the interface. It comes back online and gets correct ip address.

                        1 Reply Last reply Reply Quote 0
                        • P
                          peter_richardson
                          last edited by

                          please help :-)

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

                            I think a packet capture showing the client failing to get a lease is the next step here.
                            Do you see anything coming back from the DHCP server at all?

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • P
                              peter_richardson
                              last edited by peter_richardson

                              Thanks Steve. Sorry, as I'm not a total expert (yet), can you please break it down for me a bit?

                              Packet capture - from within pfSense? (as in Diagnostics -> Packet Capture?) If so, what settings do I use?

                              ps - I just found a display bug - I'm using Chrome on a Mac - there are more options in Diagnostics that I can't access because I'd have to scroll, but even if I scroll to the bottom of the page, I can't scroll the dropdown menu from Diagnostics (see attached image). Also, it's worse if the "downloads" bar is visible at the bottom of the Chrome window, it covers up the last one or two options in the Diagnostics menu.
                              0_1542922958038_Screenshot 2018-11-23 08.40.15.png

                              I just checked the DHCP log, here's what it shows: (see below) Is it the Netgear that's not giving out an address via DHCP? Because it will if I connect my laptop to it via WiFi. There is definitely a link light on the ethernet port of the router that is connected to the Netgear, and occasionally the activity light will blink.

                              Nov 23 14:54:12	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:54:13	dhclient	84923	No DHCPOFFERS received.
Nov 23 14:54:13	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 14:54:13	dhclient		FAIL
Nov 23 14:54:28	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:54:29	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:54:31	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 14:54:36	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 14:54:42	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 23 14:54:51	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 19
Nov 23 14:55:10	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 14:55:23	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 14:55:29	dhclient	84923	No DHCPOFFERS received.
Nov 23 14:55:29	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 14:55:29	dhclient		FAIL
Nov 23 14:55:44	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:55:45	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:55:46	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:55:47	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:55:49	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 14:55:54	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 14:56:07	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 23 14:56:23	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 23 14:56:32	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 23 14:56:43	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:56:45	dhclient	84923	No DHCPOFFERS received.
Nov 23 14:56:45	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 14:56:45	dhclient		FAIL
Nov 23 14:57:00	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 14:57:01	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:57:03	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 14:57:07	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 14:57:12	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 14:57:17	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 14:57:30	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 14:57:43	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 23 14:57:57	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 14:58:01	dhclient	84923	No DHCPOFFERS received.
Nov 23 14:58:01	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 14:58:01	dhclient		FAIL
Nov 23 14:58:16	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:58:18	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 14:58:22	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 23 14:58:33	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 10
Nov 23 14:58:43	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 20
Nov 23 14:59:03	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 14:59:11	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 14:59:17	dhclient	84923	No DHCPOFFERS received.
Nov 23 14:59:17	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 14:59:17	dhclient		FAIL
Nov 23 14:59:32	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 14:59:34	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 3
Nov 23 14:59:37	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 14:59:43	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 23 14:59:46	dhcpd		DHCPREQUEST for 10.20.63.33 from ac:37:43:e8:50:4a (android-5482cd93fd6e378c) via igb3
Nov 23 14:59:46	dhcpd		DHCPACK on 10.20.63.33 to ac:37:43:e8:50:4a (android-5482cd93fd6e378c) via igb3
Nov 23 14:59:52	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:00:05	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 23 15:00:19	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 10
Nov 23 15:00:29	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:00:33	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:00:33	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:00:33	dhclient		FAIL
Nov 23 15:00:48	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:00:49	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:00:51	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 3
Nov 23 15:00:54	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:00:58	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 15:01:04	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 23 15:01:16	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:01:29	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 23 15:01:41	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 15:01:49	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:01:49	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:01:49	dhclient		FAIL
Nov 23 15:02:04	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:02:05	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:02:07	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:02:09	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:02:14	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:02:19	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 23 15:02:28	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 19
Nov 23 15:02:47	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 23 15:03:03	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:03:05	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:03:05	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:03:05	dhclient		FAIL
Nov 23 15:03:20	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:03:22	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:03:26	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 9
Nov 23 15:03:35	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 21
Nov 23 15:03:56	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 23 15:04:10	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 23 15:04:21	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:04:21	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:04:21	dhclient		FAIL
Nov 23 15:04:36	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:04:37	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:04:38	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:04:39	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:04:41	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:04:45	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 15:04:51	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 15
Nov 23 15:05:07	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 23 15:05:19	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 23 15:05:33	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:05:38	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:05:38	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:05:38	dhclient		FAIL
Nov 23 15:05:53	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:05:54	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:05:55	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:05:56	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:05:58	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:06:00	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:06:05	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:06:10	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 14
Nov 23 15:06:24	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 17
Nov 23 15:06:41	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:06:54	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:06:54	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:06:54	dhclient		FAIL
Nov 23 15:07:09	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:07:10	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:07:12	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:07:16	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 15:07:24	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 23 15:07:36	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 17
Nov 23 15:07:53	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 17
Nov 23 15:08:10	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:08:10	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:08:10	dhclient		FAIL
Nov 23 15:08:25	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:08:27	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:08:31	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:08:36	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 15:08:42	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:08:55	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 15:09:03	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 10
Nov 23 15:09:13	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 7
Nov 23 15:09:20	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 6
Nov 23 15:09:26	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:09:26	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:09:26	dhclient		FAIL
Nov 23 15:09:30	dhcpd		DHCPREQUEST for 10.20.63.35 from e8:99:c4:7e:78:7b (android-aaa02c5bc3d65de) via igb3
Nov 23 15:09:30	dhcpd		DHCPACK on 10.20.63.35 to e8:99:c4:7e:78:7b (android-aaa02c5bc3d65de) via igb3
Nov 23 15:09:41	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:09:42	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:09:44	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:09:49	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:10:02	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 19
Nov 23 15:10:21	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 13
Nov 23 15:10:34	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 15:10:42	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:10:42	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:10:42	dhclient		FAIL
Nov 23 15:10:57	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 1
Nov 23 15:10:58	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:11:00	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:11:04	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 7
Nov 23 15:11:11	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 16
Nov 23 15:11:27	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 12
Nov 23 15:11:39	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 8
Nov 23 15:11:47	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 23 15:11:58	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:11:58	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:11:58	dhclient		FAIL
Nov 23 15:12:13	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:12:15	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 4
Nov 23 15:12:19	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 10
Nov 23 15:12:29	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 17
Nov 23 15:12:46	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 17
Nov 23 15:13:03	dhclient	84923	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 11
Nov 23 15:13:14	dhclient	84923	No DHCPOFFERS received.
Nov 23 15:13:14	dhclient	84923	No working leases in persistent database - sleeping.
Nov 23 15:13:14	dhclient		FAIL

                              I just noticed that new firmware was available for it so I updated it and after a couple of reboots, it's back online. Here's the log from DHCP in pfSense:

                              Nov 23 15:45:13	dhclient	81089	No DHCPOFFERS received.
Nov 23 15:45:13	dhclient	81089	No working leases in persistent database - sleeping.
Nov 23 15:45:13	dhclient		FAIL
Nov 23 15:45:25	dhclient	81089	igb1 link state up -> down
Nov 23 15:45:26	dhclient	57640	connection closed
Nov 23 15:45:26	dhclient	57640	exiting.
Nov 23 15:45:42	dhcpd		reuse_lease: lease age 854 (secs) under 25% threshold, reply with unaltered, existing lease for 10.20.63.133
Nov 23 15:45:42	dhcpd		DHCPREQUEST for 10.20.63.133 from a0:99:9b:14:37:55 (Petes-MBP) via igb3
Nov 23 15:45:42	dhcpd		DHCPACK on 10.20.63.133 to a0:99:9b:14:37:55 (Petes-MBP) via igb3
Nov 23 15:46:02	dhclient		PREINIT
Nov 23 15:46:02	dhclient		EXPIRE
Nov 23 15:46:02	dhclient		Deleting old routes
Nov 23 15:46:02	dhclient		PREINIT
Nov 23 15:46:02	dhclient	71272	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 2
Nov 23 15:46:04	dhclient	71272	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 3
Nov 23 15:46:07	dhclient	71272	DHCPDISCOVER on igb1 to 255.255.255.255 port 67 interval 5
Nov 23 15:46:10	dhclient	71272	DHCPOFFER from 192.168.1.1
Nov 23 15:46:10	dhclient	71272	unknown dhcp option value 0x78
Nov 23 15:46:10	dhclient		ARPSEND
Nov 23 15:46:13	dhclient		ARPCHECK
Nov 23 15:46:13	dhclient	71272	DHCPREQUEST on igb1 to 255.255.255.255 port 67
Nov 23 15:46:13	dhclient	71272	DHCPACK from 192.168.1.1
Nov 23 15:46:13	dhclient	71272	unknown dhcp option value 0x78
Nov 23 15:46:13	dhclient		BOUND
Nov 23 15:46:13	dhclient		Starting add_new_address()
Nov 23 15:46:13	dhclient		ifconfig igb1 inet 192.168.1.46 netmask 255.255.255.0 broadcast 192.168.1.255
Nov 23 15:46:13	dhclient		New IP Address (igb1): 192.168.1.46
Nov 23 15:46:13	dhclient		New Subnet Mask (igb1): 255.255.255.0
Nov 23 15:46:13	dhclient		New Broadcast Address (igb1): 192.168.1.255
Nov 23 15:46:13	dhclient		New Routers (igb1): 192.168.1.1
Nov 23 15:46:13	dhclient		Adding new routes to interface: igb1
Nov 23 15:46:13	dhclient		Creating resolv.conf
Nov 23 15:46:13	dhclient	71272	bound to 192.168.1.46 -- renewal in 21600 seconds.
Nov 23 15:46:16	dhcpd		Internet Systems Consortium DHCP Server 4.3.6-P1
Nov 23 15:46:16	dhcpd		Copyright 2004-2018 Internet Systems Consortium.
Nov 23 15:46:16	dhcpd		All rights reserved.
Nov 23 15:46:16	dhcpd		For info, please visit https://www.isc.org/software/dhcp/
Nov 23 15:46:16	dhcpd		Config file: /etc/dhcpd.conf
Nov 23 15:46:16	dhcpd		Database file: /var/db/dhcpd.leases
Nov 23 15:46:16	dhcpd		PID file: /var/run/dhcpd.pid
Nov 23 15:46:16	dhcpd		Internet Systems Consortium DHCP Server 4.3.6-P1
Nov 23 15:46:16	dhcpd		Copyright 2004-2018 Internet Systems Consortium.
Nov 23 15:46:16	dhcpd		All rights reserved.
Nov 23 15:46:16	dhcpd		For info, please visit https://www.isc.org/software/dhcp/
Nov 23 15:46:16	dhcpd		Wrote 0 deleted host decls to leases file.
Nov 23 15:46:16	dhcpd		Wrote 0 new dynamic host decls to leases file.
Nov 23 15:46:16	dhcpd		Wrote 73 leases to leases file.
Nov 23 15:46:16	dhcpd		Listening on BPF/igb3/00:0e:c4:d2:10:2c/10.20.63.0/24
Nov 23 15:46:16	dhcpd		Sending on BPF/igb3/00:0e:c4:d2:10:2c/10.20.63.0/24
Nov 23 15:46:16	dhcpd		Sending on Socket/fallback/fallback-net
Nov 23 15:46:16	dhcpd		Server starting service.
Nov 23 15:46:20	dhcpd		Internet Systems Consortium DHCP Server 4.3.6-P1
Nov 23 15:46:20	dhcpd		Copyright 2004-2018 Internet Systems Consortium.
Nov 23 15:46:20	dhcpd		All rights reserved.
Nov 23 15:46:20	dhcpd		For info, please visit https://www.isc.org/software/dhcp/
Nov 23 15:46:20	dhcpd		Config file: /etc/dhcpd.conf
Nov 23 15:46:20	dhcpd		Database file: /var/db/dhcpd.leases
Nov 23 15:46:20	dhcpd		PID file: /var/run/dhcpd.pid
Nov 23 15:46:20	dhcpd		Internet Systems Consortium DHCP Server 4.3.6-P1
Nov 23 15:46:20	dhcpd		Copyright 2004-2018 Internet Systems Consortium.
Nov 23 15:46:20	dhcpd		All rights reserved.
Nov 23 15:46:20	dhcpd		For info, please visit https://www.isc.org/software/dhcp/
Nov 23 15:46:20	dhcpd		Wrote 0 deleted host decls to leases file.
Nov 23 15:46:20	dhcpd		Wrote 0 new dynamic host decls to leases file.
Nov 23 15:46:20	dhcpd		Wrote 73 leases to leases file.
Nov 23 15:46:20	dhcpd		Listening on BPF/igb3/00:0e:c4:d2:10:2c/10.20.63.0/24
Nov 23 15:46:20	dhcpd		Sending on BPF/igb3/00:0e:c4:d2:10:2c/10.20.63.0/24
Nov 23 15:46:20	dhcpd		Sending on Socket/fallback/fallback-net
Nov 23 15:46:20	dhcpd		Server starting service.
Nov 23 15:55:36	dhcpd		reuse_lease: lease age 1448 (secs) under 25% threshold, reply with unaltered, existing lease for 10.20.63.133
Nov 23 15:55:36	dhcpd		DHCPREQUEST for 10.20.63.133 from a0:99:9b:14:37:55 (Petes-MBP) via igb3
Nov 23 15:55:36	dhcpd		DHCPACK on 10.20.63.133 to a0:99:9b:14:37:55 (Petes-MBP) via igb3
                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post