OpenVZ Forum


Home » General » Support » tc RTNETLINK answers: Invalid argument / We have an error talking to the kernel
tc RTNETLINK answers: Invalid argument / We have an error talking to the kernel [message #50894] Sat, 23 November 2013 03:48 Go to previous message
piplite is currently offline  piplite
Messages: 27
Registered: March 2008
Junior Member
Hello.
Can anyone please recommend a solution for the problem with tc rule setup. Im not sure if its ovz kernel related by decided to ask it here anyway.

Here is what i got for error messages:
root@a-5 ~ # /bin/sh -c tc\ filter\ add\ dev\ vlan496\ parent\ 1:\ prio\ 142\ protocol\ ip\ u32\ match\ ip\ src\ 93.171.21.3\ flowid\ 1:142
RTNETLINK answers: Invalid argument
We have an error talking to the kernel


ipv6 on the other hand works perfectly fine
root@ ~ # /bin/sh -c tc\ filter\ add\ dev\ vlan496\ parent\ 1:\ prio\ 101\ protocol\ ipv6\ u32\ match\ ip6\ src\ 2a02:128:4:5::10\ flowid\ 1:101
root@ ~ # /bin/sh -c tc\ filter\ del\ dev\ vlan496\ parent\ 1:\ prio\ 101\ protocol\ ipv6\ u32\ match\ ip6\ src\ 2a02:128:4:5::10\ flowid\ 1:101


iproute is the stable version for Debian 7 - http://packages.debian.org/wheezy/iproute
iproute-dev installed too

Linux kernel 2.6.32-042stab081.5

# lsmod |egrep -i "sch*|cls|cqb|htb"
sch_ingress             2116  1
cls_u32                 6802  1
sch_sfq                 5779  1
sch_htb                15572  2
xt_DSCP                 2913  0
xt_dscp                 2105  0
fscache                53079  1 nfs
scsi_transport_sas     35503  1 mpt2sas


here is my ifconfig
# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:25:90:83:24:26
          inet6 addr: fe80::225:90ff:fe83:2426/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:1291709796 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1416374081 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:644877381022 (600.5 GiB)  TX bytes:976947258877 (909.8 GiB)
          Interrupt:16 Memory:dfc00000-dfc20000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:169135 errors:0 dropped:0 overruns:0 frame:0
          TX packets:169135 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9051662 (8.6 MiB)  TX bytes:9051662 (8.6 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1216035326 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1234115696 errors:0 dropped:5427 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:692529324124 (644.9 GiB)  TX bytes:633737631447 (590.2 GiB)

vlan496   Link encap:Ethernet  HWaddr 00:25:90:83:24:26
          inet addr:93.171.21.1  Bcast:93.171.216.255  Mask:255.255.255.0
          inet6 addr: fe80::225:90ff:fe83:2426/64 Scope:Link
          inet6 addr: 2a02:128:4::5/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1287339327 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1234841418 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:626530343357 (583.5 GiB)  TX bytes:964240099115 (898.0 GiB)

vlan496:1 Link encap:Ethernet  HWaddr 00:25:90:83:24:26
          inet addr:93.171.22.1  Bcast:93.171.217.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

root@ #


Any recommendation on where to look for problem would be very very much appreciated.
thank you.

[Updated on: Sat, 23 November 2013 03:49]

Report message to a moderator

 
Read Message
Read Message
Previous Topic: Vps with VPN
Next Topic: NOHZ: local_softirq_pending 100 - is there something to worry about?
Goto Forum:
  


Current Time: Sat Jul 27 22:29:13 GMT 2024

Total time taken to generate the page: 0.02680 seconds