Pfsense not sending traffic after reboots
Pfsense not sending traffic after reboots
Yeah the troubleshooter has been entirely unhelpful lol, I have just been living with this issue for months and decided top finally ask for help fixing it. here's the ipconfig: Windows IP Configuration Host Name . . . . . . . . . . . . : DESKTOP-R5ORPAV Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : home.arpa Ethernet adapter Ethernet: Connection-specific DNS Suffix . : home.arpa Description . . . . . . . . . . . : Intel® Ethernet Controller (3) I225-V Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.1.169(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, August 24, 2022 12:45:02 PM Lease Expires . . . . . . . . . . : Wednesday, August 24, 2022 2:45:02 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : Enabled Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : hitronhub.home Description . . . . . . . . . . . : Intel® Dual Band Wireless-AC 7265 Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 1: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 10: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2 Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Bluetooth Network Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2 Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
Are you operating a DNS server, proxy, or cache on your PFSense device located at 192.168.1.1? DNS issues can occur and Windows often uses them to verify internet connectivity. You might switch to Wi-Fi, retrieve IP details, then revert to Ethernet. Or perhaps the network switches are managed differently. I’m not very experienced with hardware setups.
I'm just getting started with all this, so I'm not sure how to respond to your questions. I believe the answer is yes. For the second point, I typically connect to the built-in Ethernet ports at airports to retrieve IP information.
Cool, so can you post ipconfig /all when it is working, so we can see the difference? I'm still not convinced it isn't a cable issue at this point, not all RJ45 (ethernet) sockets are created equal, and finding a cable that works in one socket but not another wouldn't be the first time. I'll try and run pfsense up in a VM, get a feel for it ... done So, yeah, in it's default state you might get dns issues, if you can log into it and use the Diagnostic > DNS Lookup menu option to see if it can resolve stuff on it's own, that's the starting point in my mind. Another Edit: pfsense is rather well though out UI over a BSD backend, I wouldn't use it myself as I route on my server, but it's still quite nice.
On the non-connected setup, my higher-level reply shows the connected state. Windows IP Configuration Host Name is listed as DESKTOP-R5ORPAV with the primary DNS suffix and node type details. Hybrid IP routing is active, no WINS proxy is running, and there’s no DNS suffix search list present. The Ethernet adapter is described as Intel® controller, DHCP is enabled, autoconfiguration is active, and the IPv4 address is 169.254.251.121 with a default gateway of 255.255.0.0. The description also notes a media disconnection and mentions wireless options including Wi-Fi and Bluetooth.
So this is a self assigned APIPA address, meaning your computer couldn't reach the DHCP server or it didn't like the reply etc. You said earlier you tried the PC with a static IP and it still didn't work? We know the DHCP server works because it works when plugged into the Airport, this is firmly in the "hardware error" camp*. Whether that is "pins on an RJ45 crimped down a bit hard" and not making contact with the switches port, or the the swicthport is literally on it's way out (some switch hardware nearly dead). Let the PC run through the Airport for a time, and see if the problem re-occurs, or see if it works on the "spare" LAN port. *Unless you have been adding firewall rules and managed to block the "renew my lease please" traffic but not the "hello can I have an IP please" traffic (it's possible, I've done it ) and windows is confused. It's not a managed switch is it?
It appears the 5-port setup might be affected by the entire switch. It seems to occur with wired devices and occasionally on wireless ones—possibly due to a recent change or a firewall configuration issue.
The optimal method is connecting one of the PCs directly to the PFSSEN machines LAN port, leaving it overnight. If it functions in the morning, move the switch back; if it works with a TP-link, discard it and upgrade. Regarding your question, how many Ethernet ports are on the AirPort? You can completely remove the switch and still maintain a working network for testing.
I’m back and things are worse than before. I removed the switch from my setup and switched to using the AP, which seems to be working well. Yet connections keep dropping on both wired and some wireless devices. I replaced all Ethernet cables between my modem and the machines, but the problem persists. I’m not sure what to do next—my plan was to reset PFSense back to defaults and check the results. If I have time later, I might take a look at my PC and capture screenshots of firewall rules and airport settings. The odd thing is that only certain devices are affected: the 2016 MacBook Pro, the 2011 MacBook Pro with newer Wi-Fi card, Apple TV, and Roku TV. Devices that don’t include multiple iPhones, iPads, Apple Watches, Google Homes, and even the Airport AP (though it’s wired).