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

  • From: Miika Komu <miika@xxxxxx>
  • To: hipl-users@xxxxxxxxxxxxx
  • Date: Wed, 21 Feb 2007 19:51:54 +0200 (EET)

On Wed, 21 Feb 2007, Jesús Rojo Martínez wrote:

Hi!,

Last tests with patch-204. I use "make deb" and then install the debian
package.
I've seen two behaviors:

- With some config in /etc/hip/hipd_config:
client-gai get frozen at "Waiting for daemon info", as previous tries.
I attach the log from syslog in the file "syslog-hipd_config".

Can you get the newest version and try to repeat? Thanks.

- Without any config in hipd_config:
It seems to work, at least it doesn't stop... but fails to connect.
Log from syslog attached in file "syslog".
Output from client-gai is:

node2:~# conntest-client-gai node1 tcp 1111
...
Trying to connect to 2001:73:1a32:d033:b0c7:4e08:3f60:6294
After call conntest.c: connect to 2001:73:1a32:d033:b0c7:4e08:3f60:6294
connect ret=-1 errno=11
trying next
failed to connect


I hope you can see the problem now with the information in the syslogs...

Ok, I think I got it finally. The daemon mistakenly tries to get a route to the peer IP address using dummy0 (which contains only HITs!):

Feb 21 12:28:36 node2 hipd[13226]: debug(debug.c:566@hip_print_hit) Peer HIT: 2001:0073:1a32:d033:b0c7:4e08:3f60:6294 Feb 21 12:28:36 node2 hipd[13226]: debug(debug.c:566@hip_print_hit) Peer addr: 3ffe:0000:0000:0000:0000:0000:0000:0001 Feb 21 12:28:36 node2 hipd[13226]: debug(debug.c:566@hip_print_hit) Getting route for destination address: 3ffe:0000:0000:0000:0000:0000:0000:0001 Feb 21 12:28:36 node2 hipd[13226]: error(nlink.c:1078@parse_rtattr) Deficit len28, rta_len=0 Feb 21 12:28:36 node2 hipd[13226]: debug(debug.c:566@hip_print_hit) src: 2001:007c:d397:1b35:2ae9:cea3:5fcc:1afb Feb 21 12:28:36 node2 hipd[13226]: debug(hadb.c:416@hip_hadb_add_peer_info) Source address found Feb 21 12:28:36 node2 hipd[13226]: info(hidb.c:724@hip_for_each_hi) Found HIT0x2001007cd3971b352ae9cea35fcc1afb

Looking at your earlier posts, you have this route:

  dummy0 3ffe::1/128                                

Do this and try again:

  ip route del 3ffe::1/128 dev dummy0

Why did you add that weird route in the first place? Got desparate during first failures ?)

--
Miika Komu                                       http://www.iki.fi/miika/

Other related posts: