Ok, looks like I had to create the qdisc first before I can create a filter.

On Sun, Jun 28, 2015 at 5:05 AM, Podrigal, Aron <ar...@guaranteedplus.com>
wrote:

> After looking a bit more, it looks to me that this is what was happening
> (correct me if I'm wrong). looks like those filter types are now statically
> linked into tc. But if the parameters given to  tc could not be understood
> using any statically linked algorithms, tc tries to dynamically load other
> libraries matching matched by keywords within the command line arguments.
> However I still do not understand why my command is not valid.
>
> On Sun, Jun 28, 2015 at 4:02 AM, Podrigal, Aron <ar...@guaranteedplus.com>
> wrote:
>
>> I am trying to do traffic shaping using tc, however I can't add any
>> filters and am getting this  generic error message
>>
>> RTNETLINK answers: Invalid argument
>> We have an error talking to the kernel
>>
>>
>> A simple strace shows that the problem is that it can't find the required
>> filter type libraries in /usr/lib/tc/<filter_type>
>>
>> socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 3
>> setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
>> setsockopt(3, SOL_SOCKET, SO_RCVBUF, [1048576], 4) = 0
>> bind(3, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 0
>> getsockname(3, {sa_family=AF_NETLINK, pid=13737, groups=00000000}, [12])
>> = 0
>> open("/usr/lib/tc//f_u32.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
>> file or directory)
>> sendto(3,
>> "(\0\0\0\22\0\1\3\6\267\217U\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
>> 40, 0, NULL, 0) = 40
>> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
>> msg_iov(1)=[{"l\4\0\0\20\0\2\0\6\267\217U\2515\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0"...,
>> 16384}], msg_controllen=0, msg_flags=0}, 0) = 3420
>> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
>> msg_iov(1)=[{"\24\0\0\0\3\0\2\0\6\267\217U\2515\0\0\0\0\0\0", 16384}],
>> msg_controllen=0, msg_flags=0}, 0) = 20
>> sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
>> msg_iov(1)=[{",\0\0\0,\0\5\6\7\267\217U\0\0\0\0\0\0\0\0\2\0\0\0\0\0\0\0\377\377\377\377"...,
>> 44}], msg_controllen=0, msg_flags=0}, 0) = 44
>> recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=00000000},
>> msg_iov(1)=[{"@\0\0\0\2\0\0\0\7\267\217U\2515\0\0\352\377\377\377,\0\0\0,\0\5\6\7\267\217U"...,
>> 16384}], msg_controllen=0, msg_flags=0}, 0) = 64
>> write(2, "RTNETLINK answers: Invalid argum"..., 36RTNETLINK answers:
>> Invalid argument
>> ) = 36
>> write(2, "We have an error talking to the "..., 39We have an error
>> talking to the kernel
>> ) = 39
>> close(3)                                = 0
>> exit_group(2)                           = ?
>> +++ exited with 2 +++
>>
>>
>> Iv'e tried searching for any related packages that would provide it, but
>> no success. Can anyone point out if there was any changes to file
>> locations? or if this is a bug?
>>
>>
>> Thank you.
>>
>> --
>> Aron Podrigal
>> -
>> //Be happy :-)
>>
>
>
>
> --
> Aron Podrigal
> -
> //Be happy :-)
>



-- 
Aron Podrigal
-
//Be happy :-)

Reply via email to