Traffic Shaping and VLANs
-
At home I have a cable 60/10 connection and I'm running 2.3.3 p1 on an old Lenovo T410 laptop. Obviously it has only one NIC (Intel em) so I'm using VLANs in conjunction with a Netgear GS108Tv2 managed switch.
I have set the LAN interface as parent untagged (em0) with WAN as VLAN 100 and DMZ as VLAN 500. Everything works well, but I noticed that the traffic graph and the sharper queues are a bit odd. I took the screenshots below while I was downloading/uploading using Bittorrent from a host on the DMZ. The traffic is correctly being sent to the qOthersLow queue by the floating rules. At that time there was no significant traffic in or out of the LAN network.
However, it looks like that all the traffic in and out of WAN and DMZ is always going through the parent LAN interface. I suspect this is normal since physically there is only one interface, but I wanted to confirm. If that's the case should I change the bandwidth on the LAN qInternet from 60Mb to 70Mb since both uploads and downloads go through it as shown in the queue screenshot?
-
I think you misunderstand how the queues work. The queues are for outbound traffic for an interface only. According to what you've shown me below it looks like you are uploading 10.55 Mbps and downloading 60.68 + 43.11 Mbps.
-
Thank you for the reply. I understand that traffic shaping happens on the outgoing traffic and you are correct, at the time the queues screenshot was taken, the host on the DMZ was in fact downloading at 43Mbs and uploading at 10Mbs.
My question is more related to the fact that LAN is reporting 60M of traffic when I know for a fact that there was no significant traffic on the LAN at the time. So I was wondering, since LAN is the parent VLAN for the WAN and DMZ interfaces, if it is normal for pfSense to report traffic on the parent VLAN even when is generated from or going to the child interface.
If that's the case, it would explain why the traffic graph on the LAN interface will always be symmetrical (second screenshot).
-
I solved the problem by creating a new tagged VLAN and assigning it to the LAN interface, leaving the actual parent interface and default untagged VLAN 1 unused.