Packet loss on RCC-VE 2440 after move and reflash?
-
Hi folks,
I have a RCC-VE 2440 that's been quietly humming along running pfSense for a couple years now. We recently moved and I decided to reflash pfSense and start our new home network fresh. I also applied the CoreBoot upgrade (through packages).
Unfortunately, I started experiencing some packet loss around the same time that essentially renders the internet unusable. Even when I ping the unit from the switch it's attached to (see the attached picture). I'm not sure if something got jostled during the move, or if the CoreBoot upgrade changed something, or what. I've tried two different switches and two different network cables.
Any suggestions? I might try seeing if the problem persists after a factory reset.
Mike
EDIT: I had been running pfSense 2.3 and I flashed 2.4, so that might have something to do with it as well.
-
Probably not pfSense. Look at your layer 2. Packet capture on pfSense and run the same thing. Are the packets arriving?
-
Shouldn't this be in "Official Hardware" ?
-
Probably nothing hardware-specific there.
-
Probably nothing hardware-specific there.
Well, then it shouldn't be in any hardware at all :P
-
Probably not pfSense. Look at your layer 2. Packet capture on pfSense and run the same thing. Are the packets arriving?
Okay, I'll give that a try.
@johnkeates:
Shouldn't this be in "Official Hardware" ?
It's an RCC-VE 2440, not an SG-2440. ;D
Probably nothing hardware-specific there.
I hope this is the case but no other device on my network is experiencing packet loss.
-
Quick check: it did work fine before, didn't it? Should be a firmware/software configuration issue I suspect.
-
My first guess would be an address conflict with 192.168.1.1 that didn't exist before.
-
Well this is a long and stupid story but to the best of my understanding the root evil was my new TP-Link AP (AP500). It's noisy and terrible and was causing issues even between wired devices. Changing the wireless settings from Multi-SSID mode to simple AP mode (or disconnecting it entirely) would completely solve the packet loss and latency issues. I should have mentioned that I got a new AP in my original post and didn't, so that's my bad.
I tried working with TP-Link support to resolve this issue. I also read up on all the issues with TP-Link hardware that people have reported (on this forum and TP-Link's own forum) over the past few years. It would have been smart to do this research before I spent ~$400 on TP-Link smart switches and the AP. ::)
Ultimately, I decided to rip out the AP and replace it with a UniFi AP (AC Pro). It's amazingly awesome—and $10 cheaper than the AP500, so go figure. I have some UniFi switches coming as well. My biggest complaint so far is that nobody seems to keep the 16-port, 150W switch in stock, so I had to pony up some big boy money for the 24-port, 250W model. I've got the controller running on an rpi2 and everything works great!
EDIT: To give some idea of what I was seeing, I had a wireless client on a SSID assigned to VLAN10, pinging the VLAN10 interface on the 2440. Packet captures in pfSense showed ICMP packets hitting the VLAN interface and its parent interface with partial overlap. It was completely bizarre.
-
Sounds like typical TP-Link VLAN behavior.
Garbage brand.
Glad you got it figured out.
-
Sounds like they messed up VLAN behaviour for the multi-SSID part. On top of that, they probably couldn't do this in the ASIC or accelerator, so as soon as you use those (rather common) functions to spit 802.11 traffic into 802.1q VLANs the bad performance of the (supposed) MIPS device shows. I suspect that if you use no VLAN (or default 1) and no multi-SSID it all works fine because the switch is in hardware forwarding mode.
