lundi 5 janvier 2015

Is Traffic control inside namespace supported?


I am trying to limit the bandwidth of an interface inside a namespace using tc without much success. Seems it's not supported according to http://ift.tt/1xzrePG


This is on CentOS 6.5


The following command just fails with RTNETLINK answers: Invalid argument:



# ip netns exec qrouter-6a080f37-4da0-4646-ad36-062b748d15be tc qdisc add dev qr-a9b3962f-d4 root netem loss 30%
RTNETLINK answers: Invalid argument
[root@node-1 ~]# ip netns exec qrouter-6a080f37-4da0-4646-ad36-062b748d15be ip a
43: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
44: qg-4bda7108-d2: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:95:cc:7b brd ff:ff:ff:ff:ff:ff
inet 119.81.159.206/27 brd 119.81.159.223 scope global qg-4bda7108-d2
inet 119.81.159.207/32 brd 119.81.159.207 scope global qg-4bda7108-d2
inet 119.81.159.209/32 brd 119.81.159.209 scope global qg-4bda7108-d2
inet6 fe80::f816:3eff:fe95:cc7b/64 scope link
valid_lft forever preferred_lft forever
47: qr-a9b3962f-d4: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether fa:16:3e:c2:64:dd brd ff:ff:ff:ff:ff:ff
inet 192.168.99.1/24 brd 192.168.99.255 scope global qr-a9b3962f-d4
inet6 fe80::f816:3eff:fec2:64dd/64 scope link
valid_lft forever preferred_lft forever
# ip netns exec qrouter-6a080f37-4da0-4646-ad36-062b748d15be tc qdisc add dev qr-a9b3962f-d4 root tbf rate 1mbit burst 10kb limit 100kb
RTNETLINK answers: Invalid argument


Aucun commentaire:

Enregistrer un commentaire