Another Wan to Lan connectivity issue
-
Ok, so. I isolated the network. Basically ISP>Router>PFsense> separate switch>1port>laptop. It ran beautifully. I then had the theory that perhaps my sorta smart switches, had poor routing capabilities and had bad MAC routing info. So I rebooted my switch, reset all things to my network, and bam. went from a 77ms ping time to google and a network connection that made people with Modems laugh at to a 2ms ping to google. So in the end the issue lay outside the scope of troubleshooting we did. Which we should have thought about this after we received the same results with a separate system. All good though.
Thanks for the help! I'm sure I'll be back for more.
-
Hmm, ok. Weird. I guess I'll chalk that up to experience. ;)
Steve
-
Just caught this one, glad to hear it's all good now. One point that I would have added is did you want Pfsense to NAT or route? Seems to me your first router connected to the ISP should be doing the NATing and PfSense should route. You will need to run a routing protocol between the two or setup static routes. You might see a speed increase as NATing can be expensive. Hell you might want to put PfSense first at the perimeter of your network.
-
Unfortunately with a dual network failover configuration my current setup won't support PFsense at the edge of the network (only 2 ports available) I have considered setting up a PFsense router/firewall device, but with the cost of ours, and the fact the the owner just put more money out on it for support/updates he would be unwilling to pay out for another device. So am stuck where I am.
