Some websites not responding
I'm having the issue where pfSense is causing some websites to not respond correctly. I've found a couple of sites that I can't connect to: craigslist.org (220.127.116.11) and speedtest.net (18.104.22.168). I've looked through the doc https://doc.pfsense.org/index.php/Unable_to_Access_Some_Websites and I've done all of the recommendations.
pfSense 2.2 stable
Single WAN (10.1.1.80), single LAN in bridged (transparent) mode.
WAN Gateway at 10.1.1.254/24.
Most traffic flows and everything is working correctly besides the 2 sites above.
Here's what I've done so far:
1. Followed instructions in doc cited above, all IPs, netmasks, and routes seem to be correct.
2. Set IPv6 type to none on the WAN interface (we're only using v4 and I'm grasping at straws).
3. Nothing logged for the firewall, so it doesn't appear to be an issue there.
4. Nothing logged at all that I can find for either site.
5. Simplified down to a telnet session to port 80 from client machine. No response, it eventually times out.
6. From an SSH session on the pfSense box I am able to telnet to port 80.
7. Tried static route to craigslist, same results.
8. Tried adding firewall rules specifically allowing access to the above sites. Same results.
9. When bypassing pfsense the above sites work. It's only when traffic is flowing through pfsense that it's a issue.
Since I've now tried everything I can think of, does anyone else have any ideas? Even any ideas on where to look for useful logs would be great. I can't find anything, that traffic just seems to disappear.
99.99999999999% sure its DNS issue.
I'd do a clean install of pfsense if it isn't very configured.
Default clean install of 2.2 is pretty optimal. Don't add any DNS servers or change any DNS settings. At all. Anywhere…
Now - Make sure the adapters on your laptops, computers or whatever are getting both IP and DNS automatically via DNS (YES - Manually check the adapter settings)
Plug everything in. Reboot everything.
Let me know how that works for you.
I can absolutely start from scratch and will give it a go.
One question though, If those IPs work when bypassing pfSense (phsically removing pfSense from the network), wouldn't that rule out a DNS issue?
No - It just means you probably configured pfsense DNS badly.
Gotcha. I'll start from scratch and will report back this afternoon. Thanks for the help!
I'm once again stumped. I've reinstalled pfSense probably half a dozen times now trying to get this to work. At this point, I'm down to Craigslist not working, and only on some machines. I have a Vista laptop that can access Craigslist when it's behind pfSense, and a Win 7 desktop that can't, both using the latest Chrome.
Kejianshi, I took your advice and only configured the most basic version of pfSense that I could. I installed pfSense, setup the WAN and LAN, setup the bridging and that was it. Everything else (including DNS) was left at the default.
I did find that if I disable packet filtering I'm able to get to CL, but I don't think that's surprising.
Are there any logs I could look at to find out where the traffic is going? I've tried running wireshark, but all it tells me is that I'm sending SYN packets, but never getting any ACK. Is there any way to trace traffic within pfSense to find out what's going on?
I ran a packet capture on the WAN and LAN interfaces. On the WAN I can see the SYN and ACK packets flowing as I would expect. On the LAN side, the ACKs never make it there. So, there is some sort of disconnect between the WAN and the LAN. I don't see anything in any of the logs.
There's got to be a way to trace the traffic, I just don't know what it is.
KOM last edited by
WAN/LAN connectivity is usually an all-or-nothing deal. I can't even fathom how the firewall would decide to selectively break some websites, but only on some of your clients. No caching involved such as Squid?
No squid, no packages installed at all. Just the base system configured with bridging, that's it.
It seems really bizarre to me as well. I can only think that there must be something specific to that traffic that is causing some sort of failure, but I can't figure out how to track it down.
KOM last edited by
I'd start at the back end. You have clients that consistently fail to render a site that is fine in other clients? What is different between these clients? What's different between sites that always works and problem sites (eg HTTPS)? Are you allowing IP6?
um if your trying to use pfsense as transparent bridge firewall. Then there really wouldn't be a wan would there? It would be a bridge interface.. pfsense would not be the dns server normally in such a setup, etc. And by default I don't even think it firewalls traffic over a bridge. Don't you have to that?
What guide did you follow to setup this sort of setup?
What if you just let pfsense do its thing and route and nat the connection?
haha - So we are now finding out pfsense is in some bizarre configuration?
Looks like you found me the magic bullet. In the guide I used for the bridging setup, it did have me turn on filtering on the bridge interface (net.link.bridge.pfil_bridge=1). I had assumed that was required for bridging, but apparently not. I've set that back to default, the bridging still works and I am still able to set firewall rules and limiters, etc. Craigslist is also now responding. I think that's got this problem solved. Now to find new, more exciting problems.
Kejianshi, I did mention in my first post that I was using a bridged setup. :)
Kejianshi, KOM and johnpoz, thank you all so much for your help. This is a great community and I'm glad I found my way here.
Without even looking at the guide - can tell you its dated, link says 2.0.1, your on 2.2 are you not? Shitload of changes since 2.0
Yeah, I am on 2.2. I searched, but I didn't find any newer guides. Everything I found on setting up bridging was 2.0 or older. Is there a newer, better way of doing bridging?
Did you ever find a resolution for this issue? We just deployed a brand new pfsense firewall (2.2.1) this morning and we have the exact same issue.
All API calls fail form servers behind the firewall. Its a transparent bridge setup with all public IPs (no NAT no DHCP).
dennypage last edited by
Call this a shot in the dark…
I had a great deal of problem with a handful of sites after I upgraded from 2.1.5 to the 2.2 beta. My problem turned out to be excessive & unexplained IP fragmentation occurring somewhere between the remote site and the firewall. For some reason, 2.1.5 had no problem with this, but in 2.2 did. Setting the "Clear Invalid DF bits" did not address the problem.
In the end, what fixed my issue was to clamp the media segment size to 1400 on the WAN interface. You might give clamping a try and see if it has any effect.
Just tried that. It did not work.