On Wed, 30 Mar 2005 09:30:52 +0200 (CEST), Ed Kapitein <[EMAIL PROTECTED]>
wrote:
> Hi Pedro,
>
> I think that there is something wrong with the routing tables on you machine.
> perhaps you can send the output of ifconfig and ip -6 route show to the
> list, so we can take a closer look.
GW stuff:
(eth1 is the interface connecting to the AP)
result of ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:40:F4:84:2B:7F
inet addr:172.20.72.2 Bcast:172.20.255.255 Mask:255.255.255.0
inet6 addr: 2000::240:f4ff:fe84:2b7f/128 Scope:Global
inet6 addr: fe80::240:f4ff:fe84:2b7f/64 Scope:Link
result of ip -6 route show
2000::201:29ff:fed0:7c84 dev eth2 metric 1 mtu 1500 advmss 1440 metric10 64
2000::201:29ff:fed0:8b59 dev eth1 metric 1 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev eth2 metric 256 mtu 1500 advmss 1440 metric10 64
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 1
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 metric10 1
ff00::/8 dev eth2 metric 256 mtu 1500 advmss 1440 metric10 1
default dev eth2 proto kernel metric 256 mtu 1500 advmss 1440 metric10 64
default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 metric10 64
default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 metric10 64
unreachable default dev lo proto none metric -1 error -101 metric10 255
so, packets to the AP will go through eth1
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.255
inet6 addr: 2000::201:29ff:fed0:8b59/128 Scope:Global
inet6 addr: fe80::201:29ff:fed0:8b59/64 Scope:Link
result of ip -6 route show
2000::201:29ff:fed0:7ba3 dev eth0 metric 1 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev wlan0 metric 256 mtu 1500 advmss 1440 metric10 64
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 metric10 1
ff00::/8 dev wlan0 metric 256 mtu 1500 advmss 1440 metric10 1
default dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 metric10 64
default dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 metric10 64
unreachable default dev lo proto none metric -1 error -101 metric10 255
the 2000::201:29:ff:fed0:7ba3 is the GW eth0 interface IP, not the GW
eth1 IP (this is because of the protocol structure itself)
so, pings to the GW eth1 IP will go through eth0 (default)
with these routing tables and IP I can ping 2000::240:f4ff:fe84:2b7f
(GW eth1) from the AP and ping 2000::201:29ff:fed0:8b59 (AP eth0)
from the GW... when I turn on ipv6forwarding on the AP these pings
stop working.
> Besides that, did you really mean to use a 2000::/3 addres? that seems
> like a rather big chunk of address space.
yes, I know. But it was suggested to me to use that, to be like the
protocolv4 that uses global ip's too. I remind that the network is
isolated so there isn't conflict problems with assigned worldwide
global ip's.
> If you are familiar with irc, you can try the #ipv6 channel to get more
> realtime help.
yes, I am :D #ipv6 in what network?
thanks,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Pedro Tome' [EMAIL PROTECTED]
INESC-id Grupo de Computa��o Natural
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
