[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: Fri, 9 Feb 2007 17:27:59 +0100
Hi again! :)
Hmm, what kernel did you install? Did you say that you used a binary
kernel or did you patch it yourself?
I've been trying with my own patched&compiled kernels: 2.6.16.x and now
2.6.19.2, I (think I) have tried the precompiled one you give ( 2.6.17.14).
I'll try it again (end of this mail).
After you have tried a connection, what do the following commands display:
* uname -a
* lsmod
* setkey -D
* route -6 -n
* ifconfig
* pidof hipd
node1:~# uname -a
Linux node1 2.6.19.2 #1 SMP Thu Feb 1 19:34:25 CET 2007 i686 GNU/Linux
node1:~# lsmod
Module Size Used by
xfrm6_mode_beet 3616 0
xfrm4_mode_beet 3424 0
esp4 7360 0
esp6 7328 0
dummy 2980 0
xfrm_user 22112 1
xfrm4_tunnel 2656 0
tunnel4 3396 1 xfrm4_tunnel
xfrm6_tunnel 7264 0
tunnel6 3428 1 xfrm6_tunnel
ppdev 8804 0
lp 11044 0
button 6704 0
ac 5220 0
battery 9988 0
ipv6 226432 16 xfrm6_mode_beet,esp6,xfrm6_tunnel,tunnel6
deflate 3840 0
zlib_deflate 18232 1 deflate
twofish 8544 0
twofish_common 36064 1 twofish
serpent 18944 0
aes 28128 0
blowfish 9440 0
des 17504 0
cbc 4448 0
ecb 3584 0
blkcipher 5664 2 cbc,ecb
sha256 11136 0
sha1 2688 0
crypto_null 2656 0
af_key 32752 0
dm_snapshot 16708 0
dm_mirror 20176 0
dm_mod 52088 2 dm_snapshot,dm_mirror
loop 15976 0
tsdev 7552 0
parport_pc 32644 1
serio_raw 6724 0
floppy 54084 0
parport 33608 3 ppdev,lp,parport_pc
i2c_piix4 8300 0
rtc 12468 0
i2c_core 20640 1 i2c_piix4
psmouse 34856 0
pcspkr 3136 0
evdev 9376 1
ext3 123912 1
jbd 54248 1 ext3
mbcache 8420 1 ext3
ide_disk 15584 3
8139too 25536 0
8139cp 22208 0
mii 5376 2 8139too,8139cp
piix 9444 0 [permanent]
generic 5508 0 [permanent]
ide_core 112264 3 ide_disk,piix,generic
thermal 13864 0
processor 30472 1 thermal
fan 4772 0
node1:~# setkey -D
No SAD entries.
node1:~# route -6 -n
Kernel IPv6 routing table
Destination Next
Hop Flags Metric Ref Use Iface
::1/128
:: U 0 1 1 lo
2001:73:1a32:d033:b07c:4e08:3f60:6294/128
:: U 0 0 1 lo
2001:73:1a32:d033:b07c:4e08:3f60:6294/128
:: U 1024 0 0 dummy0
2001:75:7922:b367:f79e:c3c2:5cfe:1489/128
:: U 0 0 1 lo
2001:75:7922:b367:f79e:c3c2:5cfe:1489/128
:: U 1024 0 0 dummy0
2001:76:74e0:4890:9db4:fc87:caa2:bfbd/128
:: U 0 0 1 lo
2001:76:74e0:4890:9db4:fc87:caa2:bfbd/128
:: U 1024 0 0 dummy0
2001:7c:a6dc:f37c:96b6:3d3e:2c42:99d/128
:: U 0 0 1 lo
2001:7c:a6dc:f37c:96b6:3d3e:2c42:99d/128
:: U 1024 0 0 dummy0
2001:70::/28
:: U 256 0 0 dummy0
3ffe::1/128
:: U 0 16 1 lo
3ffe::/64
:: U 256 0 0 eth0
fe80::989f:c4ff:fe68:d43a/128
:: U 0 0 1 lo
fe80::a8cc:ff:fe00:bd01/128
:: U 0 2 1 lo
fe80::/64
:: U 256 0 0 eth0
fe80::/64
:: U 256 0 0 dummy0
ff00::/8
:: U 256 0 0 eth0
ff00::/8
:: U 256 0 0 dummy0
node1:~# ifconfig
dummy0 Link encap:Ethernet HWaddr 9A:9F:C4:68:D4:3A
inet6 addr: fe80::989f:c4ff:fe68:d43a/64 Scope:Link
inet6 addr: 2001:73:1a32:d033:b07c:4e08:3f60:6294/28 Scope:Global
inet6 addr: 2001:75:7922:b367:f79e:c3c2:5cfe:1489/28 Scope:Global
inet6 addr: 2001:7c:a6dc:f37c:96b6:3d3e:2c42:99d/28 Scope:Global
inet6 addr: 2001:76:74e0:4890:9db4:fc87:caa2:bfbd/28 Scope:Global
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:1260 (1.2 KiB)
eth0 Link encap:Ethernet HWaddr AA:CC:00:00:BD:01
inet addr:10.0.1.1 Bcast: 10.255.255.255 Mask:255.0.0.0
inet6 addr: 3ffe::1/64 Scope:Global
inet6 addr: fe80::a8cc:ff:fe00:bd01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1075 errors:0 dropped:0 overruns:0 frame:0
TX packets:1000 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:997591 (974.2 KiB) TX bytes:186801 ( 182.4 KiB)
Interrupt:16 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2160 (2.1 KiB) TX bytes:2160 (2.1 KiB)
node1:~# pidof hipd
6929
node1:~#
So, yes, now a 2.6.19.2, there is no SAD (obviusly, the connection failed
with the name and used plain TCP when the addresses were specified). I think
all the modules are loaded, right?
Do you see any output of hipd e.g. in /var/log/syslog? Some "hip_error"
lines?
Mmm, some, but doesn't look extrange. Just this ones:'
Feb 9 16:06:28 node1 hipd[6929]: error(nlink.c:1073@parse_rtattr) Deficit
len 28, rta_len=0
[...]
Feb 9 16:06:35 node1 hipd[6929]: error(
hadb.c:310@hip_hadb_add_peer_info_complete)
Ignoring new mapping, old one exists
(These ones above are repeated several times)
Feb 9 16:11:04 node1 hipd[6929]: error(netdev.c:394@hip_netdev_handle_acquire)
if_index NOT determined
Feb 9 16:11:04 node1 hipd[6929]: error(hipd.c:534@main) Netlink receiving
failed
Do they say you something?
You have set two IPs per node. Try having a single IP per node by
commenting extra IPs with # in the beginning of the line.
That was my first try (well, with just one HIT and two IPs... I'll try
only one IP, results are down together with the precompiled version of
kernel&HIPL). Since it didn't work I tried it again with two. Does it matter
which HIT I am using?
tcpdump -n -i any esp or proto 253 or port 50500
Please just show the tcpdump output as it is without any patching.
Nothing. It doesn't capture anything :S I have OpenDHT disable, if I use
an enable hipl version I see something (probably is not because the dht,
cuase what I see is independently of it, and I try it again and now it
doesn't show anything :S). So, when executing client-gai:
16:37:40.178069 IP6 3ffe::1 > 3ffe::2: ip-proto-253 40
16:37:40.193023 IP6 3ffe::2 > 3ffe::1: ip-proto-253 576
16:37:40.246468 IP6 3ffe::1 > 3ffe::2: ip-proto-253 824
16:37:42.130213 IP6 3ffe::1 > 3ffe::2: ip-proto-253 40
16:37:42.139876 IP6 3ffe::2 > 3ffe::1: ip-proto-253 760
16:37:42.199715 IP6 3ffe::1 > 3ffe::2: ip-proto-253 640
16:37:42.467241 IP6 3ffe::2 > 3ffe::1: ip-proto-253 128
*** Precompiled Version of Kernel and HIPL:
Same configuration as previous tries:
It directly fails to connect with:
node1:~# conntest-client-gai node2 tcp 1111
name='node2' service='1111'
flags: 800
not IPv4 or IPv6 address, resolve name (!AI_NUMERICHOST)
HIP_TRANSPARENT_API: fetch HIT addresses
name='planetlab1.diku.dk' service='5851'
flags: 8000
not IPv4 or IPv6 address, resolve name (!AI_NUMERICHOST)
HIP_TRANSPARENT_API: fetch HIT addresses
HIP_TRANSPARENT_API: AI_HIP unset: get IPv6 addresses too
Dumping the structure
AF_INET in_addr=0xc0266d8f (192.38.109.143)
Dumping the structure after removing IP addreses
AF_INET in_addr=0xc0266d8f (192.38.109.143)
Connect: Connection refused
Resolving and connecting failed.
node1:~#
And this is quite extrange: First that fails to connect to the OpenDHT,
even if the network works well; second that it needs to connect to the DHT
when the mapping are already in the config file.
And tcpdump captures some packets, BUT previous to the execution of the
client-gai (but after the execution of the server in the peer):
node1:~# tcpdump -n -i any esp or proto 253 or port 50500
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
16:56:59.093473 IP 10.0.1.2 > 10.0.1.1: ip-proto-253 40
16:57:05.205681 IP 10.0.1.2 > 10.0.1.1: ip-proto-253 40
Any ideas?
Let's try with only one HIT and only one IP address...
Well, after changing the conf and restart the daemon, I have realized that
it complains about a missing module in your prebuilt version (I guess is
builtin the kernel), but just in case:
node1:/etc/hip# /etc/init.d/hipd start
Starting hipd.
FATAL: Module xfrm4_mode_beet not found.
FATAL: Module xfrm6_mode_beet not found.
debug(hipconf.c:367@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(debug.c:566@hip_print_hit): id:
3ffe:0000:0000:0000:0000:0000:0000:0002
info(hipconf.c:955@hip_do_hipconf): hipconf command successfull
And again, the same exctly error as above (with several HITs and IPs), but
no packets captured at all with tcpdump.
And also again, if I try to connect directly specifying the address
instead of the name, it connects throught plain TCP (no packets captured in
tcpdump and client-gai connects perfeclty).
Sorry if there are too much information now in this mail, but I hope it
can be useful.
Any new idea?
--
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:
