On Thu, 12 Jul 2001, Stefan Thom wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Steve,
>
> > stefan,
> >
> > the ipv6 bits in the 2.4.4 kernel are broken. you should upgrade
> > to the kernel to 2.4.6...
> >
> > -steve
>
> I did as you proposed and (good news!) the dual pcmcia sleeve is
> supported by kernel 2.4.6 now :-))
right. jamey carried that forward from 2.4.4.
> But the interface still does not pick up the sitelocal address, and
> if I assign it manually it does also not respond on pings. I tried a
> WaveLAN and a Xircom 10/100BaseT. Both cards are picking up a IPv4
> DHCP but no IPv6 Prefix.
>
> Who has IPv6 working on 2.4.6 kernel?
we do, and one possible reason that you don't see a v6 address if dhcp is
running is that i've seen dhcp mess up auto-address configuration. you
should see a link-local address but nothing else.
try this:
-turn off dhcp
-put an ipv6 router on the same subnet
then bring up the interface manually thus:
with a wireless, make sure you set the essid to an access point on an
ipv6-friendly subnet. then do an ifconfig eth0 inet6 up, and then you can
do an ifconfig eth0 <v4 address>.
things to check: are your ethernet cards on the handhelds/wiki list of
ones known to work? are their drivers v6 friendly (wvlan_cs is, don't
know about others)? you may have to do some testing/debugging here. is
there a non-ipv6-compliant router somewhere, 'cause it'll blow away any
packet that doesn't have a 4 in the first byte.
also remember, that if you have to set an address manually, then routing
is surely hosed, too, so pinging is gonna be tough. got a v6 compliant
ping?
final hint: ipv6 is supposed to do stateless auto address configuration,
and likewise for its routing. if this isn't working, nothing else will
behave in a reasonable manner. one cause: if your network environment is
exposed to unfriendly routers, you're hosed.
-steve
[snip]
Received on Fri Jul 13 17:03:44 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:38:27 EDT