OpenVZ Forum


Home » General » Support » 6to4 - tunnel for VE (IPv6 to IPv4 tunnel for VE)
Re: 6to4 - tunnel for VE [message #37135 is a reply to message #37011] Thu, 20 August 2009 14:37 Go to previous message
shion is currently offline  shion
Messages: 5
Registered: August 2009
Junior Member
The tcpdump was taken from the VE and there are no firewall rules installed on HN and VE.

Well, I have added your rule on the HN but I'm not sure if it is active, because I get only a empty result with the following command.
# ip -6 neigh show

I have found this comment:
"Strangely, the ip neighbor show command does not display any entries added and deleted with ip neighbor add proxy, so arp is required to view these entries. In short, don't use ip neighbor add proxy. "

"#arp -a -n" shows me only IPv4 addresses. Either "ip neighbor add proxy" wasn't successful or I do something wrong with arp.
Is there another way to control whether the command "ip neigh add proxy" was successful?

Ping from VE
# ping6 ipv6.google.com
PING ipv6.google.com(ey-in-x68.google.com) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5030ms


tcpdump from VE
# tcpdump -i venet0 -n
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooked socket
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
13:33:29.115424 IP 117.170.42.21.41339 > 117.170.42.99.53: 34024+ AAAA? ipv6.google.com. (33)
13:33:29.115653 IP 117.170.42.99.53 > 117.170.42.21.41339: 34024 2/0/0 CNAME[|domain]
13:33:29.116173 IP 117.170.42.21.37874 > 117.170.42.99.53: 6854+[|domain]
13:33:29.116554 IP 117.170.42.99.53 > 117.170.42.21.37874: 6854[|domain]
13:33:29.117074 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 1, length 64
13:33:29.159630 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 1, length 64
13:33:29.159663 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
13:33:30.131819 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 2, length 64
13:33:30.174764 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 2, length 64
13:33:30.174808 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
13:33:31.135296 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 3, length 64
13:33:31.178152 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 3, length 64
13:33:31.178189 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
13:33:32.135325 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 4, length 64
[...]


tcpdump from HN
# tcpdump -i venet0 -n
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooked socket
tcpdump: WARNING: venet0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
15:33:29.115424 IP 117.170.42.21.41339 > 117.170.42.99.53: 34024+ AAAA? ipv6.google.com. (33)
15:33:29.115653 IP 117.170.42.99.53 > 117.170.42.21.41339: 34024 2/0/0 CNAME[|domain]
15:33:29.116173 IP 117.170.42.21.37874 > 117.170.42.99.53: 6854+[|domain]
15:33:29.116554 IP 117.170.42.99.53 > 117.170.42.21.37874: 6854[|domain]
15:33:29.119851 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 1, length 64 
15:33:29.159630 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 1, length 64
15:33:29.159663 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
15:33:30.161829 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 2, length 64  
15:33:30.174764 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 2, length 64
15:33:30.174808 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
15:33:31.176834 IP6 2002:75aa:2a15::1 > 2001:4860:a005::68: ICMP6, echo request, seq 3, length 64  
15:33:31.178152 IP 192.88.99.1 > 117.170.42.21: IP6 2001:4860:a005::68 > 2002:75aa:2a15::1: ICMP6, echo reply, seq 3, length 64
15:33:31.178189 IP 117.170.42.21 > 192.88.99.1: ICMP 117.170.42.21 protocol 41 port 0 unreachable, length 132
[...]

If I remember correctly, 6to4 tunneling is also referred as proto-41.
But I don't know the message "protocol 41 port 0 unreachable" and I don't find any helpful information about it with google.

[Updated on: Tue, 25 August 2009 09:46]

Report message to a moderator

 
Read Message
Read Message
Read Message
Previous Topic: openVZ-2.6.27 Ext4 stable patch?
Next Topic: RTNETLINK problem with tc
Goto Forum:
  


Current Time: Thu Aug 07 19:26:36 GMT 2025

Total time taken to generate the page: 1.01527 seconds