Linux QOS ipv4 affects kernel using zebra for ipv6

[Smith, Mark - Sydney]

Well, I haven't had the specific problem you having, but I have been having
trouble with zebra on a 2.4.18 kernel, on a debian 2.2 box.

Specifically, I can't get zebra to recognise and advertise new IPv6 prefixes
via ripng when I bring up a new interface. Initially I thought it was
because I didn't compile in netlink support, but after doing that, the zebra
daemon does recognise when I bring up / down  the interface externally,
assign a prefix via "ip addr add" etc, but ripng just won't advertise it out
the other Ripng enabled interfaces, when I add that interface to the "router
ripng" config section.

Strangely enough, this only seems to happen after the machine is booted. I
have boot scripts on the box that bring up the interfaces, assign prefixes,
and then run zebra / ripng, it all works fine (I'm initially running zebra
with an ethernet (facing a ripng running cisco router) and a tap interface,
with http://openvpn.sf.net sitting behind it, running a virtual ethernet
tunnel to my home over a dial up link.).

I do have all of netfilter compiled in, with all the options / plug ins
enabled, but I haven't actually done any netfilter config yet.

Could be a netfilter code / zebra / ripng conflict as you suggest.

Hope this helps a bit,
Mark.

> -----Original Message-----
> From: Xavier Sudre [mailto:xavier@sudre.fr]
> Sent: Friday, 10 May 2002 7:59
> To: Xavier Sudre
> Cc: 6bone@ISI.EDU
> Subject: Re: Linux QOS ipv4 affects kernel using zebra for ipv6
> 
> 
> 
> So do I have to suppose nobody had this poblem before ?
> 
> On Wed, May 08, 2002 at 05:26:54AM +0200, Xavier Sudre wrote:
> > Hi everybody,
> > 
> > I sent 3 days to find the trouble I had with dynamic 
> routing tool zebra
> > and I have isolate a problem into the netfilter code of the 
> kernel or
> > the iptables tool.
> > 
> > In faact I have QOS on my linux box running Debian with 2.4.18 usagi
> > kernel. The QOS is applied to ipv4 stack using iproute tool 
> routing with
> > the help of packet marquing.
> > To mark packets I use iptables and the mangle table like this:
> > 
> > iptables -t mangle -A OUTPUT -m length --length 0:500 -j 
> MARK --set-mark
> > 3
> > 
> > iptables -t mangle -A OUTPUT -m length --length 500:1500 -j MARK
> > --set-mark 4
> > 
> > I use tc tool to create cues and filter packet marked by iptables.
> > 
> > I have isolated this two lines of iptables marking process 
> and they are
> > doing a very starnge stuff on my dynamic routing process in ipv6.
> > I use zebra bgp facilities for ipv6 and using it it does not
> > redistribute routes to the kernel when marking process is used.
> > In this case I have the following error message from the kernel:
> > 
> > kernel: route_me_harder: 
> ip_route_output_key(dst=213.91.4.3, src=80.65.229.50,
> > oif=7, tos=0x0, fwmark=0x0) error -19
> > 
> > I searched for a solution and switched form kernel 2.4.18 
> to 2.4.18 usagi, and 
> > I have also tried the 2.4.19-pre8 kernel but I get always 
> the same eror
> > message. 
> > 
> > I am using the latest iptables 1.2.6a, and there is no bug known on
> > their web-site for that problem.
> > 
> > Do you have any solution or any experience with this problem ?
> > 
> > I really hope that you would be able to help me because QOS 
> is a big part
> > of my ipv4 routing and I dont want to slow down in ipv6 because of
> > ipv4...
> > 
> > Thanks,
> > -- 
> > Xavier Sudre
> > URL: <http://www.sudre.fr>
> > EMAIL: <xavier@sudre.fr>
> > 
> 
> -- 
> Xavier Sudre
> URL: <http://www.sudre.fr>
> EMAIL: <xavier@sudre.fr>
>