WAN not getting IP address on reboot
-
Greetings,
I have 2 pfSense boxes that are having the same problem that they do not get a DHCP address on the WAN interface after any reboot. Both of these boxes are connected to a Rogers cable service without a static IP address. This started happening a few months ago but has started to become a problem with more summer power outages.
The fix I have been using is to manually log into the GUI and disable/enable the WAN interface and it picks up an IP without any issues and is fine until the next reboot.
In addition, it appears that this might be a issue related specifically to Rogers non-static accounts as I have another box I manage on Rogers with a static IP address and no issues with that one and at my house I have cable internet with a 3rd party over Rogers lines and no issues there either.
Any one else having this issue and any suggestions on how to resolve thiis.
Cheers
-
As always, packet captures help. Shut down pfsense and disconnect the WAN cable. Then start it up and run Packet Capture, filtering on DHCP. Next, reconnect the WAN cable. You can then download the capture.
-
@jknott I followed directions and I have included the packet capture but I am not sure that this will help as the WAN received an IP address as soon as I connected the cable.
Please let me know your thoughts.
Cheers!
11:43:24.865796 ARP, Request who-has 198.2.89.96 tell 198.2.89.97, length 46
11:43:24.869614 ARP, Request who-has 99.253.138.88 tell 99.253.138.1, length 46
11:43:24.873590 ARP, Request who-has 172.86.194.207 tell 172.86.194.193, length 46
11:43:24.876541 ARP, Request who-has 99.253.142.198 tell 99.253.142.1, length 46
11:43:24.877489 ARP, Request who-has 99.253.137.18 tell 99.253.136.1, length 46
11:43:24.879490 ARP, Request who-has 99.253.139.27 tell 99.253.138.1, length 46
11:43:24.888645 ARP, Request who-has 38.121.92.185 tell 38.121.92.161, length 46
11:43:24.889515 ARP, Request who-has 99.253.139.232 tell 99.253.138.1, length 46
11:43:24.891467 ARP, Request who-has 209.204.203.158 tell 209.204.203.129, length 46
11:43:24.919897 ARP, Request who-has 64.58.45.76 tell 64.58.45.65, length 46
11:43:24.927673 ARP, Request who-has 38.121.92.187 tell 38.121.92.161, length 46
11:43:24.966629 ARP, Request who-has 99.253.156.141 tell 99.253.156.1, length 46
11:43:24.983556 ARP, Request who-has 99.253.143.234 tell 99.253.142.1, length 46
11:43:24.985606 ARP, Request who-has 99.253.143.220 tell 99.253.142.1, length 46
11:43:25.000535 ARP, Request who-has 99.253.156.159 tell 99.253.156.1, length 46
11:43:25.003508 ARP, Request who-has 24.105.108.149 tell 24.105.108.129, length 46
11:43:25.010559 ARP, Request who-has 198.2.89.62 tell 198.2.89.33, length 46
11:43:25.011034 ARP, Request who-has 99.253.141.83 tell 99.253.140.1, length 46
11:43:25.011559 ARP, Request who-has 99.253.135.140 tell 99.253.134.1, length 46
11:43:25.012510 ARP, Request who-has 99.253.133.212 tell 99.253.132.1, length 46
11:43:25.014484 ARP, Request who-has 99.253.139.9 tell 99.253.138.1, length 46
11:43:25.021536 ARP, Request who-has 148.64.95.88 tell 148.64.95.65, length 46
11:43:25.029536 ARP, Request who-has 99.253.119.185 tell 99.253.118.1, length 46
11:43:25.033512 ARP, Request who-has 99.253.137.143 tell 99.253.136.1, length 46
11:43:25.062543 ARP, Request who-has 99.253.143.120 tell 99.253.142.1, length 46
11:43:25.068568 ARP, Request who-has 99.253.142.123 tell 99.253.142.1, length 46
11:43:25.108576 ARP, Request who-has 149.248.108.150 tell 149.248.108.129, length 46
11:43:25.120575 ARP, Request who-has 149.248.108.155 tell 149.248.108.129, length 46
11:43:25.121381 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 80
11:43:25.121422 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121507 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121522 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121535 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121552 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121638 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121653 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121665 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121678 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.121771 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.139579 ARP, Request who-has 107.189.253.20 tell 107.189.253.1, length 46
11:43:25.143553 ARP, Request who-has 99.253.141.130 tell 99.253.140.1, length 46
11:43:25.157580 ARP, Request who-has 99.253.137.93 tell 99.253.136.1, length 46
11:43:25.178610 ARP, Request who-has 99.253.138.206 tell 99.253.138.1, length 46
11:43:25.222590 ARP, Request who-has 149.248.108.142 tell 149.248.108.129, length 46
11:43:25.224564 ARP, Request who-has 99.253.135.104 tell 99.253.134.1, length 46
11:43:25.225640 ARP, Request who-has 99.253.141.128 tell 99.253.140.1, length 46
11:43:25.232566 ARP, Request who-has 209.204.195.105 tell 209.204.195.97, length 46
11:43:25.252619 ARP, Request who-has 64.58.45.73 tell 64.58.45.65, length 46
11:43:25.253543 ARP, Request who-has 99.253.143.100 tell 99.253.142.1, length 46
11:43:25.272597 ARP, Request who-has 99.253.143.77 tell 99.253.142.1, length 46
11:43:25.286600 ARP, Request who-has 99.253.135.214 tell 99.253.134.1, length 46
11:43:25.289552 ARP, Request who-has 198.91.152.60 tell 198.91.152.33, length 46
11:43:25.302589 ARP, Request who-has 99.253.139.101 tell 99.253.138.1, length 46
11:43:25.303129 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
11:43:25.303130 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
11:43:25.303131 IP6 :: > ff02::1:ff03:32cd: ICMP6, neighbor solicitation, who has fe80::7e8b:caff:fe03:32cd, length 32
11:43:25.303132 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 2 group record(s), length 48
11:43:25.303133 IP6 fe80::7e8b:caff:fe03:32cd > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
11:43:25.315742 ARP, Request who-has 99.253.157.229 tell 99.253.156.1, length 46
11:43:25.317609 ARP, Request who-has 99.253.157.69 tell 99.253.156.1, length 46
11:43:25.340608 ARP, Request who-has 99.253.138.167 tell 99.253.138.1, length 46
11:43:25.342557 ARP, Request who-has 99.253.135.208 tell 99.253.134.1, length 46
11:43:25.345682 ARP, Request who-has 99.253.157.136 tell 99.253.156.1, length 46
11:43:25.348580 ARP, Request who-has 99.253.141.127 tell 99.253.140.1, length 46
11:43:25.356592 ARP, Request who-has 38.141.165.145 tell 38.141.165.129, length 46
11:43:25.440699 ARP, Request who-has 99.253.135.160 tell 99.253.134.1, length 46
11:43:25.489680 ARP, Request who-has 99.253.140.88 tell 99.253.140.1, length 46
11:43:25.502633 ARP, Request who-has 99.253.157.243 tell 99.253.156.1, length 46
11:43:25.520633 ARP, Request who-has 99.253.157.200 tell 99.253.156.1, length 46
11:43:25.606774 ARP, Request who-has 216.181.96.63 tell 216.181.96.33, length 46
11:43:25.612772 ARP, Request who-has 24.105.108.155 tell 24.105.108.129, length 46
11:43:25.624774 ARP, Request who-has 99.253.143.11 tell 99.253.142.1, length 46
11:43:25.637800 ARP, Request who-has 104.204.61.156 tell 104.204.61.129, length 46
11:43:25.645383 IP 45.74.96.151.1197 > 99.253.141.175.1197: UDP, length 96
11:43:25.652803 ARP, Request who-has 72.137.112.29 tell 72.137.112.1, length 46
11:43:25.659778 ARP, Request who-has 99.253.137.154 tell 99.253.136.1, length 46
11:43:25.677756 ARP, Request who-has 99.253.141.240 tell 99.253.140.1, length 46
11:43:25.691791 ARP, Request who-has 45.2.14.148 tell 45.2.14.129, length 46
11:43:25.707793 ARP, Request who-has 149.248.108.158 tell 149.248.108.129, length 46
11:43:25.708634 ARP, Request who-has 99.253.142.136 tell 99.253.142.1, length 46
11:43:25.709735 ARP, Request who-has 99.253.135.209 tell 99.253.134.1, length 46
11:43:25.721786 ARP, Request who-has 99.253.140.226 tell 99.253.140.1, length 46
11:43:25.755941 ARP, Request who-has 99.253.141.213 tell 99.253.140.1, length 46
11:43:25.778798 ARP, Request who-has 198.2.89.74 tell 198.2.89.65, length 46
11:43:25.805926 ARP, Request who-has 99.253.141.140 tell 99.253.140.1, length 46
11:43:25.820830 ARP, Request who-has 99.253.157.61 tell 99.253.156.1, length 46
11:43:25.821629 ARP, Request who-has 99.253.139.136 tell 99.253.138.1, length 46
11:43:25.841836 ARP, Request who-has 99.253.157.224 tell 99.253.156.1, length 46
11:43:25.849814 ARP, Request who-has 99.253.157.216 tell 99.253.156.1, length 46
11:43:25.873764 ARP, Request who-has 107.179.181.6 tell 107.179.181.1, length 46
11:43:25.875761 ARP, Request who-has 99.253.137.215 tell 99.253.136.1, length 46
11:43:25.908818 ARP, Request who-has 148.64.95.75 tell 148.64.95.65, length 46
11:43:25.913814 ARP, Request who-has 99.253.135.187 tell 99.253.134.1, length 46
11:43:25.925967 ARP, Request who-has 99.253.141.156 tell 99.253.140.1, length 46
11:43:25.926665 ARP, Request who-has 99.253.137.112 tell 99.253.136.1, length 46
11:43:25.927717 ARP, Request who-has 99.253.136.241 tell 99.253.136.1, length 46
11:43:25.950821 ARP, Request who-has 99.253.139.13 tell 99.253.138.1, length 46
11:43:25.958848 ARP, Request who-has 99.253.157.213 tell 99.253.156.1, length 46
11:43:25.961797 ARP, Request who-has 99.253.156.252 tell 99.253.156.1, length 46
11:43:25.966047 ARP, Request who-has 216.181.96.28 tell 216.181.96.1, length 46 -
If DHCP works after the computer has been up for a while, but not when first boot up, that might be a hardware issue, but given it happens with 2 that's not a likely. I'm on Rogers and don't have that problem. Where are you located? There could be an issue with an individual head end. I experienced that on IPv6. What happens if you connect a computer directly to the modem? Also what hardware are you running pfsense on? One other thing you could try is to capture DHCP using a data tap so that you can see what happens without using the method I described above.
-
You had a few questions in there so let me try to respond to them all.
- Both of these locations are in Brantford, Ontario
- Yes I have connected my laptop directly to the modem and I get an address on boot
- These are both running on repurposed intel processor based PCs. One location using an intel quad and the other is using the internal NIC and a Realtek NIC.
As for the hardware issue, I had thought about that and in my one box, I switched the WAN/LAN adapters and tried a reboot and had the same issue.
One other thing to note, until last week, these 2 boxes were on different versions. The one location was running 2.45 until last week when I upgraded to 2.52. The second location where my office is, has been having this while running 2.5.0, 2.5.1 and 2.5.2.
I will see if I can build a data trap next week to capture what is happening and let you know.
Cheers
-
I currently use the hardware described in my sig but previously used an old HP computer.
-
BTW, how's IPv6 on those two?
-
So I set up a data trap as you suggested and as per usual with me, installing the trap caused my office setup to pickup a DHCP address right away both with a reboot of the pfSense box and simulated power failure where both boxes lost power.
I'm not sure what to think now. Any thoughts?
And I do not use IPv6 so I can't comment on that.
Cheers
-
@bhollingsworth said in WAN not getting IP address on reboot:
I'm not sure what to think now. Any thoughts?
Does it still fail when the data tap isn't connected? If so, that would tend to indicate a hardware problem, which it masked by it.
And I do not use IPv6 so I can't comment on that.
Well, why not give it a try? You'll have to move to it some time.