Weird…. Can't access certain sites
-
Ok here's the deal and it's got me very confused (By the way great job on this PFsense team so far this is great).
My Config.
LAN IP 192.161.10.1 with DCHP enabled
WAN 70.89.221.233 / 8
wan gateway 70.89.221.238now from internally I can view and ping most sites. But There are a few I can't like. stumbleupon.com (70.85.3.132) and suvault.com (70.84.208.122)
I know this is an issue with pfsense or the way I have it set up because when I plug in the old linksys with the same wan ip and lan ip it goes to these sites just fine and I can ping them. Anyone have any clue why this is going on?????Thanks,
-
Are you sure you have a /8 at wan???
Also make sure if you can ping the hosts by IP. might be a DNS issue. check the DNS servers. -
yep I'm sure it's /8 and I can't ping by ip. If I ping by IP all packets are lost and if I ping by domain it will give me the ip (hence it does get to the dns server) but will also lose all the packets. I also tried pinging from the diagnostics tools and it also does the same thing.
-
I'm just curious. Can you set your WAN subnet to /16, maybe even /24 to see if this makes a difference? Your wan gateway is within a /24 or even higher value subnet.
-
hoba,
Ok it works…
thanks now I reallize what I did I switched the subnet numbers around in my head.
-
cool. a /8 is very unlikely at wan ;)
-
Ok here's the deal and it's got me very confused (By the way great job on this PFsense team so far this is great).
My Config.
LAN IP 192.161.10.1 with DCHP enabled
WAN 70.89.221.233 / 8
wan gateway 70.89.221.238now from internally I can view and ping most sites. But There are a few I can't like. stumbleupon.com (70.85.3.132) and suvault.com (70.84.208.122)
I know this is an issue with pfsense or the way I have it set up because when I plug in the old linksys with the same wan ip and lan ip it goes to these sites just fine and I can ping them. Anyone have any clue why this is going on?????Thanks,
This looks like a Comcast business connection. I guarantee that WAN is supposed to be /29. I'm in the same 70.0.0.0/8 CIDR block (on two seperate connections) and /8 is NOT the correct netmask for machines attached to it.
–Bill