I changed the IP addr of the AP to /3 instead of /128...it was a stupid distraction that made me do that...after that, the problem of the ping GW -> AP with the src addr = link local was resolved...the AP uses his global address now!
And I can now enable forwarding in the AP that the ping's still work! Now I have some other problem with forwarding in the gateway but I'll try to google a little more to see if I can find a solution...if not, then I will bother you all :) Thanks everybody, Pedro On Wed, 30 Mar 2005 14:26:17 +0200 (CEST), Ed Kapitein <[EMAIL PROTECTED]> wrote: > Hi Pedro, > > I cut and paste some of your output and comment in between > > > >AP stuff: > >result of ifconfig > >eth0 Link encap:Ethernet HWaddr 00:01:29:D0:8B:59 > > inet addr:172.20.72.4 Bcast:172.20.255.255 > >Mask:255.255.255.0 > > You ipv4 netmask and broadcast are not correct. this has nothing to do > with the ipv6 issue, but you might want to correct it anyway. > 172.20.72.4 with netmask > 255.255.255.0 should result in a bcast address of > 172.20.72.255 > > > inet6 addr: 2000::201:29ff:fed0:8b59/128 Scope:Global > > inet6 addr: fe80::201:29ff:fed0:8b59/64 Scope:Link > > > your ipv6 mask is also incorrect. the way it is configured now would leave > only 1 host in the 2000::201:29ff:fed0:8b59 network. > Change this to 2000::201:29ff:fed0:8b59/64 for example > > And i use #ipv6 on irc://irc.ipv6.freenode.net > > I hope this helps. > > Kind regards, > @ > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pedro Tome' [EMAIL PROTECTED] INESC-id Grupo de Computa��o Natural ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
