Trying to figure out VLANs, 3 LAN's, 1 Ubiquiti AP
-
So on this same setup I have a question.
I'm getting some Rx Bad Packets on the switch (TP-Link SG-108E).
Cables are good, interfaces are good, VLANs are causing the problem. If I disable the VLAN, then 0 Bad Packets.
I've attached screenshots of my current config, is this correct?
-No Flow Control
-No Storm Control
-No Bandwidth Limiting
-YES IGMP SnoopingBad Packets are pretty low right now
~0.04% on Port 1 (pfSense)
~0.003% on Port 3 (Ubiquiti AP)But earlier it was ~1% on Port 1 and ~2% on Port 3.
Everything is working, but my Ubiquiti AP AC PRO seems slow. About the best I can get out of it is between 160-200Mbps via iPerf on an S7 Edge (AC, MIMO) on a clean channel with excellent reception. I got better performance out of my a TP-Link as an AP.
I would assume this is not a pfSense problem as the AP & S7 are on the same LAN (S7 is not on VLAN), also there are no dropped packets on any interface in pfSense.
Any suggestions on speeding up the wifi is appreciated. Ubiquiti support asked for Speedtest results to test my performance after I sent them iperf results…. They ultimately just recommended replacing the AP, I did exchange it, but the performance is the same.
-
Not sure what to tell you there:
sg300-223#sh interface counters gig 46
Port InUcastPkts InMcastPkts InBcastPkts InOctets
–-------------- ------------ ------------ ------------ ------------
gi46 2147428356 5953624 1534156 1958781584609Port OutUcastPkts OutMcastPkts OutBcastPkts OutOctets
gi46 1385816636 39047110 10667840 275780164044
Alignment Errors: 0
FCS Errors: 0
Single Collision Frames: 0
Multiple Collision Frames: 0
SQE Test Errors: 0
Deferred Transmissions: 0
Late Collisions: 0
Excessive Collisions: 0
Carrier Sense Errors: 0
Oversize Packets: 0
Internal MAC Rx Errors: 0
Symbol Errors: 0
Received Pause Frames: 0
Transmitted Pause Frames: 0That is a tagged interface to an SG-2440 igb NIC.
For sure the errors between the AP and the switch have zero to do with the firewall.
-
For sure the errors between the AP and the switch have zero to do with the firewall.
Yeah, I was just hoping I'd misconfigured something simple on the switch that would be easy for someone else to spot.
-
I am seeing the same sort of thing on the other side of the MoCA 2 here. Not quite sure what that's about yet. Port 1 is the MoCA adapter (untagged + tagged), port 8 is the Ruckus 7372 (tagged). All the other connected ports are simple untagged ports and should be completely clean. The MoCA 2 adapters aren't really dot1q but seem to handle the frame sizes just fine. The one up here on the cisco sg300 is completely clean.
Might have to put a brocade down there for a while so I can see what's really going on. It's a dlink right now.
![Screen Shot 2017-04-29 at 3.24.56 PM.png](/public/imported_attachments/1/Screen Shot 2017-04-29 at 3.24.56 PM.png)
![Screen Shot 2017-04-29 at 3.24.56 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-04-29 at 3.24.56 PM.png_thumb) -
Well I honestly don't know what a bunch of the stuff you said is, but some googling tells me that a MoCA is Multimedia over Coax.
The closest thing I have to that on my network is the PoE injector, which really isn't close to that at all haha. Could the PoE injector be causing problems?
My assumption was that the switch was the problem, considering that it's the weakest (cheapest) link in the network. I've been looking around eBay to see if I could pick up a better used switch for cheap, but haven't found one yet.
Could these packet issues be related to my Ubiquiti AP slow wifi?
The bad Rx packets are up to ~1.4% on the AP port (#3) now, but still at ~0.097% for the pfSense port (#1).
-
"between 160-200Mbps via iPerf on an S7 Edge (AC, MIMO) on a clean channel with excellent reception"
Between what an what? What is the client, what is the server for your iperf test?
What exactly is connect to ports 1 and 3?? Your AP? How are they configured for your vlans?
edit: Just ordered one of these switches. It was only $30 and I can replace the dumb switch I am using for my raspberry pis with it ;) Or change out my netgear in the AV cabinet.. But having it around will allow me to test both the lowend netgear GS108Ev3 and this TL-SG108E, their seem to be lots of people using them here..
So couple of days and I will connect it to my unifi APs that are doing vlans using poe injectors so will be able to duplicate your setup. I see no errors on my sg300 or my netgear that my AP are currently connected to.
-
The iPerf test I've seen pretty consistent results with multiple setups.
I've tried S7 Edge as client and server connected to both a desktop and laptop on wired connections (both desktop & laptop have Intel NICs and get full gigabit ~944 Mbps iPerf between one another).
The topology is:
S7 Edge (5GHz VHT 80) <> Ubiquiti AP AC PRO (Cat 7<>Injector<>Cat 6) <> SG-108E (Port 3) <> SG-108E (Port 7) <> Desktop or Laptop Intel NIC (Cat 6)
VLAN setup on the switch in the screenshots of this post: https://forum.pfsense.org/index.php?topic=129420.msg714891#msg714891
VLAN setup on pfSense attached to this post. DHCP servers, firewall rules have been setup and both VLANs seem to be working fine. I don't know if I can misconfigure them in such a way that they route and access the internet but are still wrong, other than firewall rules but I've tried with allow any rules?
I'm looking forward to seeing how a similar setup works for you!
It's possible that the issues I'm having with both Bad Rx Packets and slow wifi stem from the Ubiquiti AP, but I've tried two different units so I kind of don't think so?
-
Well be happy to duplicate your tests for sure.. Looks like the switch should be here tues.. I can fire up something and test current setup. I have Pro, LR and lite I can test.. I make out my 80mbps internet connection.. So I haven't tested what I see normally wifi to wired.. But pretty sure last time I tested it was over 400mbps..
Just had to grabe the 3rd underworld - we were going to watch the last one and seems we missed the one in 2012 ;) Sunday Funday and all..
-
I have not connected another switch down there yet but tested throughput across the MoCA bridges yesterday. Was getting a solid 750-800Mbit/sec between my Mac Mini and MBP using iperf3 TCP. Errors were not incrementing in any relevant manner during the tests.
I think these switches might be counting something as an error that the beefier switches understand even though there is really nothing wrong. STP perhaps?
I watched a mirror port off the dlink for a while and didn't see anything obvious.
-
I think these switches might be counting something as an error that the beefier switches understand even though there is really nothing wrong. STP perhaps?
That makes sense. Googling finds that there are other people having the same issue (BadRxPackets with VLAN enabled on SG-108E).
http://forum.tp-link.com/showthread.php?83046-High-RxBadPkt-on-TL-SG108E -
It would not surprise me if all of these crappy little switches used the same basic chipset.
All of the guis basically look the same.
I just cracked a DGS-1100-08 and it's under a heatsink. It was only $35 but I don't feel like burning it.
-
So I swapped to a zyxel GS1900-8HP and all is working without errors and BadRxPackets (almost).
Now I can access clients across VLANs (and subnets).
There are 4 VLANs on the switch and 2 on pfSense (I'm fairly certain this has nothing to do with pfSense config but I thought I'd mention just in case).
VLANs:1: Default - SWITCH
10: Guest - SWITCH + PFSENSE
20: IoT - SWITCH + PFSENSE
99: UNUSED - SWITCHAll used ports are UNTAGGED on VLAN 1
Ports 3 (WAP) & Ports 1+2(PFSENSE, [LACP LAGG]) are TAGGED on VLAN 10 and VLAN 20
All unused ports are UNTAGGED on VLAN 99
What am I doing wrong here? Should I not TAG the LACP LAGG to pfSense and just TAG port 3(WAP) traffic?
-
You didn't say what isn't working. All you said is everything is working.
-
Now I can access clients across VLANs (and subnets).
Sorry, I should have clarified.
This is what I meant.
The main reason I want VLANs is to segregate traffic.
Right now I can access clients in VLAN 20 while connected to a client on VLAN 10.
My understanding is that I shouldn't be able to cross VLANs? So I'm assuming that I'm messing up the configuration on this.I also took a look at my State Table.
If I connect to my Guest Wifi (VLAN 10) and try to connect to a client on my IoT subnet (VLAN 20) I can.
When I go to the Guest interfaces firewall rules, and click the state table for the allow any any any rule there is a state between the two clients crossing subnets and VLANs. -
Without reading all the history of this long thread, I will just say that you need to look at the rules on each VLAN interface in pfSense.
If you have a "pass all" rule on an interface, then the firewall will allow all traffic originating on that interface - going to "the public internet" and to other subnets/VLANs/real LANs/… that are local to the firewall.
If you want to stop the local connections and allow public internet access, then you will need to have a smarter rule set. e.g. put a block rule with source any, destination "the local subnets you want to block from reaching". Then have a "pass all" rule after it to let everything else out.
-
hmm, I didn't think a pass all rule on an interface would allow traffic to route between different VLANs and Subnets.
I also didn't really think of this traffic as "originating" at the interface. It has to first pass through the switch which is assigning VLANs before it can get to the pfSense interface. I've pretty much just thought of the pfSense firewall interface as the last place traffic goes before heading either to the internet or a different interface.
What's the point of VLANs or subnets then? From my understanding I could have two(or many more) VLANs, an allow any rule for each of them but not have any of them be able to contact one another so long as they were all on separate VLANs.
I also expected most if not all of this client to client traffic on my network to be happening at the switch, not the firewall/router.
This doesn't seem correct but it's late, and I obviously am having issues understanding this anyway. I'll head to bed and see if this makes more sense tomorrow.
-
"hmm, I didn't think a pass all rule on an interface would allow traffic to route between different VLANs and Subnets. "
What did you think it would do exactly? ???
If you don't want vlan A talking to vlan B, then put in the rules to stop that..
"I also expected most if not all of this client to client traffic on my network to be happening at the switch, not the firewall/router. "
Do you have a L3 switch doing the routing? Then how would vlan A talk to vlan B without routing - that is not done at a switch that is done at a router.. If you need to route at the switch then you need an L3 switch (router)..
You can allow or block whatever traffic you want between your vlans - but you have to create the rules to do so, any any is just routing not firewall..
Rules are evaluated as traffic enters an interface, first rule to trigger wins no other rules are evaluated. If you don't want vlan A talking to vlan B, then on vlan A interface block A from going to B.. Its that simple!!
"LACP LAGG to pfSense"
What exactly are you trying to accomplish with your lag? Are you really worried about cable/port failing that you need failover? Lagg is not 1+1=2, its just 1 and 1.. You seem to have a lack of basic understanding of layer 2 and 3.. So I am thinking your not actually sure what lacp does either.. Or when it makes sense to lag.. I find it almost impossible to consider this something you would need to do in a home setup.. How many clients do you have exactly? Your internet connection is how fast? Why would you need/want to lag into pfsense??
-
I also didn't really think of this traffic as "originating" at the interface.
Technically you are correct. I could have worded it a bit better - "traffic originating from a client device downstream of/attached to the interface" might be clearer?
And what @johnpoz says.
There has to be a way for the firewall admin to allow traffic between 2 local interfaces (whether separate physical ethernet ports or VLANs). A "pass all" rule is one way to achieve all of that quickly.
-
Well, unsurprisingly I completely and fundamentally misunderstood(stand) how all of this works and the experienced users on the forum pointed me in the right direction.
Thank you to all of you for your help. I already posted the "Thank you" for the thread but applauds for all, haha!
I adjusted the firewall rules and all is well.
-
"hmm, I didn't think a pass all rule on an interface would allow traffic to route between different VLANs and Subnets. "
What did you think it would do exactly? ???
If you don't want vlan A talking to vlan B, then put in the rules to stop that..
"I also expected most if not all of this client to client traffic on my network to be happening at the switch, not the firewall/router. "
Do you have a L3 switch doing the routing? Then how would vlan A talk to vlan B without routing - that is not done at a switch that is done at a router.. If you need to route at the switch then you need an L3 switch (router)..
You can allow or block whatever traffic you want between your vlans - but you have to create the rules to do so, any any is just routing not firewall..
Rules are evaluated as traffic enters an interface, first rule to trigger wins no other rules are evaluated. If you don't want vlan A talking to vlan B, then on vlan A interface block A from going to B.. Its that simple!!
**"LACP LAGG to pfSense"
What exactly are you trying to accomplish with your lag? Are you really worried about cable/port failing that you need failover? Lagg is not 1+1=2, its just 1 and 1.. You seem to have a lack of basic understanding of layer 2 and 3.. So I am thinking your not actually sure what lacp does either.. Or when it makes sense to lag.. I find it almost impossible to consider this something you would need to do in a home setup.. How many clients do you have exactly? Your internet connection is how fast? Why would you need/want to lag into pfsense??**
Thank you for your reply!
As for the LACP LAGG, I have no use for it now. I really just tried to turn it on my Tp-Link switch just bto mess around with something new. It didn't work on the TP-link switch so I tried it again on this switch and it worked right away.
There's nothing on my network that would make use of an LACP LAGG right now, and there may not ever be. I may very well just put it back to one port. It was really just messing around.
As far as my current understanding of how the LACP LAGG works, I'll write it out here because I wouldn't be the least bit surprised if I was wrong.
LACP LAGG would balance load between two Full Duplex Ethernet ports creating one etherchannel from the switch to pfSense. The benefit would only be local as I don't have a >gigabit WAN and would probably very rarely if ever be realized on a small home network.
About the only time I could think of it being utilized would be multiple clients transferring large files to/from a NAS that also had a LACP LAGG configured on it. So that basically more than 1 client could get full gigabit speeds at a time.Is that description even close? If not please set me straight.
Again, I only set up the LAGG out of curiosity and likely won't keep it enabled because at this point all it's doing (in my understanding) is keeping power applied to two ports that I don't need on. Even with a high speed NAS I doubt I would get significant improvements on an LACP LAGG on my small home network.