[hipl-users] Re: Test fails due to use the HIT as a *real* address

  • From: "Jesús Rojo Martínez" <jrojomartinez@xxxxxxxxx>
  • To: hipl-users@xxxxxxxxxxxxx
  • Date: Thu, 8 Feb 2007 17:11:26 +0100

Hi!,

If I make a ping or ping6 to the peer name, it works perfectly. But if I
> try to make the connection test it works if I specify the addresses, but
not
> if I specify the name (well, after many tries, with your prebuilt image,
it
> connects, but the same, with plain TCP, not using HIP at all).

Does this work:

   hipconf add map PEER_HIT PEER_IP
   ping6 PEER_HIT


 No, no at all :S It says:

node1:~/tcpdump-3.8.3# hipconf add map
2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb 10.0.1.2
debug(hipconf.c:374@hip_conf_handle_map): action=1 optc=2
debug(debug.c:566@hip_print_hit): id:
2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb
debug(misc.c:479@convert_string_to_address): Mapped v4 to v6
debug(debug.c:544@hip_print_lsi): mapped v6: 10.0.1.2
debug(message.c:99@hip_send_recv_daemon_info): waiting to receive daemon
info
debug(message.c:109@hip_send_recv_daemon_info): 88 bytes received
info(hipconf.c:1060@hip_do_hipconf): hipconf command successfull
node1:~/tcpdump-3.8.3# ping6 2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb
connect: Resource temporarily unavailable


It seems almost everything OK, at least it retrieves the HIT and the
> addresses correctly... But, why does it remove all the ip address and
tries
> to connect *directly* to the HIT? Is that normal? Obviuosly when it
tries to
> connect to the HIT (as it was a *real* adddress), it fails.

Connecting directly to the HIT is ok. The IP address information is sent
and stored to the HIP daemon.


 Aha, that's what I didn't understand. Thanks.

Can you show the complete contents of /etc/hipd_config, /etc/hip/hosts and
/etc/hosts.


#/etc/hip/hipd_config
add map 2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb 10.0.1.2
add map 2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb 3ffe::2

add map 2001:0070:7484:0667:34ea:658b:ccbb:ef09 10.0.1.2
add map 2001:0070:7484:0667:34ea:658b:ccbb:ef09 3ffe::2

#/etc/hip/hosts
2001:0073:1a32:d033:b07c:4e08:3f60:6294 node1
2001:007c:a6dc:f37c:96b6:3d3e:2c42:099d node1
2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb node2
2001:0070:7484:0667:34ea:658b:ccbb:ef09 node2

#/etc/hosts
127.0.0.1       localhost
127.0.1.1       node1.verkstad.net      node1

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

10.0.1.1        node1
3ffe::1           node1
10.0.1.2        node2
3ffe::2           node2

tcpdump -n -i any esp or proto 253 or port 50500


 I cannot get tcpdump compiling correctly with the patch for HIP. Actually,
there are some dependencies with an archive called hip.h that I have found
only in HIPL version 0.1.1 :S And in something related to the kernel! :S
(Now only BEET mode is in the kernel and everything outside, as far as I
understood, right?).

 I found some of the definitions on that file in libhiptool/protodefs.h and
I included that directory as it's said in the instructions of the HIP patch
for tcpdump, but it still fails. I made a symbolic link to protodefs from
net/hip.h and it seems to work better (since it finds now most of the
definitions), but there are still some simbols missing... How did you get
tcpdump working with that patch?

 Anyway, I got ethereal working, but there is no HIP mesages, just some
tries to send I1 to the DNS server and to the OpenDHT server, obviously it
fails and fallback to normal TCP connections, but then, when it tries to
contact the desired peer, it makes it directly with a SYN TCP packet (no HIP
at all).


Also, what version of HIPL userspace software are you running?


 The last one in the nightly tarball from 7th  February (Ie been trying
several tarballs, as well as the releases 1.0.0 and 1.0.1).

GAI ERROR -2: Name or service not known

conntest-client-gai is forced to use HIP or nothing at all. The error
tells that there were nothing to connect to.


 Mmm, ok. But then... what about the first error? There I got
conntest-client-gai (GAI) connecting to the peer through plain TCP (not HIP
at all, no ESP to encrypt...).

conntest-client uses opportunistic mode of HIP. It can do fallback to IP
and actually you don't need any HIT configuration with it. However, I'd
appreciate if you could try out once again with client-gai.


 I've been only using client-gai...

 Thank you a lot again :)
 Hope you can help me better now with this information.

--
Jesús Rojo Martínez.
Human Resource responsible BEST Stockholm - Kungliga Tekniska Högskolan
BEST - Board of European Students of Technology (www.BEST.eu.org)

e-mail: jrojomartinez@xxxxxxxxx
phone: +46704369273
MSN: jrojomartinez@xxxxxxx

Other related posts: