[LARTC] Re: What am I missing?

[LARTC] Re: What am I missing?

[Jarek Poplawski]

Ray Van Dolson <rayvd <at> digitalpath.net> writes:

> 
> On a custom compiled Linux 2.6.13 kernel...
> 
> # tc qdisc add dev ppp145 handle ffff: ingress
> # tc filter add dev ppp145 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 384kbit
> burst 10k drop flowid :1
> RTNETLINK answers: Invalid argument
> 
> This works fine on a CentOS machine and my Fedora Core 2 box with default
> kernel.  I'm trying to figure out what is missing in the custom built 2.6.13
> kernel.  strace isn't real helpful, and there doesn't appear to be a way to
> make tc present more useful error messages...
> 
> Non ingress filtering works.  Here's an excerpt from kernel config:
...

> Any ideas?  Can paste entire kernel config if necessary.

You didn't write anything about this box: distro or previous kernel.
Maybe you should try to recompile or get newer version of iproute?

Jarek P.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

[LARTC] Re: What am I missing?

[Ray Van Dolson]

Follow-up to my own post here:

  http://marc.theaimsgroup.com/?l=lartc&m\x115332794424197&w=2

Problem ended up being that the tc included in the iproute RPM in Fedora
Core 2 was built specifically against the headers in the glibc-kernheaders
RPM.

When I switched to a custom kernel (for built-in MPPE support), apparently
some symbols referenced in the glibc-kernheaders package are not present in
the non-RH kernel.  This was causing my issue.

Solution was to modify the .spec file for iproute and tell it to compile
against my custom kernel's headers specifically.

Specifically I had to make the following changes to the .spec file to get
things to work:

 - Modify iproute2-2.4.7-kernel.patch to point to /usr/src/linux/include
 - Do not apply iproute2-2.4.7-misc.patch
 - Do not apply iproute2-2.4.7-in_port_t.patch

This makes everything happy once again!  I'm not sure what the consequenes
are of not applying those RedHat patches, but the tool still works normally
as far as I can tell.

Ray
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc