[hipl-dev] ping6 is strange - Re: Re: Manual needs updating for hacking with NC

  • From: Robert Moskowitz <rgm@xxxxxxxxxxxxxxx>
  • To: hipl-dev@xxxxxxxxxxxxx
  • Date: Thu, 10 Apr 2014 13:53:44 -0400


On 04/10/2014 01:10 PM, Miika Komu wrote:
Hi,

On 04/10/2014 07:46 PM, Robert Moskowitz wrote:

On 04/10/2014 12:35 PM, Miika Komu wrote:
Hi,

On 04/10/2014 01:14 AM, Robert Moskowitz wrote:
In "Testing a HIP connection with an IPv6 application", the manual has:

nc6 -l -p 1111

on the server side.  For at least Centos 6.5 and Fedora 20 it is:

nc -6 -l 1111

NC now has a 4|6 switch and -p is not used, it is assumed.

nc and nc6 are two different separate software

And I can't find nc6 for Fedora of Centos.  But nc has the -6 switch.
Which seems to work...

ping/ping6 is better because it shows addresses. Check my previous email.

Well, I just tried the test with ping6 and two VERY strange things are happening....

First the HIP/ESP connection is going over IPv4! Here is what I am seeing on the server (oqo1) that is being ping6ed:

# tcpdump -n -i any esp or proto 139 or port 10500
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes 13:38:47.716801 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 44 13:38:47.765559 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 652 13:38:47.778138 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 44 13:38:47.778608 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 652 13:38:47.944827 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 628 13:38:48.012749 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 628 13:38:48.118548 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 628 13:38:48.224315 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 220 13:38:48.777077 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:48.777590 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:49.090208 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:38:49.090523 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:38:49.737200 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:49.737499 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:50.928676 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:50.928992 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:51.699093 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:51.699408 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:52.232209 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:38:52.436739 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:38:52.706022 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:52.706336 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:53.696799 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:53.697116 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:54.797116 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:54.797421 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:55.786866 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 116 13:38:55.787049 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 116 13:38:55.855803 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:38:55.856022 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:38:58.443075 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:38:58.528275 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:02.029417 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:02.029587 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:04.534076 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:04.928087 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:07.129497 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:07.129670 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:10.934556 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:11.310683 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:13.229639 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:13.229793 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:16.316896 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:16.379066 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:19.308022 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:19.308345 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:22.386284 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:22.527777 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:25.478163 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:25.478498 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:28.535133 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 68 13:39:28.926721 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 68 13:39:31.380303 IP 70.194.7.152.8311 > 208.83.67.139.hip-nat-t: UDP, length 212 13:39:31.427307 IP 208.83.67.139.hip-nat-t > 70.194.7.152.8311: UDP, length 212


Neat? That is from a ping6 and supposedly there is IPv6 connectivity (I can ping6 to an ipv6 address, but it looks like Verizon blocks all inward connections?).

The stranger thing is what ping6 is reporting.  I enter:

ping6 oqo1.htt-consult.com


I get back:

PING oqo1.htt-consult.com(crossroads.infrahip.net) 56 data bytes
64 bytes from crossroads.infrahip.net: icmp_seq=2 ttl=46 tiem=306ms
....

WHAT is going on with the reverse lookup???

From tcpdump there is no question that oqo1 is being pinged. Not crossroads!



Other related posts: