Problem after ISP change
-
Hello, first time poster here.
Earlier today I encountered a rather odd and annoying issue. I got a new Internet provider this morning (Telus Purefibre, in Canada), and there was much troubleshooting to get the advertised speeds. Well, after disconnecting and reconnecting my Windows 10 workstation from my pfSense router many times, I'm no longer able to access websites, either wirelessly (via my access point) or through a CAT6 connection.
Other devices on my network (both wired and wireless) are able to access the pfSense router (and Internet) just fine on my 940/940 line.
Oddly, I have no trouble pinging the LAN gateway, or global IP addresses. I'm also able to do nslookups of global addresses, as well as successfully ping domains.
Although I can't rule out the possibility of my LAN adapter being damaged (unlikely), I can rule out the possibility that my box's wireless adapter was damaged during this morning's activities. I'm able to connect to my phone's LTE hotspot and browse websites just fine.
Before I get into the nitty gritty details of my pfSense config, is there some obvious step that I'm missing here?
Any ideas would be very appreciated. And apologies if I've posted this in the wrong thread.
Cheers.
-
Do you have any packages installed? If you turn on logging of the default block rule (Status/System Logs/Settings are you seeing your connection blocked in the firewall log? If other devices can connect out and not this PC then it seems like it is either on the PC (firewall there?) or that PC's HTTP connections are being blocked.
-
@steveits Hi Steve, thanks for the input. I don't have any packages installed, and I've tried turning the default Windows 10 firewall on and off to no effect. Some devices get routed through an OpenVPN configuration, and some don't. Both types of devices seem to be working properly.
I would assume (though don't obviously know) that the issue is with pfSense. Though oddly, I restored yesterdays pfSense backup and the problem persists. All other devices pass traffic just fine, with only this box being denied (at least denied web traffic).
I'm rather new to the logs, but I'm not seeing my machine's source IP in there at all, which I find odd.
-
Mmm, this seems more likely to be a problem in that client that the firewall.
However, try setting a different static on that client. Does the behaviour change?
Try booting a live Linux distro on that client.
Since you have policy routing for some clients you might be hitting that from this client. So check it's IP is not in some alias somewhere.
Since it affects only TCP traffic check there is not a policy routing firewall rule that is still set to the default TCP only and should be using protocol 'any'.Steve
