|
AICCU setting up invalid route
![[se]](/s/countries/se.gif) Shadow Hawkins on Sunday, 17 June 2007 18:34:04
This is more a tip than it is a problem.
When I start my aiccu on Gentoo Linux, it normally works fine until recently that I think has to do with me adding "advanced routing" to the kernel because of several reasons, anyhow - aiccu adds the following route:
default via 2001:16d8:ff00:190::1 dev sixxs metric 1024 expires 21333787sec mtu 1280 advmss 1220 hoplimit 4294967295
Which is fine you'd think, but it'd seem that when the machine is an 'advanced router' that route doesn't work - i.e, it doesn't take it.
So what I did was to replicate that above route:
$ route -A inet6 add default gw 2001:16d8:ff00:190::1 dev sixxs
And it worked.
I analyzed it a little bit and the only visible difference I could find was this:
default via 2001:16d8:ff00:190::1 dev sixxs metric 1 expires 21334246sec mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:16d8:ff00:190::1 dev sixxs metric 1024 expires 21334058sec mtu 1280 advmss 1220 hoplimit 4294967295
That's right - the metric. I think it has to do with how the advanced router code tries to find a good route, lower metric seems to have it value it higher.
Just my two cents,
Ludvig Ericson.
AICCU setting up invalid route
Which kernel version is this. 2.6.20.x++ series seem to be heavily broken with respect to 'default' routing.
See this kernel bug for more information.
AICCU setting up invalid route
Shadow Hawkins on Wednesday, 11 July 2007 23:11:47
Linux 2.6.21-gentoo #2 SMP PREEMPT
AICCU setting up invalid route
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Monday, 18 June 2007 15:59:28
This might have something to do with the old (and now resurfaced?) bug that default routes are sometimes ignored in IPv6 in Linux. As a workaround I've used:
ip -6 route add 2000::/3 via 2001:14b8:100:69::1 dev sixxs
Currently I'm running CentOS 5 with kernel version 2.6.18-8.1.6.el5. I had the same problem with my previous Red Hat 9 gateway machine that was running kernel 2.4.20-28.9.
As a sidenote, I just installed aiccu on the new machine, replacing heartbeat-client I was running on the previous gateway. I had a hard time finding sample sixxs configuration information for aiccu. Maybe the configuration information is given to new users as a part of the signup / new tunnel creation, but it doesn't help those that are converting an older configuration. Via some trial and error it's working now, after I found the tic server name mentioned in one FAQ question.
AICCU setting up invalid route
This bug has been resolved in 2.6.21.5 and was a Kernel bug, not an AICCU bug.
As one is already 'on the edge' with their kernel, upgrading it should not be much of an hassle.
AICCU setting up invalid route
Shadow Hawkins on Monday, 26 November 2007 15:42:12
Yeah, I noticed that too - I guess I worded it pretty badly, even outright wrongly.
Though, it is indeed invalid if the intended action does not take place, but that's a matter of definition. :-P
AICCU setting up invalid route
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 10 December 2008 19:27:53
This bug is still in Centos 5.2 (2.6.18-91.1.18).
But is fixed (at least for me) in version 2.6.18-120 from RHEL53 beta.
So it should be fixed in RHEL53 final as well. Took only over a year! ;-)
Greeting
Jens Kühnel
AICCU setting up invalid route
Simple: vote with your money; aka better use something like Debian where people actually care about fixing things (and do so for free), instead of paying a company for not fixing your problems.
|
![[ch]](/s/countries/ch.gif)
on Sunday, 17 June 2007 18:54:16
Posting is only allowed when you are