[Dibbler] Re: Re: Problem with relays

kf kf at fourdays.com
Fri Apr 22 15:33:18 CEST 2005


Thank you for your reply. Your work is appreciated.

Here is the full view of our network topology. Keep in mind that this is a 
lab-setup:
http://www.fourdays.com/dibb/Full_network_topology_IPv6.png
(Image is created using Visio)

Both the routers running the relay and the server are running GNU/Linux.

Routers - Gentoo & Debian
Server - Ubuntu

Our server.conf and relay.conf can be found here. They are currently very 
simple and only for testing purposes:
Router 1: http://www.fourdays.com/dibb/relay1.conf
Router 2: http://www.fourdays.com/dibb/relay2.conf 
Server: http://www.fourdays.com/dibb/server.conf

-----

We also have some problems with requests going over both our relays. DHCP-
requests coming from Client Stan and travels over both relays/routers 
generates a server crash. Here is a full log from the server - 
http://www.fourdays.com/dibb/dibbler-server.log

The interface-id recognized att the server is the one from Router Kyle (Relay 
2).

We are not sure if it's the second relay that messes upp the message or if 
the problem lies on the server. Relays traveling over just Router Kyle (relay 
2) works fine.

Regards,
Kristoffer Fredriksson





On Thu, 21 Apr 2005 12:00:06 +0200 (CEST), dibbler-request wrote
> Send Dibbler mailing list submissions to
> 	dibbler at klub.com.pl
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://klub.com.pl/cgi-bin/mailman/listinfo/dibbler
> or, via email, send a message with subject or body 'help' to
> 	dibbler-request at klub.com.pl
> 
> You can reach the person managing the list at
> 	dibbler-owner at klub.com.pl
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dibbler digest..."
> 
> Today's Topics:
> 
>    1. Problems with relay (kf)
>    2. Re: Problems with relay (Tomasz Mrugalski)
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 20 Apr 2005 15:06:14 +0200
> From: "kf" <kf at fourdays.com>
> Subject: [Dibbler] Problems with relay
> To: dibbler at klub.com.pl
> Message-ID: <20050420122452.M14013 at fourdays.com>
> Content-Type: text/plain;	charset=iso-8859-1
> 
> Hello,
> 
> We are setting up a IPv6 lab environment and have some problems configuring
> relays.
> 
> Dibbler is installed on a server with one ethernet card. The server 
> is then connected to a computer acting as router. The router has 
> four ethernet cards and receives requests on three of them, each on 
> its own subnet, and then relays via multicast to the server. Our 
> problem is that we can't figure out how to configure the dibbler-
> server to accept three different interface-ids on the same 
> interface. All of our attempts to configure this has been 
> unsuccessful and we can't find any information about this in the 
> documentation. The problem we encounter (if the server successfully 
> parse the config) is that it tries to bind the socket twice.
> 
> Error     Unable to bind socket (iface=eth0/4, addr=ff05::1:3, 
> port=547).
> 
> Is what we are trying to do possible? We hope there is just a configuration
> error from our side. All sugestions on solutions are welcome.
> 
> Simplified Network Topology - http://www.fourdays.com/network_topology.png
> 
> Regards,
> Kristoffer Fredriksson
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 20 Apr 2005 20:32:57 +0200 (CEST)
> From: Tomasz Mrugalski <thomson at klub.com.pl>
> Subject: Re: [Dibbler] Problems with relay
> To: Dibbler users list <dibbler at klub.com.pl>
> Message-ID: <Pine.LNX.4.61.0504202016340.20395 at v13.klub.com.pl>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
> 
> On Wed, 20 Apr 2005 somebody known as kf wrote:
> 
> > We are setting up a IPv6 lab environment and have some problems 
configuring
> > relays.
> >
> > Dibbler is installed on a server with one ethernet card. The server is 
then
> > connected to a computer acting as router. The router has four ethernet 
cards
> > and receives requests on three of them, each on its own subnet, and then
> > relays via multicast to the server. Our problem is that we can't figure 
out
> > how to configure the dibbler-server to accept three different interface-
ids on
> > the same interface. All of our attempts to configure this has been
> > unsuccessful and we can't find any information about this in the
> > documentation. The problem we encounter (if the server successfully parse 
the
> > config) is that it tries to bind the socket twice.
> > Error     Unable to bind socket (iface=eth0/4, addr=ff05::1:3, port=547).
> >
> > Is what we are trying to do possible? We hope there is just a 
configuration
> > error from our side. All sugestions on solutions are welcome.
> 
> I have never thought about such topology, so I belive this cannot be 
> done. But what you are trying to accomplish is valid usage, so this 
> can be classified as a bug. I'm currently very busy, but is a few 
> days (probably in the beginning of the next week) I'll take a look 
> at that. I belive fixing this should be relatively easy. What 
> operating system are you using on the server and relay? As soon as I 
> fix this, I'll prepare an unofficial version for you, so you can 
> confirm (or deny) my fix.
> 
> I would also make things easier for me if you send me your 
> relay.conf and server.conf files.
> 
> > Simplified Network Topology - http://www.fourdays.com/network_topology.png
> Cool image. What software have you used to produce it?
> 
> Thanks for your bug report. I have added bug #112 to the Dibbler bug 
> database.
> 
> Regards,
> 
> -- 
> Tomasz Mrugalski,              | "I think there is a world market 
> for     | thomson(at)klub(dot)com(dot)pl |  about five computers."   
>                |                                |     Thomas J. 
> Watson (Chairman, IBM) 1943|
> 
> ------------------------------
> 
> _______________________________________________
> Dibbler mailing list
> Dibbler at klub.com.pl
> http://klub.com.pl/cgi-bin/mailman/listinfo/dibbler
> 
> End of Dibbler Digest, Vol 4, Issue 1
> *************************************



More information about the Dibbler mailing list