[olsr-dev] Fwd: [OLSR-users] olsrd on multiple interfaces
Pawel Foremski
(spam-protected)
Sun Sep 26 14:26:04 CEST 2004
Hi.
Yesterday I was asking about running olsrd on multiple interfaces with the
same IP address. It seems olsrd doesn't support such setup, so I wrote a
patch. Could you please tell me what do you think about it?
---------- Forwarded Message ----------
Subject: [OLSR-users] olsrd on multiple interfaces
Date: Saturday 25 of September 2004 21:19
From: Pawel Foremski <(spam-protected)>
To: (spam-protected)
Hi!
I'm running olsrd 0.4.7 on Linksys WRT-54G with OpenWRT firmware. I've got 5
interfaces on it (1 x wireless, 4 x Ethernet) I'd like to run olsrd on: eth0,
vlan1, vlan2, vlan3 and vlan4. The IP addresses are the same on each
interface.
I'm trying to deploy the following scenario: there are 3 machines, 10.1.0.1
(pc), 10.3.0.1 (wrt54g nr 2) and 10.2.0.1 (wrt54g) between them (the one I'm
currently fighting with :P). All of the machines are running olsrd 0.4.7. I'd
like to make 10.1.0.1 be able to communicate via 10.2.0.1 with 10.3.0.1,
simple. But the olsrd daemon running at 10.2.0.1 on multiple interfaces seems
to add all discovered routes only on the first interface from "INTERFACES"
list. In my setup the list is "vlan1 eth1 vlan2 vlan3 vlan4".
10.3.0.1, which I'm trying to contact from 10.1.0.1, is connected to eth1;
10.1.0.1 is connected to vlan1. So, olsrd running on 10.2.0.1 properly adds
the route to 10.1.0.1 (vlan1), but fails to add proper route to 10.3.0.1
(eth1), using vlan1 instead. Of course I can't contact 10.3.0.1 from
10.1.0.1.
And here is my question - is it a bug, am I missing something obvious or is
it a "feature" :P?
-------------------------------------------------------
--
Pawel Foremski
(spam-protected)
http://pjf.dotgeek.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: olsrd-interface.diff
Type: text/x-diff
Size: 3411 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20040926/9a05c4a5/attachment.diff>
More information about the Olsr-dev
mailing list