Re: Unable to ping6 on local network im vmware

Hello,

My experience suspects the use of dummy itself - I have seen strange things
happening while using it for more than basic stuff.
I would suggest running tcpdump on dummy0 and examine if ICMP replies (or
neighbour information for that matter) are being sent. You could also try
bridging with a real interface (perhaps try some veth combo).

If vmware-bridge creates a br-interface like brctl does, you could also try
assigning your XX::1 ip to that interface.

Greetings,

Christian Svensson
System administrator - Kalmar NDC <http://codelead.se>


On Fri, Feb 4, 2011 at 21:13, Jan Lühr <[email protected]> wrote:

> Hello,
>
> I've started to use  IPv6 on Debian Lenny. To do so I set up an HE-/64
> Tunnel an registered an a routed /48 block
>
> tunnel is: 2001:470:1f14:1460::/64
> Routed block is: 2001:470:d600::/48
>
> The tunnel is running fine - and I can Ping ipv6 hosts outside.
> he-ipv6   Link encap:IPv6-in-IPv4
>          inet6 addr: fe80::ac10:f801/64 Scope:Link
>          inet6 addr: 2001:470:1f14:1460::2/64 Scope:Global
>          inet6 addr: fe80::ac12:1/64 Scope:Link
>          inet6 addr: fe80::576a:da85/64 Scope:Link
>          inet6 addr: fe80::ac10:1/64 Scope:Link
>          UP POINTOPOINT RUNNING NOARP  MTU:1280  Metric:1
>          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:458 (458.0 B)  TX bytes:618 (618.0 B)
>
> Furthermore I assigned a /64slice of 2001:470:d600::/48 to dummy0
>
> dummy0    Link encap:Ethernet  HWaddr e6:70:b6:3e:23:e7
>          inet addr:172.18.0.1  Bcast:172.18.0.255  Mask:255.255.255.0
>          inet6 addr: 2001:470:d600::1/64 Scope:Global
>          inet6 addr: fe80::e470:b6ff:fe3e:23e7/64 Scope:Link
>          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 B)  TX bytes:14232 (13.8 KiB)
>
> and set up raddvd to announc auto-configuration
> interface dummy0
> {
>   AdvSendAdvert on;
>   prefix 2001:470:d600::1/64
>   {
>   };
> };
>
> routing seems to be running fine and I can reach  2001:470:d600::1 from the
> outside
> ip -6 route
> 2001:470:1f14:1460::1 dev he-ipv6  metric 1024  mtu 1280 advmss 1220
> hoplimit 4294967295
> 2001:470:1f14:1460::/64 via :: dev he-ipv6  metric 256  mtu 1280 advmss
> 1220 hoplimit 4294967295
> 2001:470:d600::/64 dev dummy0  metric 256  mtu 1500 advmss 1440 hoplimit
> 4294967295
> fe80::/64 dev vmnet1  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
> fe80::/64 dev vmnet8  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
> fe80::/64 dev eth0  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
> fe80::/64 dev dummy0  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
> fe80::/64 via :: dev he-ipv6  metric 256  mtu 1280 advmss 1220 hoplimit
> 4294967295
> default via 2001:470:1f14:1460::1 dev he-ipv6  metric 1024  mtu 1280 advmss
> 1220 hoplimit 4294967295
>
> ping from miredo / toredo client:
> ping6 2001:470:d600::1
> PING6(56=40+8+8 bytes) 2001::5ef5:79fd:1c04:3ba8:a8b0:4d4c -->
> 2001:470:d600::1
> 16 bytes from 2001:470:d600::1, icmp_seq=0 hlim=61 time=125.626 ms
> 16 bytes from 2001:470:d600::1, icmp_seq=1 hlim=61 time=27.079 ms
> 16 bytes from 2001:470:d600::1, icmp_seq=2 hlim=61 time=27.759 ms
>
> dummy0 is assigned to a vmware-bridge, that is connected to a debian lenny
> guest.
> The guest got its radvd announce and set up his interfacse:
>
> eth1      Link encap:Ethernet  HWaddr 00:0C:29:BB:D7:70
>          inet addr:172.18.0.2  Bcast:172.18.0.255  Mask:255.255.255.0
>          inet6 addr: 2001:470:d600:0:20c:29ff:febb:d770/64 Scope:Global
>          inet6 addr: fe80::20c:29ff:febb:d770/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:34 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:6820 (6.6 KiB)  TX bytes:4602 (4.4 KiB)
>
> ip -6 route
> 2001:470:d600::/64 dev eth1  proto kernel  metric 256  expires 2147074sec
> mtu 1500 advmss 1440 hoplimit 4294967295
> fe80::/64 dev eth1  metric 256  expires 21325411sec mtu 1500 advmss 1440
> hoplimit 4294967295
> fe80::/64 dev eth0  metric 256  expires 21325466sec mtu 1500 advmss 1440
> hoplimit 4294967295
> default via fe80::e470:b6ff:fe3e:23e7 dev eth1  proto kernel  metric 1024
>  expires 1717sec mtu 1500 advmss 1440 hoplimit 64
>
> The interface itself is running fine, the guest is able to ping 172.18.0.1
> (IPv4 address of host), but he's not able to ping6 2001:470:d600::1.
> Even more, the guest seems to be unaware of his neighbor:
>
> ping6 2001:470:d600::1
> PING 2001:470:d600::1(2001:470:d600::1) 56 data bytes
> From 2001:470:d600:0:20c:29ff:febb:d770 icmp_seq=1 Destination unreachable:
> Address unreachable
>
> ip -6 neig
> fe80::e470:b6ff:fe3e:23e7 dev eth1 lladdr e6:70:b6:3e:23:e7 router STALE
> 2001:470:d600::1 dev eth1  FAILED
>
> What might be wrong here?
> Thanks in advance,
> J.Luehr
>
> --
> To UNSUBSCRIBE, email to [email protected]
> with a subject of "unsubscribe". Trouble? Contact
> [email protected]
> Archive:
> http://lists.debian.org/[email protected]
>
>
> --
> Meddelandet har kontrollerats mot virus samt skadligt
> innehåll av MailScanner och förmodas vara säkert.
>
>