Hello, On Wed, 30 Mar 2005 09:12:32 +0200, Peter Bieringer <[EMAIL PROTECTED]> wrote: > > > --On Wednesday, March 30, 2005 12:25:01 AM +0100 Pedro Tom� > <[EMAIL PROTECTED]> wrote: > > > Hello all! > > I'm developing a micro-mobility protocol in an IPv6 network for my > > final degree project but I'm having some problems using IPv6. > > > > Imagine the following, simple, situation: > > I'm connecting only two machines, a gateway and a pc that will work as > > an access point using hostap. I have assigned global IPv6 addresses > > (2000::etc/3) to simplify things (the protocol v4 is using global ipv4 > > for the machines) and my network is an island isolated from the > > internet. > > > > I've configured the routes to be point-to-point from the GW to the AP > > and vice-versa. > > When I try to ping the AP from the GW, the src addr of the packets > > transmited from the GW is the global IPv6 addr that I've assigned to > > the GW (so far so good), but when I try to ping the GW from the AP, > > the src addr of the packets transmited from the AP is the link local > > IPv6 addr autoconfigured by the AP... why is that? shouldn't the src > > addr be the global addr ? they behave differently, the GW and the > > AP...in either situations, the src addr should be OR the link local, > > or the global addr, but the should be the same type of addr in both > > situation. > > That's very strange, because the scope should always be the same. What > happen using e.g. telnet? >
telneting from the AP to the GW gives me the same thing... src : AP link local addr dest: GW global ip addr telneting from the GW to the AP gives me the (right?) src and dest. addr: src: GW global addr dest: AP global addr in both situation the scope should be the same, all global or all local...I agree :( > Looks like something is going wrong here. Take a look in on both sides: > > # ip -6 addr show > # ip -6 route show > # ip -6 neigh show > # sysctl -a | grep ipv6 > ip -6 addr show and ip -6 route show gives the things that I've showed in the previous mail ip -6 neigh show, done after some ping/telnet/whatever gives in the GW: fe80::201:29ff:fed0:8b59 dev eth1 lladdr 00:01:29:d0:8b:59 nud delay 2000::201:29ff:fed0:8b59 dev eth1 lladdr 00:01:29:d0:8b:59 nud reachable in the AP: fe80::240:f4ff:fe84:2b7f dev eth0 lladdr 00:40:f4:84:2b:7f nud delay 2000::240:f4ff:fe84:2b7f dev eth0 lladdr 00:40:f4:84:2b:7f nud reachable and it looks right, I guess... the sysctl-a | grep ipv6 gives me the same thing in GW and AP (except for the normal stuff from the other GW interfaces) --------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
