Ipv6 - problem with multicast addresses
Brecht Vermeulen
brecht.vermeulen at rug.ac.be
Tue Feb 26 11:43:39 EST 2002
I've looked at the ipv6->ipv4 trace and I think our problems are not
that related. I think your problem is explainable as already done by
Eddie :-) :
your IPv6 host sends a sollicitation, the translator answer with an
advertisement, the IPv6 sends an echo request, the translator replies
with a destination unreachable (this will be Linux itself I think) but
the packet gets translated (by click) and so on.
The only problem there is that for the final reply from translator to
IPv6: the translator does a neighbor sollicitation from fe80::200...
which is the link local address. It asks who has 3ffe...:2 but the IPv6
doesn't respond with an advertisement. Do you receive this sollicitaion
on your IPv6 machine ?
You use a bsd and a linux machine, so that's an extra possible place for
problems :-).
Have you tried to run this in kernel level click (in a previous mail I
saw you had a patched kernel which wasn't needed for userlevel click I
think) ?
If you don't run click and don't run ipv6 on the translator machine, can
you sniff the neighbor sollicitation messages from the Ipv6 machine on
the translator ? (assumed that the routes on the Ipv6 machine are okay)
Normally I would think that you must be able to run on the translator
machine click with a translator (or pure ipv6 configuration) without the
linux ipv6 module.
regards,
Brecht
Juan Luis Baptiste wrote:
>
> > > If the ipv6 module is loaded, ping6'ing ::172.25.0.3 and using a sniffer, I can see that the translator responds >to the ipv6 machine with an destination unreachable message, but click translates the packet and send it to >172.25.0.3. This machine replies to the packet but again the translator responds to it with an destination >unreachable message, and the packet never goes back to the ipv6 machine.
> >
> > mmm, and what are the 'destination unreachable messages' which are sent
> > ?
> > with our configuration the first host just doesn't receive anything and
> > says destination unreachable, but it doesn't get such messages. Do you
> > have a tcpdump trace of all these ?
> >
>
> The ipv6 host doesn't get the dest unreachable mssages, I see them on the capture.
>
> Yes, I sending a ethereal capture with this mail.
>
> bye
>
> Juan Luis
> --
>
> Get your free email from www.linuxmail.org
>
> Powered by Outblaze
>
> ------------------------------------------------------------------------
> Name: gt64_debug-17022002.tar.gz
> gt64_debug-17022002.tar.gz Type: Unix Tape Archive (application/x-tar)
> Encoding: base64
More information about the click
mailing list