On Wed, 21 Jan 2004, Andreas Jellinghaus wrote:
> Hi,
Hello Andreas,
> could you give me a hint how to get it working?
since you are using link-locals, you at least need to specify which device
you are running your tunnel over. Try:
ipv6tunnel add ip6sec0 \
local fe80::202:ddff:fe32:6525 \
remote fe80::209:5bff:fe2f:ea7e \
dev wlan0
(or whatever your physical interface is called)
> Now, two things are strange:
> a) on my 2.6.1 machine / laptop:
...
> dream:~# ip -6 addr ls dev ip6sec0
...
> there is no link local address. why?
Hmm, strange. Do you have the string "init ip6-ip6: add_linklocal failed"
somewhere in your logs?
> Also the tunnel does not seem to work at all:
> ping6 -I ip6sec0 ip6-allnodes
> should send a ping via the tunnel, i.e. I
> should see a packet on wlan0 with ip6ip6 headers.
> But tcpdump shows no package at all.
When I define global endpoints to the tunnel I can also ping link-local
addresses over the tunnel, but it seems that link-local over link-local
doesn't work at the moment. The packets reach the ip6_tunnel, but get
silently discarded after that.
I'll look into this and see if anything can be done about it.
> There are some unrelated issues I foiund, maybe bugs
> in the linux ip stack?
> - using wlan0 the laptop can ping6 the gw fine.
> The other way it's not working:
Sorry about that, I already sent a patch to DaveM. Thanks for noticing :)
> now another issue: from laptop to gw:
...
> ping6 ip6-allnodes -I wlan0
Don't know anything about that, let's hope some one else can help you.
Regards,
Ville
--
Ville Nuorvala
Research Assistant, Institute of Digital Communications,
Helsinki University of Technology
email: vnuorval@tcs.hut.fi, phone: +358 (0)9 451 5257
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
