[Dibbler] Relay Configuration Problem

Jimmy Ott admin at onnet.ch
Wed May 4 09:40:27 CEST 2005


many thanks for the quick fix. i appreciate your work!

.. but, i have still a problem with the relay, and now, it doesn't look
so easy as yesterday.

same network layout, same config, but new relay from cvs.
relay log:

2005.05.04 09:33:46 Rel Critical  | Dibbler - a portable DHCPv6, version
0.4.0-CVS (May  4 2005 00:24:08) (RELAY)
2005.05.04 09:33:46 Rel Critical  | Authors : Tomasz
Mrugalski<thomson(at)klub.com.pl>,Marek Senderski<msend(at)o2.pl>
2005.05.04 09:33:46 Rel Critical  | Licence : GNU GPL v2 or later.
Developed at Gdansk University of Technology.
2005.05.04 09:33:47 Rel Critical  | Homepage: http://klub.com.pl/dhcpv6/
2005.05.04 09:33:47 Rel Notice    Detected iface Wireless Network
Connection/6, flags=0, MAC=00:02:2d:43:77:ff.
2005.05.04 09:33:48 Rel Notice    Detected iface Local Area
Connection/5, flags=5, MAC=00:00:39:24:d1:e1.
2005.05.04 09:33:48 Rel Notice    Detected iface Teredo Tunneling
Pseudo-Interface/4, flags=0, MAC=ff:ff:ff:ff:ff:ff:ff:ff.
2005.05.04 09:33:48 Rel Notice    Detected iface 6to4
Pseudo-Interface/3, flags=5, MAC=ff:ff:ff:ff.
2005.05.04 09:33:49 Rel Notice    Detected iface Automatic Tunneling
Pseudo-Interface/2, flags=5, MAC=ac:10:01:0a.
2005.05.04 09:33:49 Rel Notice    Detected iface Loopback
Pseudo-Interface/1, flags=13, MAC=.
2005.05.04 09:33:49 Rel Debug     Parsing relay.conf config file...
33:49 Debug     Parsing config done.
33:49 Debug     1 interface(s) specified in relay.conf
33:50 Info      Interface Local Area Connection/5 configuration has been
loaded.
33:50 Warning   There is only one interface defined. At least two is a
sanite configuration.
33:50 Warning   Both server and client support is defined on the Local
Area Connection/5 interface.
33:51 Notice    Creating srv unicast (fd00::1:5479:5aa7:4f80:497f)
socket on the Local Area Connection/5 interface.
33:51 Notice    Creating clnt multicast (ff02::1:2) socket on the Local
Area Connection/5 interface.
33:51 Notice    Accepting messages.
34:03 Debug     Received 80 bytes on the Local Area Connection/5
interface (socket=1728, addr=fe80::200:39ff:fe10:3aa2, port=547).
34:04 Notice    Received SOLICIT on Local Area
Connection/5,TransID=0x28de, 4 opts: 1 3 8 6
34:04 Notice    Relaying message on the Local Area Connection/5
interface to unicast (fd00:0:0:3::a) address.
34:04 Notice    Accepting messages.
34:04 Error     sock_recv(1752,...) failed.
34:04 Debug     Received 80 bytes on the Local Area Connection/5
interface (socket=1728, addr=fe80::200:39ff:fe10:3aa2, port=547).
34:05 Notice    Received SOLICIT on Local Area
Connection/5,TransID=0x28de, 4 opts: 1 3 8 6
34:05 Notice    Relaying message on the Local Area Connection/5
interface to unicast (fd00:0:0:3::a) address.
34:05 Notice    Accepting messages.
34:06 Error     sock_recv(1752,...) failed.


many thanks for your help!!
cheers jimmy


Tomasz Mrugalski wrote:
> On Tue, 3 May 2005 somebody known as Jimmy Ott wrote:
> 
>> the client now sends a dhcpv6 solicitation message, the relay receive
>> this, and try to relay to fd00:0:0:3::a, but nothing happens, i also
>> don't see a packet when i trace with ethereal besides the IPv6
>> Solicitation Packet from the Client. the client try in different
>> intervals, as specified, to get an ip via the relay....
>>
>> on the top of the relay log i see something very strange:
>> 32:30 Notice    Creating srv unicast (fe80::200:39ff:fe24:d1e1) socket
>> on the Local Area Connection/5 interface.
>> 32:30 Notice    Creating clnt multicast (ff02::1:2) socket on the Local
>> Area Connection/5 interface.
>>
>> does the relay try to reach the routeable multicast address
>> fd00:0:0:3::a via it's link-local address????
> 
> Oops. I have checked it and found an intersting comment in the code:
> 
> RelTransMgr.cpp:82: // FIXME: global or site-scoped address should be used
> 
> Well, that explains it. This is definetly a Dibbler bug. I have added it
> to the bugzilla (see bug #113). I have fixed it in no time. I'm
> compiling new CVS snapshot right now. Linux binaries and source version
> will be available in an hour or so. I'll try to prepare Windows binaries
> too, but this might take some time.
> 
>> on the server, i'm using the cvs version.
>> attached are the configs and the logs.
> 
> Thanks. Those log files were really helpful.
> 
> Cheers,
> 



More information about the Dibbler mailing list