On 2011-08-28 02:16, Christiano F. Haesbaert wrote: > Heya, > > So here is a crude diff, the shiffting can be improved and if we wan't > this in the future we'll need a knob to enable "don't touch the > vlanprio thingy". > > Please it would be great if you can give this a spin Peter. I did some > basic tests with a re(4) (hw tagging) and a rl(4) (no hw tagging).
Thanks, tested and works like a charm: Before patch: em1: 15:13:55.762101 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:13:55.762400 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 500 pri 0 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:13:56.201398 00:1e:0b:2b:eb:ed 88:ae:1d:b5:94:e1 8100 102: 802.1Q vid 500 pri 2 192.168.0.1 > 192.168.0.2: icmp: echo request (id:21e1 seq:623) (DF) (ttl 64, id 0, len 84) 15:13:56.201553 88:ae:1d:b5:94:e1 00:1e:0b:2b:eb:ed 8100 102: 802.1Q vid 500 pri 0 192.168.0.2 > 192.168.0.1: icmp: echo reply (id:21e1 seq:623) (ttl 64, id 42697, len 84) em0: 15:13:55.762116 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 1500 pri 0 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:13:55.762388 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 1500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:13:56.201412 00:1e:0b:2b:eb:ed 88:ae:1d:b5:94:e1 8100 102: 802.1Q vid 1500 pri 0 192.168.0.1 > 192.168.0.2: icmp: echo request (id:21e1 seq:623) (DF) (ttl 64, id 0, len 84) 15:13:56.201547 88:ae:1d:b5:94:e1 00:1e:0b:2b:eb:ed 8100 102: 802.1Q vid 1500 pri 2 192.168.0.2 > 192.168.0.1: icmp: echo reply (id:21e1 seq:623) (ttl 64, id 42697, len 84) After patch: em1: 15:07:07.277884 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:07:07.278039 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:07:07.576643 00:1e:0b:2b:eb:ed 88:ae:1d:b5:94:e1 8100 102: 802.1Q vid 500 pri 2 192.168.0.1 > 192.168.0.2: icmp: echo request (id:21e1 seq:214) (DF) (ttl 64, id 0, len 84) 15:07:07.576794 88:ae:1d:b5:94:e1 00:1e:0b:2b:eb:ed 8100 102: 802.1Q vid 500 pri 2 192.168.0.2 > 192.168.0.1: icmp: echo reply (id:21e1 seq:214) (ttl 64, id 42409, len 84) em0: 15:07:07.277901 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 1500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:07:07.278029 00:04:96:51:71:80 01:04:96:51:71:80 8100 66: 802.1Q vid 1500 pri 7 snap 0:e0:2b:0:bb sap aa ui/C len=37 15:07:07.576658 00:1e:0b:2b:eb:ed 88:ae:1d:b5:94:e1 8100 102: 802.1Q vid 1500 pri 2 192.168.0.1 > 192.168.0.2: icmp: echo request (id:21e1 seq:214) (DF) (ttl 64, id 0, len 84) 15:07:07.576788 88:ae:1d:b5:94:e1 00:1e:0b:2b:eb:ed 8100 102: 802.1Q vid 1500 pri 2 192.168.0.2 > 192.168.0.1: icmp: echo reply (id:21e1 seq:214) (ttl 64, id 42409, len 84) This was tested with an extreme networks summit 450 switch with prio tagging on the ports going into the fw on both sides and clients on untagged ports on both sides. Again, many thanks and I hope this could be implemented with or without a knob. //Peter
