[hipl-users] Re: Some HIPL -questions

  • From: Väisänen Teemu <teemuuolevivaisanen@xxxxxxxxx>
  • To: hipl-users@xxxxxxxxxxxxx
  • Date: Mon, 22 Aug 2005 12:31:57 +0300

2005/8/19, Miika Komu <miika@xxxxxx>:
> On Fri, 19 Aug 2005, Väisänen Teemu wrote:
> 
> > Hi, I have few questions about using HIPL:
> >
> > 5. I have tried 'Chapter 6. Testing a HIP connection between two hosts'
> > and it seems to work, at least text typed in crash appear to oops.
> > Sometimes # tools/hipconf add hi default gives after 'Calculated RSA
> > HIT' -message next messages in both crash and oops:
> >
> > setsockopt failed (-1)
> > sending msg failed
> >
> > What they might mean?
> >
> > After them connection might still work fine..
> 
> See from "/var/log/kern.log" if you compiled CONFIG_HIP_DEBUG. It might be
> that the delay between the execution of hipmod and "hipconf add hi
> default" is too little. Can you repeat this?

I can't find that file even I compiled kernel with CONFIG_HIP_DEBUG.
After few tests, seems that after computer reboot,
# modprobe hipmod
and running first time
# hipconf add hi default
there aren't those messages.. If using same hipconf -command later
again, they might come up.

> > 6.
> > Before starting HIPL,  ping6 has to work both ways, and using HIPL
> > also, but sometimes routes seems to disappear and HIPL connections and
> > ping6 doesn't work anymore. So I have to add routes back and after
> > them connections work again. Has someone seen this problem?
> 
> Seems odd to me, and may not related HIP. I usually use an "isolated"
> network for the HIP hosts, and the routes are configured upon boot-up:
> 
> panu:~# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0
> iface eth0 inet static
>         address 10.0.0.3
>         netmask 255.255.255.0
>         network 10.0.0.0
>         broadcast 10.0.0.255
>         gateway 10.0.0.1
>         # dns-* options are implemented by the resolvconf package
>         dns-nameservers 10.0.0.1
>         dns-search localnet
> 
> iface eth0 inet6 static
>         address 3ffe::3
>         netmask 64

Seems that there are something wrong with routes or something, as you
though not related to HIP. ping6 doens't work from crash to oops
before pinging from oops to crash... I haven't figured out reason yet.
Crash's address is 3ffe::1 and oops' 3ffe::2 as in examples. There are
no other computers in network. In Fedora these addresses are defined
in /etc/sysconfig/network-scripts/ifcfg-eth0 -file:

DEVICE=eth0
ONBOOT=yes
TYPE=Ethernet
NETWORKING_IPV6=yes
IPV6INIT=yes
IPV6ADDR="3ffe::X/64"  # where X=1 in crash and 2 in oops

I added those IPV6 -features there. 

After
# service network restart
ifconfig shows addresses right and both hosts have in Kernel IPv6 routing table:
Destination 3ffe::/64 Iface eth0, so ping6 should go to both way.

-Teemu Väisänen

Other related posts: