Gateways "Pending", no WAN access on fresh 2.3Release install
I've done a fresh install of 2.3 Release (several times actually) each time with the same result. The ipv4 gateway is "Pending", IPv6 gateway is "offline" and I have no internet access. I can ping the pfsense box fine and also ssh into it fine. The offense is plugged directly into my cable modem. I've checked the modem by plugging it directly into a laptop and it works fine btw.
I'm having to browse this forum on my cell phone, but gateway log is below
Under System/Routing/Gateways says "dynamic" and is blank for Monitor IP
14 12:43:40 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::201:5cff:fe67:8a46%igb0 bind_addr fe80::ec4:7aff:feaa:eb84%igb0 identifier "WAN_DHCP6 "
Apr 14 12:43:43 dpinger WAN_DHCP6 fe80::201:5cff:fe67:8a46%igb0: Alarm latency 0us stddev 0us loss 100%
Apr 14 12:44:23 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::201:5cff:fe67:8a46%igb0 bind_addr fe80::ec4:7aff:feaa:eb84%igb0 identifier "WAN_DHCP6 "
Apr 14 12:44:26 dpinger WAN_DHCP6 fe80::201:5cff:fe67:8a46%igb0: Alarm latency 0us stddev 0us loss 100%
Please let me know what else you need to know. Thanks in advance for any help.
coxhaus last edited by
I assume you have the WAN interface on pfsense set for DHCP. You should probably unplug your modem wait a couple of minutes and then plug it in. Once it boots up reboot pfsense. Do you have an outside public IP address on pfsense?
Switching MACs like using your windows machine with a modem can require unplugging the modem.
Yes WAN is dhcp. I unplugged/rep lugged the modem, and rebooted pfsense box, no change still same issue.
I did notice when logged in via ssh I re-assigned the interfaces and it said "can't open /bar/unbound/root.key" haven't seen that before.
Have disconnected the modem several times now and no change. FYI when I hook back up my ASUS router it works fine..
coxhaus last edited by
Has this box been running an older pfsense before or is this new hardware for pfsense.?
Do you have good link lights on modem and pfsense?
It is a relatively new build (see specs in sig) on which I ran 2.2.6 for a few weeks. I then upgraded to the 2.3RC track and it ran fine for about 2 weeks. Then randomly one morning the interfaces went down with this exact same issue and I could not get it back up.
Having a important business project at that time I had to switch back to my ASUS router for a week or two. Yesterday I fresh installed the 2.3Release on the pfsense box and have these same issues again.
cmb last edited by
You're not getting an IP. Most likely because you're switching devices. Most of the time a power cycle of your modem after unplugging the old device and before plugging in the new will suffice to get an IP on the new system. Where that's problematic, spoofing the MAC of your other router's WAN NIC on the WAN interface is easiest.
Well dadgum! Got it working.
I did 2 things: 1. Switched the WAN to 1gb1 from igb0. 2. Found that a Cat6A cable was being used from the modem to the router so I switched it to Cat5e. One of those two worked, I'm guessing the Cat5e cable. I'll switch the interface back to igb0 at another date…
Thanks for your time and help coxhaus and cmb, I know you are busy right now :)