(usagi-users 03284) Re: Radvd and default route problem with router/client configuration

Hi,

your answer seems quite logical to me, but if this is the normal behaviour,
then why the PC sometimes accepts and uses the routes learned via radvd??

Tobias


> Hi Tobias,
> 
> there is one simple answer to your problem: this behavior ist quite
> normal. 
> At the time you enable forwarding using "sysctl 
> net.ipv6.conf.all.forwarding=1" you have to configure the routing
> manually.
> For further information please read the section
> /proc/sys/net/ipv6/* Variables
> in your <KERNEL-SOURCE-PATH>/Documentation/networking/ip-sysctl.txt.
> 
> regards
> André
> 
> --On Donnerstag, 24. März 2005 12:22 +0100 Tobias Hof <[email protected]>
> wrote:
> 
> > Hi everybody,
> >
> > I have the following configuration on a Fedora Core 3 machine with a
> > 2.6.8.1 kernel (No, I cannot change the kernel version for the
> moment...):
> >
> > 2 interfaces
> > - eth0 is attached to a router and is autoconfigured via radvd from this
> > router and has also an additional fixed IPv6 address
> (3ffe:0:a:d0a:e::/64,
> > from
> > ifcfg-eth0)
> > - eth1 has only a fixed address (3ffe:0:a:d29:e::/64, from ifcfg-eth1)
> >
> > On this machine, I'm running the zebra daemon from Quagga 0.97 in order
> to
> > send router
> > advertisements (prefix 3ffe:0:a:d29::/64) over eth1 into the network
> > behind eth1.
> >
> > Of course, I also want to do forwarding between the two interfaces and
> so
> > I set sysctl net.ipv6.conf.all.forwarding=1 which works without
> problems.
> >
> > Now, my problem is the following:
> > Sometimes, the forwarding works from eth1 to eth0 and sometimes (after a
> > reboot or a "service network restart") it does not. I found out that
> when
> > it does not work, the reason is that the default route learned by radvd
> > on eth0 ( "...via <linklocal-@ of router where eth0 is connected to> dev
> > eth0" ) is not taken into account for the forwarding. So, my machine
> does
> > not know where to route packets to other networks than
> > 3ffe:0:a:d0a::/64.
> > Furthermore, I found out that if I delete the default route learned by
> > radvd and then re-add it myself manually, the forwarding always works.
> >
> > Does anybody has a clue what this could be due to??
> >
> > Is this a known kernel problem or is this due to the mixed configuration
> > of my PC (client and router at hte same time)? The strange thing is that
> > the behaviour is not alwyas the same, sometimes it's fine, sometimes
> not,
> > unpredictable...
> >
> > If anybody out there has an idea, I would appreciate any hint or
> answer..!
> >
> > Thanks a lot in advance!
> > Tobias
> >
> > --
> > Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl
> >
> 
> 
> 
> 

-- 
Sparen beginnt mit GMX DSL: http://www.gmx.net/de/go/dsl