Help!! WAN DHCP is not working trough my ISP router as bridge pfsense
-
Hi, I tried to configure the my ISP Netgear router SW as bridge, but when I tried to set up the interface wan by DHCP I didn't get a correct IP. it took 0.0.0.0 and the default gateway in the range of the 192.168.0.X. I tried to configure the wan interface static, and assign it inside the range of my IP Public (73.124.X.X) when I assigned this I tried to do ping or tracertroute to 8.8.8.8 but nothing responded. Please any ideas?
-
@gab-rc14 said in Help!! WAN DHCP is not working trough my ISP router as bridge pfsense:
and assign it inside the range of my IP Public (73.124.X.X) when I assigned this I tried to do ping or tracertroute to 8.8.8.8 but nothing responded
So you just took an IP, belonging to your ISP, that is probably assigned to a fellow-client, and you tried to use that.
( while doing so the connection of this fellow probably also died ).@gab-rc14 said in Help!! WAN DHCP is not working trough my ISP router as bridge pfsense:
Hi, I tried to configure the my ISP Netgear router SW as bridge, but when I tried to set up the interface wan by DHCP I didn't get a correct IP. it took 0.0.0.0 and the default gateway in the range of the 192.168.0.X.
It could be anything.
First, look at the paper from your ISP that explains how to set up a typical router device as a bridge.
Does your connection actually accepts bridging devices ?
If so, is standard "DHCP" as described in the RFC used ? Or did your ISP use some "home made protocol" by adding DHCP "options" that the client should sent ? Etc.A know issue us : when the WAN NIC, from a pfSense point of view, comes up, the DHCP-client is fired. But to early, the bridge isn't build yet, and you obtain some RFC19819 IP.
This :
InterfacesWAN (driver) > DHCP Client Configuration > Options = Advanced Configuration
can be used to solve timing issues, or to exclude RFC1919 answers, etc.
