Ipv6 - problem with multicast addresses

Frederik Scholaert Frederik.Scholaert at rug.ac.be
Mon Feb 25 12:12:59 EST 2002


Hi,

I'm experimenting with IPv6 in click. It works pretty well except for the
fact that i'm not able to receive all-nodes or all-router multicast
addresses in my click config.

My configuration is like this:

|HOST|-ETH1-fec0:0:0:1::65/64---ETH1-|CLICK ROUTER|-ETH2---fec0:0:0:2::66/64-ETH1-|HOST|
                          [fec0:0:0:1::64/64]  [fec0:0:0:2::64/64]


The IPv6-addresses fec0:0:0:1::64 and fec0:0:0:2::64 are not really
assigned because IPv6 is not loaded on the click router.

When for instance the IPv6 Click config is loaded and i load IPv6 on the
left host, the all-routers sollicitation packets don't seem to arrive at
the click router. Or, when i do a ping fec0:0:0:2::66 on the left host, i
see 'fec0:0:0:1::65 > ff02::1:ff00:64: icmp6: neighbor sol: who has
fec0:0:0:1::64' -packets (leaving?) on eth1 of the left host, but they
also do not seem to arrive at the click router. (I have a Print-element
there after a FromDevice(eth1,1)-element and see nothing).

But when i first load the IPv6-module on the click-router and actually
assign the fec0:0:0:1::64 and fec0:0:0:2::64 addresses, and then
afterwards load click, i can ping through the click router.

I don't think it should have to be this way. Shouldn't i be able to run a
IPv6 click config completely indepedent of IPv6 in the Linux kernel?

I use a click-version from january (from cvs), and kernel 2.2.19.

Can somebody help me on this matter?

regards,
Frederik





More information about the click mailing list