Hi,
Hello
I have few questions regarding tc functionality (qdiscs, classes, etc.) when
vlans are in use. For example, consider interface eth0, for which I create
and extra vlan with vconfig, let's say eth0.11. Then using tc I can add
usual things - qdiscs, filters, ... - to both eth0 and
Christian Benvenuti wrote:
Hi,
[cut]
Yes they are both allowed.
This means, for example, that the traffic that originates from
or that is addressed to a VLAN interface can potentially go through
two independent QoS configurations.
Depending on what you want to achieve, you may configure
Christian Benvenuti wrote:
Hi,
[cut]
Yes they are both allowed.
This means, for example, that the traffic that originates from
or that is addressed to a VLAN interface can potentially go through
two independent QoS configurations.
Depending on what you want to achieve, you may
Christian Benvenuti wrote:
This is one important detail you probably missed:
(Note that in this case the VLAN interface is a L3 interface)
If you assign an IP address to the VLAN interface and you transmit
IP traffic on that interface, than the traffic goes through the VLAN
qdisc config and
Hi,
.. so I'm probably missing / not seeing something simple, or I don't
know.
This setup works for real interface, as well as for bonding. During testing,
real interface is normally working in 192.168.100/24 subnet.
Is there an interface configured on the same VLAN on the other side
of the
Christian Benvenuti wrote:
Is there an interface configured on the same VLAN on the other side
of the link?
If there is not, ARP fails (no one replies to the requests) and you
[cut]
Bloody hell. I knew I missed something embarassing. Faked mac solved the
issue.
Thanks for help !
On Mon, 11 Jun 2007 22:11:09 +0200
Michal Soltys [EMAIL PROTECTED] wrote:
Christian Benvenuti wrote:
This is one important detail you probably missed:
(Note that in this case the VLAN interface is a L3 interface)
If you assign an IP address to the VLAN interface and you transmit
