802.1p/q pfsense setup
-
Just looked your switch up on New Egg and is does have QoS capabilities. I have no experience with your switch Platform but typically if you are breaking your traffic up on your tagged ports into different Classes then you can give one Class priority over the Other. I believe that is what you are trying to do. CoS is a layer two way to give traffic priority which is what I think you want. PfSense does have QoS capabilities as well but I will let someone who is more knowledgeable in the matter speak on that. Here http://www.youtube.com/watch?v=EfXImr5q-sw is a video explaining how to setup traffic shaping if you wanted to try to play around with it.
-
I'm feeling like a complete idiot right now. I can't even get my Watchguard to grab a DHCP address from the network.
If I put my Macbook on VLAN2, it grabs an IP immediately and I can get out to the net.
If I put dummy IPs on the Macbook VLAN2 and the WG VLAN2, I can ping from the MacBook to the WG. Interestingly, I can't ping from the WG to the Macbook.
I've set my pfSense install back to defaults, I tried setting the MTU to 1496, I've put 'allow any <> any' rules on the WAN interface for both IPv4 and v6, and still no luck. So I'm dead in the water on testing.
One thing I did notice when I was messing with the firewall rules. There's an 802.1p button down near the bottom. Looks like you could create pass rules that add the 802.1p tags.
If I can figure out what's up with my DHCP problems I'll get back into this.
-
I don't see any 802.1p settings at the bottom of my firewall rules.
-
I found this image in another, unrelated thread:
Thread reference: https://forum.pfsense.org/index.php?topic=61002.0
The above thread basically discusses how it was broken in a previous release.
If it helps, I'm running 2.1-Release on a Watchguard x5000. My firewall rule menus look like the ones in the example. If I were going to try this, I'd set up a pass-all rule for TCP/UDP, and for 802.1p I'd chose match on none and apply CA. (Critical Apps, bit 3)
I may have found what was broken in my WAN VLAN. I probably won't be able to test it before tomorrow though.
-
Interesting… 2.0.3 doesn't have that section.
-
Couple of things, remember that most pcs don't deal with tagged traffic. The port going to Pfsense should be tagged with all your vlans. The port going to your mac should be untagged. Some switches due it with the pvid setting others when you assign a vlan to a port make sure its untagged. Lastly I would remind you to make sure you configure dhcp for that vlan.
-
The VLAN'd port is facing the ISP. The WAN port has to be tagged on VLAN 2 in order for traffic to pass.
Outgoing traffic to the ISP also needs to have the .1p tags in order to not get dumped into a low speed queue.
When I talk about testing with my Mac, I'm putting a VLAN on the Thunderbolt GigE interface and plugging it directly into their ONT.
-
I fixed the VLAN and I'm getting out just fine. I'm pulling ~400 down to Softlayer in Dallas, but uploads are still stuck at 10.
What's worse is the TV system is not working. The guide is showing, but that could just be cached. I get a black screen on every channel I try.
I set up outbound rules from the WAN interface to 'any' to try to apply the tags as provided in the first post. Nothing seems to help so far.
I'm starting to wonder if the original info was deleted simply because it was wrong or incomplete, and not because it's some conspiracy to keep 3rd party routers off the network.
-
Still no joy on the uploads.
I do have some possible insight into the problem with the TV, though I'm no closer to fixing it. Atlantisman, let me know if you're a TV subscriber or if you're internet-only. I won't clutter up the thread with TV service details if I'm the only one using it right now.
-
I am also a TV subscriber, and i did notice that if i put the TV equipment behind a different router other than their own that it would just give me black screens. Even if i did this Fiber jack –-> Their router ---> pfsense ---> tv box.
-
I noticed the TV boxes and the storage box send a UDP IPv6 packet to ff02::1 approximately once per minute. This is roughly equivalent to IPv4 multicast on 224.0.0.1? I'm still really green on IPv6.
Even though my pfSense install had a permit any <> any rule for IPv6, it was still blocking these multicast messages. I put in a pass rule using the auto-generate tool in the logs. That let the traffic out, but no replies were coming in. It seems there's a lot that needs fixing. This will really test the patience of my wife ;D
-
Can you guys tunnel your TV service through a vlan on your network keeping the isp router, but then have it supply a public IP to Pfsense so you can use it as your edge router? I think this will give you control over the internet which is what you want and also allow your TV service to work undisturbed. What service are you guys using that you get 400 Mbps down? That is amazing!
-
400 is slow. It's supposed to be a gig both directions ;) Unfortunately, I think my old Watchguard box will be hardware-limited to ~400. As long as I can fix the upload speeds and get the TV working, I don't really care. Even 400 is faster than pretty much anything else I can connect to.
That's not a bad idea on segregating the ISP router. I'm not yet convinced that it's necessary though. It looks like the TV devices just need to pass certain kinds of IPv6 traffic which pfSense seems to block by default.
Later this week I'll see about borrowing some hardware from work so I can set up a Wireshark tap between the ONT and router. Then we'll see exactly what's going over the wire.
I'm also going to set up one of my Adtran routers to do some testing. I've got a much better understanding of those, and I've got a much easier interface to mess with the .1p tags.
-
You're getting better results than i am without the .1p settings, max i have seen is 85/10, and i know my pfsense build can support the whole gig.
-
Unfortunately, I think my old Watchguard box will be hardware-limited to ~400.
Are you still running the 2.8GHz P4? My X6000 passes ~365Mbps but it's running at 1.2GHz. I would expect yours to pass well over 400Mbps.
Steve
-
Are you still running the 2.8GHz P4?
Yeah. I haven't done anything to the CPU. I stuck more RAM in it because it was sitting in a box doing nothing. But that's the only performance chance I made. I had to replace the PSU and every capacitor on the motherboard though. That was not fun.
I haven't done any throughput testing on it. The reduced speeds could be due to the .1p situation. My outbound requests for data are going into the 'best effort' bin, which has the default effect of slowing down a server's response to me.
-
I haven't had a lot of time to do much testing as of now. I have just been trying to research a way of either doing the .1p settings in pfsense or possibly on a switch level before it gets to my pfsense machine.
-
I've made a bit of progress. It's not strictly pfSense related, but I'm hoping we can use this to bridge the gap.
I borrowed an Adtran Netvanta 1335 from work. It's basically a router with some Layer 3 switching capabilities. There's 24 10/100 ports and 2 gig ports.
Right off the bat, this old POS looks to be hardware limited to ~120 Mbit/sec even on the gig ports. I knew they were running out of gas (which is why we're replacing them at work) but I thought it was a CPU/ # of firewall sessions problem. I guess it's all of the above.
Also, I have no IPv6 enabled. I'm not even sure it's supported on this platform. No IPv6 = IPTV on this system.
Anyway, I fixed the upload problem. Once I got basic connectivity established, I was pulling 120 down, and only 10 up. Which is what Atlantis and I were seeing on pfSense.
After I got a QoS policy in place, upload improved to match the download rates. I was getting 120 both ways. I did verify that the gig ports were auto-negotiating at the correct rate and not accumulating errors.
So here's what I'm hoping for. Adtran configs are very similar to Cisco. It's my hope that some of the more knowledgeable folks will read what I did with this Adtran, and then chime in with how we might be able to implement a similar config on pfSense.
I'll explain the relevant parts of the config, and I'll upload the entire thing as an attachment. The only changes I've made is to remove the password hashes. Everything else is line for line identical to my running config. Please don't critique it too hard. It's just something I banged together in a few minutes for testing purposes.
So, to get this working:
Create interface VLAN 2, and set it to DHCP.
*Put interface gigabit-switchport 0/1 into VLAN trunking mode. Verify that VLAN 2 obtains an IP address and you can ping out.
*Turn up interface gigabit-switchport 0/2 and let it go on the default VLAN. Add the necessary policies to allow outbound NAT. Verify access.Create access list GF-dhcp
*Set the ACL to match both TCP and UDP port 67. Probably only needs UDP. Whatever.Create access list GF-default
*Set this as a permit IP any <-> anyCreate QoS policy GF-QoS
- On the first policy term, match against the GF-dhcp ACL
- When packets match the ACL, set the VLAN priority / 802.1p / CoS bit 2
- On the second policy term, match against GF-default
- This is the catch-all rule, which applies VLAN priority / 802.1p / CoS bit 3
- I wanted to do a ACL and QoS term for IGMP, but I couldn't figure out how to enable that. Maybe later.
Apply the QoS policy in the outbound direction on VLAN 2.
All traffic exiting VLAN 2 towards the internet will have the .1p / CoS bits set, and upload speeds should see a dramatic improvement.
Anyone want to take a crack at interpreting this into a pfSense config?
-
I was just able to get it working, but the QoS part is done through my switch (two ports are vlan'd off, one for the fiber jack, and one for pfsense). The switch strips off the QoS then passing the clean packets to pfsense. No TV as of now, as i probably need to upgrade to pfsense 2.1 to get full IPv6 support.
I have a Zyxel GS1910 switch, and i wasn't sure which bit was for IGMP and which was for DHCP (they all just have a number code on my switch) so i set them all to 3.
The result is a clean 930 down and 934 up.
UPDATE
Upgraded to pfsense 2.1 and set allow all IP6 traffic outbound, still no TV service, i get the guide, On-Demand, and DVR functionality, but no live TV.
UPDATE 2
The TV service not functioning does not appear to be caused by the firewall, it could be that the TV equipment somehow pairs to the router so you can't just take the TV box over to a buddies house and get the service from it. You'd think that they'd accomplish this task by only allowing IPs from their subnets on their IPTV servers, but who knows.
-
Have you read up on IGMP at all? I've seen people in other threads about IPTV systems mentioning that they had to run some kind of IGMP proxy in order to get TV working. I haven't dug too deep into it myself since my focus until now has been getting the data working correctly.
I really hope it's possible to get the .1p stuff working in pfSense. I've got a really nice gig switch, but I'd rather not have it managing both internal and external traffic, mainly from a simplicity standpoint. That was a big part of my reason for buying the Watchguard.
