On Thu, 03 Feb 2011 21:42:59 -0600
Grant Taylor <gtaylor@xxxxxxxxxxxxxxxxx> wrote:
> On 2/3/2011 2:01 PM, Ethy H. Brito wrote:
> > One extra detail is: this setup was working (just as it is for eth0)
> > until two weeks ago when then we created the vlans and splited the
> > traffic among them.
>
> Once the traffic is in side of a VLAN tag (on the raw device), filters
> will not match the traffic the say way that it did. - Try applying
> your filters to the VLAN sub-interface.
you mean:
tc filter add dev vlanA ... match mark client1
tc filter add dev vlanB ... match mark client1
tc filter add dev vlanC ... match mark client1
...
for each client?!?!?! the will be hundreds!!
DoesnÂt it imply having "tc {class,qdisc} add dev vlan[A-Z]" or "
tc {class,qdisc} add dev eth1" will do?
>
> This is because the traffic is no longer IP traffic in side of Ethernet
> SNAP frames, but rather VLAN tagged frames that contain Ethernet SNAP
> frames.
>
> Are you wanting to give one VLAN on a given raw interface more priority
> than another?
Nope. The vlans are to other ISPs. Each ISP demands 2 Vlans (IPv4+IPv6).
I need to shape global traffic from/to each client no matter which ISP
he/she is using.
Ethy
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
