Fios Static IP and pfsense - Can't access internet.
-
Ok I have been searching for a while now with no luck. I junked the Actiontec router provided by Verizon for their Fios service. I have been using my 2yr old Linksys WRT54GS v4 running DD-WRT. I decided to build my own replacement for that so I purchased a WRAP board and isntalled pfsense 1.2 beta2 on it. I have 1 static IP from verizon and I configured pfsense as follows:
WAN:
IP 71.246.x.x /24,
Gateway: same IP.
LAN:
IP 192.168.1.1 /24DHCP is configured to hand out IPs in the range of 192.168.1.20-254. I have the public DNS servers provided to me by Verizon on the System>General Setup page: 151.197.0.38-39. I haven't touched anything else and I seem to only be able to ping the routers LAN IP and WAN IP. I can't access any websites on the internet and cant ping any outside IP's. Am I missing some other step in the configuration proccess? Any NAT settings or Firewall rules that are required that arn't default on installation?
Any help is appreciated.
-
Is on the LAN tab any rule that allows traffic?
Per default pfSense blocks everything.
But there should be a autocreated rule that allows traffc from the LAN subnet to WANone thing i dont understand: you say you use as Gateway the same IP as your configured IP on WAN?
The Gateway IP has to be something else than your own WAN-IP.
You should have somewhere the information from your ISP what the address of your Gateway is. -
Thats the odd thing. I was told to use my static IP as my gateway. Oddly enough it's been working like that with the Linksys. As per the rule allowing traffic from LAN to WAN, I will have to check that out. If my memory serves me correctly, there wan't any rules created. But don't take my word for it, it was very very late.
-
I've only seen using the interface IP as the gateway work on a /32 netmask, effectively making it a broadcast interface.
-
Well I took your advice and verified that I was told to use the wrong IP for my gateway. I'm still trying to wrap my head around the fact that my Linksys running dd-wrt worked regardless of the improper settings.