Can't obtain external IP on WAN interface
-
What exactly do they need to do?
-
Better question for them. They should know everything about what they are providing. Explain to them exactly what you want to do.
-
They won't provide or validate instructions. Third party routers are not supported.
-
Nice.
Guess that's money well spent.
-
i may have to pay to have them run ethernet instead of coax. :(
I have a feeling its the router config that's fucked up and not the coax connection.
-
About all I can suggest trying is putting 00:26:b8:16:c0:12 in the MAC Address on Interfaces > WAN and seeing what happens.
ISPs really do suck.
-
I'll give that a shot.
Where can I find the DHCP logs for the WAN port and how can I force a release/renew?
-
The regular dhcp logs.
Status > Interfaces
-
There are some threads here re: Verizon DHCP, router impersonation, etc. In the past they even required certain DHCP options be included in the request. Try search.
Oh, and the Verizon DHCP lease is probably 2 hours, if you want to wait it out to get released.
-
I gave the WAN interface the same MAC address as the router. Still no luck.
Looking at the DHCP logs it looks like the WAN interface is getting a DHCP lease? Am I reading this wrong? I also saw the WAN lease in the pfsense DHCP leases page. What is going on here?
[dhcp logs.txt](/public/imported_attachments/1/dhcp logs.txt)
-
No it's not getting responses to DHCPREQUESTs or DHCPDISCOVERs so it used what it had cached from the last time it got 192.168.0.28 from somewhere.
