[OLSR-users] Wired Ethernet really isn't

[Andreas Tønnesen]

Allright - I'm making a bit too many assumptions here ;)

I've dealt with these LAN->WLAN bridges before, they weve actually the 
reason I removed some optimizations regarding wired links in the code. 
But setting NWMULTI to 1 should cause the same intervals to be used on 
it as on wireless interfaces. But as said before - this sould not really 
make any difference... The validity time of HELLO messages are also sent 
in the HELLO message and this is adjusted to the emission interval.

But there have been reported some strange errors before when using 
LAN->WLAN bridges... Can you provide some olsrd-logs from the node 
running the bridge?

regards,
Andreas


John Gorkos wrote:
> Hi Andreas-
>   Nah, you're making it sound too complicated.  I've got a regular old pentium 
> computer with two ethernet cards in it.  One is connected to the Real world, 
> and the other is connected to a SmartBridges AirBridge Outdoor.  The 
> AirBridge is really just a ethernet->802.11b converter.  So what I really 
> want is the second ethernet card (eth1) to _THINK_ it's a wireless interface, 
> because in reality it is.  It appears that there are different timeouts in 
> the config file for wired and wireless interfaces, and I want to use the 
> wireless values on the "wired" eth1 port, becuase it becomes a wireless 
> device just 2 meters down the cable.
>  Does that make a little more sense?  I'm not trying to do any bridging or 
> VLAN stuff here.  This is straight routing.
> 
> John Gorkos
> 
> On Wednesday 05 May 2004 11:07, you wrote:
> 
>>Hi John,
>>
>>I'm not 100% sure I understand your problem... But I reckon you've got a
>>setup like: br0(bridge)with connected interfaces wlan0 and eth0. I have
>>no experience using olsrd on bridge devices(if that is what you are
>>doing) but I guess it can cause great trouble due to the binding of
>>sockets to devices in olsrd.
>>You should always run olsrd on the actual interface(not a alias or
>>bridge or tunnel etc.). So in this cause you should use wlan0 and and
>>eth0 directly.
>>
>>However - if you just want non-wlan interfaces to act as wlan interfaces
>>you just set the NWMULTI option in the configfile to 1. But this should
>>have no effect on wether or not the node is seen by other nodes.
>>
>>When I run olsrd on the WRT54G (which I gues is the device used ;-) ) I
>>set the actual interfaces up with IP addresses(and I have disabled the
>>bridge between the switch and the wlan interface) and run olsrd on the
>>interfaces directly. This works fine.
>>
>>Finally a tip to WRT54G uses using OpenWrt. When configuring the wlan
>>interfaces give iwconfig ALL options at the same line! On my box
>>atleast, the interface is not updated unless this is done(even though
>>iwconfig reports the new values). Took me some hours to figure out :-(
>>
>>regards,
>>Andreas
>>
>>John Gorkos wrote:
>>
>>>Andreas/group-
>>>  I've got a wired ethernet card plugged directly into a wireless bridge
>>>in ad-hoc mode, meaning I want olsrd to treat it as a wireless interface,
>>>but since there are no wireless extensions on the interface, olsrd treats
>>>it as a wired interface.  The end result is that remote stations in the
>>>mesh never see the wireless bridge/router as a link partner, even though
>>>it is.  Of course, the wireless bridge/router combo sees all the other
>>>nodes in the network immediately.
>>>  Very occassionally the router/bridge will get seen by remote nodes, but
>>>the HELLO will almost immediately timeout and they'll lose interest in
>>>the bridge as a link partner.
>>>
>>>The question is, how do I fake the funk in the olsrd.conf to convince
>>>olsrd to treat eth1 (in this case) as a wireless interface instead of a
>>>wired interface?
>>>
>>>Thanks!
>>>John Gorkos
>>>_______________________________________________
>>>olsr-users mailing list
>>>(spam-protected)
>>>https://www.olsr.org/mailman/listinfo/olsr-users

-- 
Andreas Tønnesen((spam-protected))
UniK University Graduation Center
University of Oslo
http://www.olsr.org