Gateway WAN keeps on having packet lost
-
@t309 Oh, and as I've said before, it seems to ping just fine for the first ~20-30 seconds or so, so I really feel like its a service in pfsense at least contributing to the problem. But I digress, I am not even remotely close to a linux or coding expert. Just an observation to spark a thought for someone who might actually know.
-
@t309 said in Gateway WAN keeps on having packet lost:
Another funny quirk I've found, is if I run a laptop on the Spectrum router without the pfsense box connected, I can ping all day long. As soon as the network port for the pfsense box comes up, give it 5-30 seconds and it goes right back to misbehaving, both on the laptop and the pfbox/LAN.
Hmm, that's with both the laptop and pfSense connected to the cable modem dircetly? Like the pings from the laptop are not going through pfSense at all but mearly having it connected at the same time affects laptop traffic?
That's very odd if so.Has this just started for you also? Like maybe a modem firmware update that changed the way it reacts to something pfSense is doing?
Exactly 50% packet loss sounds like some conflict, MAC or IP address. Did you spoof a MAC anywhere?
Steve
-
@stephenw10 Yes, very odd indeed.
Connected like this Modem>Cable Company-provided Router.
Cable-Company Router>port 1 laptop, port 2 pfsense.port 1 laptop pings solid as long as you like. Connect port 2 up (pfsense WAN-side), laptop pings almost perfect 50%(literally).
I'm no expert by any means, but i've worked with a lot of networks (as an installer of networked devices) and never seen anything quite like this.And as far as spoofing, I may have tried that initially in my quest to find what was wrong, that was on the first pf box (2.4.4), but have not done anything but the most basic items to get the new box 2.5.2 up and running.
-
Mmm, that really does seem like an IP or MAC conflict. Or maybe the router not in routing mode, like restricted to one client only somehow.
-
The new/current box is a flat default installation beside the fact it has 2 wan connections. I added the 2 wans to a gateway group, and then broke it after the 1 interface kept going up and down. I have just been enabling and disabling the interfaces to test and/or have usable internet. When you say conflict, are you meaning external to pfsense box on the wan side or in the pf config or where? Just for context, the pf box does still ping the same without the laptop as well. I just added the laptop to see if the cable internet was acutally the culprit or not as part of my troubleshooting. Thanks.
-
@t309 said in Gateway WAN keeps on having packet lost:
Connected like this Modem>Cable Company-provided Router.
Cable-Company Router>port 1 laptop, port 2 pfsense.port 1 laptop pings solid as long as you like. Connect port 2 up (pfsense WAN-side), laptop pings almost perfect 50%(literally).
Please reboot the cable-co router. I suspect that that device is caching MAC addresses or otherwise engaging in ARP misbehavior, thus causing packets to get misrouted when you connect pfSense. Also examine system/general setup/hostname for whether it's a dupe of your laptop's hostname. Try changing it to something that doesn't include the string "pfSense", then rebooting everything.
-
@t309 said in Gateway WAN keeps on having packet lost:
When you say conflict, are you meaning external to pfsense box on the wan side or in the pf config or where?
I mean in the layer 2 segment that is common to the laptop, the ISP router and the pfSense WAN.
So, for example, if you had spoofed the laptop MAC address in pfSense because the modem was locked to that and forgotten then connecting the laptop at the same time would be a conflict.
Steve
-
@stephenw10 Ok, thats what I thought. Verified the hostnames are different. I also disconnected the laptop, and the pf box still behaves the same (only thing on the lan side of the cable-co router). After Rebooting pfsense, the PC's on the lan side of pf box ping 100%, for the first 20-30 replies, then back to 50%.
-
@stephenw10 Any other ideas or things to try, logs, etc? The only thing currently on that physical segment is the pfsense WAN port. Another thing I noticed now is that the download speeds are also roughly half, I'm assuming due to the loss.
-
Nothing I can think if currently. Yeah any sort of packet loss will kill throughput.
