Rajesh Narayanan | 5 Sep 2007 08:52
Picon

Dual Mode Operation: One WLAN interface for both 801.11 infrastructure & OLSR?

hi,

Here are some notes from trying to mess with dual mode operation.

Got the dual mode operation partly working.
1. ath0  in adhoc mode
2. ath1 in ap mode

Note that the adhoc mode interface needs to be created before the ap. If you do the other way around, the hardware does not allow you to add it. (sorry im not geeky enough to figure that out :-(  ). I just tried this on an intuition (and a couple of caffeine shots) and it seemed to do the trick.

I got OLSR running on the ath0 and seems to work ok. But still have not figured the ap mode as yet on ath1. I do get some MAC layer exchanges (arps) so I know the interfaces ARE ok. But face a bummer on the IP layer.

                         ath0       ath1
RouterA  <----------> RouterB <--------------> Laptop1
             192.168.50.X       192.168.60.X
              OLSR               
      <--- pings ok --->        <---pings not ok -->
                                      <-------- arps   ------>

Hope someone in the list can help.

Thanks,
Rajesh.



On 9/2/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:

On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:

> Not sure what the configuration is. But I dont think its likely to
> work. Atheros supports multiple modes but I didnt see anything
> related to a dual-mode operation.
>

Rajesh:

As said, I did not try it out myself but try this:
http://madwifi.org/wiki/ngFeatures

Is that what you were looking for?

best,
aaron.

> Let me know what the interfaces need to be set to. I have the
> configuration here  and can try it quite quickly.
> - R
>
> On 8/22/07, Rajesh Narayanan < nrajesh71 <at> gmail.com> wrote: I would
> be quite interested in this as well. Will test this scenario as
> soon as I can get my board (montejade-platform) to behave!
>
> Do you know what the dual mode is called?
>
> Thanks,
> Rajesh.
>
>
> On 8/22/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
> zeta,
>
> basically point 1 to remember is: olsr is more or less agnostic to
> what the lower levels are doing since it is level 3.
>
> That said, yes there are features in atheros based cards where you
> can have ad-hoc and managed mode at once in parallel on one card.
> However, I never tested that myself. Maybe somebody else can report
> on that.
>
> cheers,
> aaron.
>
>
> On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
>
> > Hi all -
> >
> > I am a new user experimenting with OLSR for laptop
> > internet connectivity.  After reading the
> > documentation, is it possible to have a laptop with a
> > WLAN card attach to both a 802.11 network in
> > infrastructure mode (to connect to the Internet), and
> > a MANET using OLSR?  Thus the laptop would be the
> > gateway between MANET devices and the Internet.  Here
> > is the catch: the laptop only has one WLAN interface;
> > there is not the option to connect to the internet via
> > ethernet.
> >
> > Assuming this is possible (perhaps a big assumption),
> > which is the best way?  Is there a way to do via HNA4
> > and INTERFACES in olsrd.conf?  Or should I be looking
> > at a different olsrd.conf option?
> >
> > A related question:  where is the SSID set?  Or in
> > this scenario, will the gateway laptop propigate the
> > SSID of the 801.11 AP?
> >
> > Thanks for any advice!
> >
> > Zeta
> >
> >
> >       ___________________________________________________________
> > Want ideas for reducing your carbon footprint? Visit Yahoo! For
> > Good   http://uk.promotions.yahoo.com/forgood/environment.html
> >
> > --
> > Olsr-users mailing list
> > Olsr-users <at> lists.olsr.org
> > http://lists.olsr.org/mailman/listinfo/olsr-users
> >
>
> ---
> there's no place like 127.0.0.1
> until we found ::1 -- which is even bigger
>
>
>
>
> --
> Olsr-users mailing list
> Olsr-users <at> lists.olsr.org
> http://lists.olsr.org/mailman/listinfo/olsr-users
>
>

---
C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research





--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Aaron Kaplan | 5 Sep 2007 09:02
Gravatar

Re: Dual Mode Operation: One WLAN interface for both 801.11 infrastructure & OLSR?


On Sep 5, 2007, at 12:52 PM, Rajesh Narayanan wrote:

> hi,
>
> Here are some notes from trying to mess with dual mode operation.
>
> Got the dual mode operation partly working.
> 1. ath0  in adhoc mode
> 2. ath1 in ap mode
>
> Note that the adhoc mode interface needs to be created before the  
> ap. If you do the other way around, the hardware does not allow you  
> to add it. (sorry im not geeky enough to figure that out :-(  ). I  
> just tried this on an intuition (and a couple of caffeine shots)  
> and it seemed to do the trick.
>
> I got OLSR running on the ath0 and seems to work ok. But still have  
> not figured the ap mode as yet on ath1. I do get some MAC layer  
> exchanges (arps) so I know the interfaces ARE ok. But face a bummer  
> on the IP layer.
>
>                          ath0       ath1
> RouterA  <----------> RouterB <--------------> Laptop1
>              192.168.50.X       192.168.60.X
>               OLSR
>       <--- pings ok --->        <---pings not ok -->
>                                       <-------- arps   ------>

subnetmasks are 255.255.255.0 ?
what does your routing table say on B, A and the laptop?

>
> Hope someone in the list can help.
>
> Thanks,
> Rajesh.
>
>
>
> On 9/2/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
> On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:
>
> > Not sure what the configuration is. But I dont think its likely to
> > work. Atheros supports multiple modes but I didnt see anything
> > related to a dual-mode operation.
> >
>
> Rajesh:
>
> As said, I did not try it out myself but try this:
> http://madwifi.org/wiki/ngFeatures
>
> Is that what you were looking for?
>
> best,
> aaron.
>
> > Let me know what the interfaces need to be set to. I have the
> > configuration here  and can try it quite quickly.
> > - R
> >
> > On 8/22/07, Rajesh Narayanan < nrajesh71 <at> gmail.com> wrote: I would
> > be quite interested in this as well. Will test this scenario as
> > soon as I can get my board (montejade-platform) to behave!
> >
> > Do you know what the dual mode is called?
> >
> > Thanks,
> > Rajesh.
> >
> >
> > On 8/22/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
> > zeta,
> >
> > basically point 1 to remember is: olsr is more or less agnostic to
> > what the lower levels are doing since it is level 3.
> >
> > That said, yes there are features in atheros based cards where you
> > can have ad-hoc and managed mode at once in parallel on one card.
> > However, I never tested that myself. Maybe somebody else can report
> > on that.
> >
> > cheers,
> > aaron.
> >
> >
> > On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
> >
> > > Hi all -
> > >
> > > I am a new user experimenting with OLSR for laptop
> > > internet connectivity.  After reading the
> > > documentation, is it possible to have a laptop with a
> > > WLAN card attach to both a 802.11 network in
> > > infrastructure mode (to connect to the Internet), and
> > > a MANET using OLSR?  Thus the laptop would be the
> > > gateway between MANET devices and the Internet.  Here
> > > is the catch: the laptop only has one WLAN interface;
> > > there is not the option to connect to the internet via
> > > ethernet.
> > >
> > > Assuming this is possible (perhaps a big assumption),
> > > which is the best way?  Is there a way to do via HNA4
> > > and INTERFACES in olsrd.conf?  Or should I be looking
> > > at a different olsrd.conf option?
> > >
> > > A related question:  where is the SSID set?  Or in
> > > this scenario, will the gateway laptop propigate the
> > > SSID of the 801.11 AP?
> > >
> > > Thanks for any advice!
> > >
> > > Zeta
> > >
> > >
> > >       ___________________________________________________________
> > > Want ideas for reducing your carbon footprint? Visit Yahoo! For
> > > Good   http://uk.promotions.yahoo.com/forgood/environment.html
> > >
> > > --
> > > Olsr-users mailing list
> > > Olsr-users <at> lists.olsr.org
> > > http://lists.olsr.org/mailman/listinfo/olsr-users
> > >
> >
> > ---
> > there's no place like 127.0.0.1
> > until we found ::1 -- which is even bigger
> >
> >
> >
> >
> > --
> > Olsr-users mailing list
> > Olsr-users <at> lists.olsr.org
> > http://lists.olsr.org/mailman/listinfo/olsr-users
> >
> >
>
> ---
> C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research
>
>
>
>
>

---
C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Sven-Ola Tuecke | 5 Sep 2007 09:25
Picon

Re: Dual Mode Operation: One WLAN interface for both 801.11 infrastructure & OLSR?

Hello,

fiddeling with the multi-bss feature of madwifi will cost you devel time and
you may need some kernel hacker skills too (especially ibss and ap
concurrently). If you don't know how to debug kernel drivers you will not
have much success I fear. Nothing you can blame olsrd for...

You may try nbd's patchset (on top of an upcoming newer hal version - maybe
avail in madwifi-0.9.4++ if they think it's stable). Which can be found in
the openwrt/kamikaze source repo. Kernel oopses and matching patchsets are
welcome there - or on madwifi bugtrack.

Tip: the init sequence (first ad-hoc then ap) is more a bug than a feature.
Check out the beacon handling on chip level - which is a bit dirty if you
dig in <ggg>

// Sven-Ola

Rajesh Narayanan wrote:

> hi,
> 
> Here are some notes from trying to mess with dual mode operation.
> 
> Got the dual mode operation partly working.
> 1. ath0  in adhoc mode
> 2. ath1 in ap mode
> 
> Note that the adhoc mode interface needs to be created before the ap. If
> you do the other way around, the hardware does not allow you to add it.
> (sorry
> im not geeky enough to figure that out :-(  ). I just tried this on an
> intuition (and a couple of caffeine shots) and it seemed to do the trick.
> 
> I got OLSR running on the ath0 and seems to work ok. But still have not
> figured the ap mode as yet on ath1. I do get some MAC layer exchanges
> (arps) so I know the interfaces ARE ok. But face a bummer on the IP layer.
> 
>                          ath0       ath1
> RouterA  <----------> RouterB <--------------> Laptop1
>              192.168.50.X       192.168.60.X
>               OLSR
>       <--- pings ok --->        <---pings not ok -->
>                                       <-------- arps   ------>
> 
> Hope someone in the list can help.
> 
> Thanks,
> Rajesh.
> 
> 
> 
> On 9/2/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
>>
>>
>> On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:
>>
>> > Not sure what the configuration is. But I dont think its likely to
>> > work. Atheros supports multiple modes but I didnt see anything
>> > related to a dual-mode operation.
>> >
>>
>> Rajesh:
>>
>> As said, I did not try it out myself but try this:
>> http://madwifi.org/wiki/ngFeatures
>>
>> Is that what you were looking for?
>>
>> best,
>> aaron.
>>
>> > Let me know what the interfaces need to be set to. I have the
>> > configuration here  and can try it quite quickly.
>> > - R
>> >
>> > On 8/22/07, Rajesh Narayanan <nrajesh71 <at> gmail.com> wrote: I would
>> > be quite interested in this as well. Will test this scenario as
>> > soon as I can get my board (montejade-platform) to behave!
>> >
>> > Do you know what the dual mode is called?
>> >
>> > Thanks,
>> > Rajesh.
>> >
>> >
>> > On 8/22/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
>> > zeta,
>> >
>> > basically point 1 to remember is: olsr is more or less agnostic to
>> > what the lower levels are doing since it is level 3.
>> >
>> > That said, yes there are features in atheros based cards where you
>> > can have ad-hoc and managed mode at once in parallel on one card.
>> > However, I never tested that myself. Maybe somebody else can report
>> > on that.
>> >
>> > cheers,
>> > aaron.
>> >
>> >
>> > On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
>> >
>> > > Hi all -
>> > >
>> > > I am a new user experimenting with OLSR for laptop
>> > > internet connectivity.  After reading the
>> > > documentation, is it possible to have a laptop with a
>> > > WLAN card attach to both a 802.11 network in
>> > > infrastructure mode (to connect to the Internet), and
>> > > a MANET using OLSR?  Thus the laptop would be the
>> > > gateway between MANET devices and the Internet.  Here
>> > > is the catch: the laptop only has one WLAN interface;
>> > > there is not the option to connect to the internet via
>> > > ethernet.
>> > >
>> > > Assuming this is possible (perhaps a big assumption),
>> > > which is the best way?  Is there a way to do via HNA4
>> > > and INTERFACES in olsrd.conf?  Or should I be looking
>> > > at a different olsrd.conf option?
>> > >
>> > > A related question:  where is the SSID set?  Or in
>> > > this scenario, will the gateway laptop propigate the
>> > > SSID of the 801.11 AP?
>> > >
>> > > Thanks for any advice!
>> > >
>> > > Zeta
>> > >
>> > >
>> > >       ___________________________________________________________
>> > > Want ideas for reducing your carbon footprint? Visit Yahoo! For
>> > > Good   http://uk.promotions.yahoo.com/forgood/environment.html
>> > >
>> > > --
>> > > Olsr-users mailing list
>> > > Olsr-users <at> lists.olsr.org
>> > > http://lists.olsr.org/mailman/listinfo/olsr-users
>> > >
>> >
>> > ---
>> > there's no place like 127.0.0.1
>> > until we found ::1 -- which is even bigger
>> >
>> >
>> >
>> >
>> > --
>> > Olsr-users mailing list
>> > Olsr-users <at> lists.olsr.org
>> > http://lists.olsr.org/mailman/listinfo/olsr-users
>> >
>> >
>>
>> ---
>> C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research
>>
>>
>>
>>
>>

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Rajesh Narayanan | 5 Sep 2007 11:39
Picon

Re: Dual Mode Operation: One WLAN interface for both 801.11 infrastructure & OLSR?

yes the subnet masks are 24 bit. i will put the route entries tomorrow.
- Rajesh

On 9/5/07, Aaron Kaplan <aaron <at> lo-res.org > wrote:

On Sep 5, 2007, at 12:52 PM, Rajesh Narayanan wrote:

> hi,
>
> Here are some notes from trying to mess with dual mode operation.
>
> Got the dual mode operation partly working.
> 1. ath0  in adhoc mode
> 2. ath1 in ap mode
>
> Note that the adhoc mode interface needs to be created before the
> ap. If you do the other way around, the hardware does not allow you
> to add it. (sorry im not geeky enough to figure that out :-(  ). I
> just tried this on an intuition (and a couple of caffeine shots)
> and it seemed to do the trick.
>
> I got OLSR running on the ath0 and seems to work ok. But still have
> not figured the ap mode as yet on ath1. I do get some MAC layer
> exchanges (arps) so I know the interfaces ARE ok. But face a bummer
> on the IP layer.
>
>                          ath0       ath1
> RouterA  <----------> RouterB <--------------> Laptop1
>              192.168.50.X       192.168.60.X
>               OLSR
>       <--- pings ok --->        <---pings not ok -->
>                                       <-------- arps   ------>

subnetmasks are 255.255.255.0 ?
what does your routing table say on B, A and the laptop?


>
> Hope someone in the list can help.
>
> Thanks,
> Rajesh.
>
>
>
> On 9/2/07, Aaron Kaplan < aaron <at> lo-res.org> wrote:
> On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:
>
> > Not sure what the configuration is. But I dont think its likely to
> > work. Atheros supports multiple modes but I didnt see anything
> > related to a dual-mode operation.
> >
>
> Rajesh:
>
> As said, I did not try it out myself but try this:
> http://madwifi.org/wiki/ngFeatures
>
> Is that what you were looking for?
>
> best,
> aaron.
>
> > Let me know what the interfaces need to be set to. I have the
> > configuration here  and can try it quite quickly.
> > - R
> >
> > On 8/22/07, Rajesh Narayanan < nrajesh71 <at> gmail.com> wrote: I would
> > be quite interested in this as well. Will test this scenario as
> > soon as I can get my board (montejade-platform) to behave!
> >
> > Do you know what the dual mode is called?
> >
> > Thanks,
> > Rajesh.
> >
> >
> > On 8/22/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
> > zeta,
> >
> > basically point 1 to remember is: olsr is more or less agnostic to
> > what the lower levels are doing since it is level 3.
> >
> > That said, yes there are features in atheros based cards where you
> > can have ad-hoc and managed mode at once in parallel on one card.
> > However, I never tested that myself. Maybe somebody else can report
> > on that.
> >
> > cheers,
> > aaron.
> >
> >
> > On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
> >
> > > Hi all -
> > >
> > > I am a new user experimenting with OLSR for laptop
> > > internet connectivity.  After reading the
> > > documentation, is it possible to have a laptop with a
> > > WLAN card attach to both a 802.11 network in
> > > infrastructure mode (to connect to the Internet), and
> > > a MANET using OLSR?  Thus the laptop would be the
> > > gateway between MANET devices and the Internet.  Here
> > > is the catch: the laptop only has one WLAN interface;
> > > there is not the option to connect to the internet via
> > > ethernet.
> > >
> > > Assuming this is possible (perhaps a big assumption),
> > > which is the best way?  Is there a way to do via HNA4
> > > and INTERFACES in olsrd.conf?  Or should I be looking
> > > at a different olsrd.conf option?
> > >
> > > A related question:  where is the SSID set?  Or in
> > > this scenario, will the gateway laptop propigate the
> > > SSID of the 801.11 AP?
> > >
> > > Thanks for any advice!
> > >
> > > Zeta
> > >
> > >
> > >       ___________________________________________________________
> > > Want ideas for reducing your carbon footprint? Visit Yahoo! For
> > > Good   http://uk.promotions.yahoo.com/forgood/environment.html
> > >
> > > --
> > > Olsr-users mailing list
> > > Olsr-users <at> lists.olsr.org
> > > http://lists.olsr.org/mailman/listinfo/olsr-users
> > >
> >
> > ---
> > there's no place like 127.0.0.1
> > until we found ::1 -- which is even bigger
> >
> >
> >
> >
> > --
> > Olsr-users mailing list
> > Olsr-users <at> lists.olsr.org
> > http://lists.olsr.org/mailman/listinfo/olsr-users
> >
> >
>
> ---
> C.O.S.H.E.R . - Completely Open Source Headers Engineering and Research
>
>
>
>
>

---
C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research





--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Rajesh Narayanan | 5 Sep 2007 11:46
Picon

Re: Dual Mode Operation: One WLAN interface for both 801.11 infrastructure & OLSR?

Definitely not comfy doing kernel debugging so not going to venture into it. Main intention was to look at some of the possibilities with multi-bss feature. definitely buggy but tons of potential.

Thanks for the Tip. I realized that ADHOC before AP was a bug and not a feature :).. also will look into the madwifi patches its not easy for me to add patches as i do not control the buildroot..

either way, ill post more observations/notes as i encounter them

Thanks,
rajesh.

On 9/5/07, Sven-Ola Tuecke < mail2news <at> commando.de> wrote:
Hello,

fiddeling with the multi-bss feature of madwifi will cost you devel time and
you may need some kernel hacker skills too (especially ibss and ap
concurrently). If you don't know how to debug kernel drivers you will not
have much success I fear. Nothing you can blame olsrd for...

You may try nbd's patchset (on top of an upcoming newer hal version - maybe
avail in madwifi-0.9.4++ if they think it's stable). Which can be found in
the openwrt/kamikaze source repo. Kernel oopses and matching patchsets are
welcome there - or on madwifi bugtrack.

Tip: the init sequence (first ad-hoc then ap) is more a bug than a feature.
Check out the beacon handling on chip level - which is a bit dirty if you
dig in <ggg>

// Sven-Ola

Rajesh Narayanan wrote:

> hi,
>
> Here are some notes from trying to mess with dual mode operation.
>
> Got the dual mode operation partly working.
> 1. ath0  in adhoc mode
> 2. ath1 in ap mode
>
> Note that the adhoc mode interface needs to be created before the ap. If
> you do the other way around, the hardware does not allow you to add it.
> (sorry
> im not geeky enough to figure that out :-(  ). I just tried this on an
> intuition (and a couple of caffeine shots) and it seemed to do the trick.
>
> I got OLSR running on the ath0 and seems to work ok. But still have not
> figured the ap mode as yet on ath1. I do get some MAC layer exchanges
> (arps) so I know the interfaces ARE ok. But face a bummer on the IP layer.
>
>                          ath0       ath1
> RouterA  <----------> RouterB <--------------> Laptop1
>               192.168.50.X       192.168.60.X
>               OLSR
>       <--- pings ok --->        <---pings not ok -->
>                                       <-------- arps   ------>
>
> Hope someone in the list can help.
>
> Thanks,
> Rajesh.
>
>
>
> On 9/2/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
>>
>>
>> On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:
>>
>> > Not sure what the configuration is. But I dont think its likely to
>> > work. Atheros supports multiple modes but I didnt see anything
>> > related to a dual-mode operation.
>> >
>>
>> Rajesh:
>>
>> As said, I did not try it out myself but try this:
>> http://madwifi.org/wiki/ngFeatures
>>
>> Is that what you were looking for?
>>
>> best,
>> aaron.
>>
>> > Let me know what the interfaces need to be set to. I have the
>> > configuration here  and can try it quite quickly.
>> > - R
>> >
>> > On 8/22/07, Rajesh Narayanan <nrajesh71 <at> gmail.com> wrote: I would
>> > be quite interested in this as well. Will test this scenario as
>> > soon as I can get my board (montejade-platform) to behave!
>> >
>> > Do you know what the dual mode is called?
>> >
>> > Thanks,
>> > Rajesh.
>> >
>> >
>> > On 8/22/07, Aaron Kaplan <aaron <at> lo-res.org> wrote:
>> > zeta,
>> >
>> > basically point 1 to remember is: olsr is more or less agnostic to
>> > what the lower levels are doing since it is level 3.
>> >
>> > That said, yes there are features in atheros based cards where you
>> > can have ad-hoc and managed mode at once in parallel on one card.
>> > However, I never tested that myself. Maybe somebody else can report
>> > on that.
>> >
>> > cheers,
>> > aaron.
>> >
>> >
>> > On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
>> >
>> > > Hi all -
>> > >
>> > > I am a new user experimenting with OLSR for laptop
>> > > internet connectivity.  After reading the
>> > > documentation, is it possible to have a laptop with a
>> > > WLAN card attach to both a 802.11 network in
>> > > infrastructure mode (to connect to the Internet), and
>> > > a MANET using OLSR?  Thus the laptop would be the
>> > > gateway between MANET devices and the Internet.  Here
>> > > is the catch: the laptop only has one WLAN interface;
>> > > there is not the option to connect to the internet via
>> > > ethernet.
>> > >
>> > > Assuming this is possible (perhaps a big assumption),
>> > > which is the best way?  Is there a way to do via HNA4
>> > > and INTERFACES in olsrd.conf?  Or should I be looking
>> > > at a different olsrd.conf option?
>> > >
>> > > A related question:  where is the SSID set?  Or in
>> > > this scenario, will the gateway laptop propigate the
>> > > SSID of the 801.11 AP?
>> > >
>> > > Thanks for any advice!
>> > >
>> > > Zeta
>> > >
>> > >
>> > >       ___________________________________________________________
>> > > Want ideas for reducing your carbon footprint? Visit Yahoo! For
>> > > Good   http://uk.promotions.yahoo.com/forgood/environment.html
>> > >
>> > > --
>> > > Olsr-users mailing list
>> > > Olsr-users <at> lists.olsr.org
>> > > http://lists.olsr.org/mailman/listinfo/olsr-users
>> > >
>> >
>> > ---
>> > there's no place like 127.0.0.1
>> > until we found ::1 -- which is even bigger
>> >
>> >
>> >
>> >
>> > --
>> > Olsr-users mailing list
>> > Olsr-users <at> lists.olsr.org
>> > http://lists.olsr.org/mailman/listinfo/olsr-users
>> >
>> >
>>
>> ---
>> C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research
>>
>>
>>
>>
>>


--
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Bernd Petrovitsch | 5 Sep 2007 18:41
Picon
Favicon

Re: [Olsr-dev] OLSRD RT refactoring

On Thu, 2007-08-23 at 13:23 +0200, Hannes Gredler wrote:
[...]
> attached a patch for refactoring the olsr routing table implementation.
> this is both a cleanup of duplicate routines, as well a clean
> reimplementation of the RIB.
[...]
> the overall CPU savings of this change are not dramatic (app. 10-15%
> for the entire route-calculation path) - however it provides the necessary
> infrastructure (particularly the separation between rt_entry and rt_path)
> for doing in place SPF calculations further down the road
> 
> asking for feedback and inclusion into CVS head.

Done as of now (-6 of course, together with Sven-Ola's fixes).

Everyone please test (especially on non-Linux systems) and report.
I'm considering a release in the next few days if nothing serious shows
up.

For external plugins: Some internal stuff has changed and may break the
build -
especially if the plugin's copy in olsrd-CVS also changed.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

John Zavgren | 12 Sep 2007 17:07

Re: help on MOLSR

Alberto, et al:

I was never able to get molsr to build. I think its dead-end code that was built for Solaris, but never fully ported to Linux. I finally gave up and switched over to the NRL SMF code. It can be obtained on the Naval Research Labs WWW site. It doesn't implement IGMP and it floods all multicast datagrams so that every interface in the network receives all of them, even when they don't need or want them.

There are several flooding algorithms that can be invoked that try to reduce the flooding traffic to a "dull roar" that leverage the OLSR flooding proxy functionality.

Please let me know if you get anywhere with the MOSLR code. I didn't. Perhpas I couldn't find the right person to help with this. It'd be nice to have IGMP and muticast spanning trees, etc.

Good Luck

On 9/12/07, alberto debarros <debarrosalberto <at> gmail.com> wrote:
 I am trying to build molsr on Linux. I have downloaded MOLSR code at http://hipercom.inria.fr/SMOLSR-MOLSR/downloads.html
 but this doesn't run
 Could oyu help me please?
 
Best regards
 
Alberto de Barros



--
John Zavgren
603-371-0513 (home)
603-801-2094 (cell)
john <at> zavgren.com
--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Gian Maria Giani | 12 Sep 2007 19:13
Picon
Favicon

route instability

 

We have some problems with a network running OLSR v.0.4.10, in that the routes are not very stable.

 

The problem seems strange. The main points are:

 

 

 

-          the network contains 10 nodes. They are in fixed positions. Each

node has about 3 neighbours, and the maximum distance between nodes is 3 hops.

 

-          the routes are not stable. If one observes the routing table of

one node in a given moment in time, and then observes it again after some seconds, many times the observed routes are different

 

-          this seems related to the fact that some neighbors are listed as

non-symmetric (they appear as symmetric for some moments, then appear as asymmetric, then again as symmetric)

 

-          the percentage of lost packets over these asymmetric links,

however, is 0% in both directions

 

 

 

We have already tried in many ways to solve the problem… in particular we have increased the validity time of hello messages up to 60 seconds, but the problem is still there. Any idea?

 

 

 

Thank you

 

Gian Maria Giani

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users
Kim Hawtin | 13 Sep 2007 06:33
Picon
Picon
Favicon

Re: route instability

Hi Gian,

Gian Maria Giani wrote:
> We have some problems with a network running OLSR v.0.4.10, in that the
> routes are not very stable.
> 
> The problem seems strange. The main points are:
> -          the network contains 10 nodes. They are in fixed positions.
> Each node has about 3 neighbours, and the maximum distance between nodes is 3
> hops.
> -          the routes are not stable. If one observes the routing table
> of one node in a given moment in time, and then observes it again after
> some seconds, many times the observed routes are different
> -          this seems related to the fact that some neighbors are listed
> as non-symmetric (they appear as symmetric for some moments, then appear as
> asymmetric, then again as symmetric)
> -          the percentage of lost packets over these asymmetric links,
> however, is 0% in both directions
> 
> We have already tried in many ways to solve the problem... in particular
> we have increased the validity time of hello messages up to 60 seconds,
> but the problem is still there. Any idea?

I recently did a demo for my local linux user group, and we noticed this
behaviour too.

So we had a look at the link quality (LC) settings. After enabling LC
the route map stability was significantly improved.

You can visualise the route map with dot-draw and the perl script from
here; http://wirelessafrica.meraka.org.za/wiki/index.php/OLSR_Dot_Draw

Info from the LinuxSA is demo here;
 http://www.air-stream.org.au/blog/adhoc/network-snapshots-linuxsa-meeting

Compare the second and third diagrams;
 the second did not use LC
 the third used LC=2

have fun,

Kim
-- 
Operating Systems, Services and Operations
Information Technology Services, The University of Adelaide
kim.hawtin <at> adelaide.edu.au

"I am not a finite state machine"

--

-- 
Olsr-users mailing list
Olsr-users <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-users

Bernd Petrovitsch | 14 Sep 2007 01:10
Picon
Favicon

olsrd-0.5.4rc1 released

Hi all!

I just released olsrd-0.5.4rc1. Due to the further massive changes (a
good part of it was rewritten) in the routing core to further reduce
duplicated data and *lots* of malloc() and free() calls (see the
changelog below for more), we ask for further testing and - thus - this
is a release candidate.
It compiles and runs on Linux and Win32 (though the testing on Win32 was
pretty minimal), so we are especially interested in feedback from all
non-Linux systems.
The only known issues are
- warnings on x86_64 in code only used by the nameservice plugin.
- the Quagga plugin is the last with the old plugin interface version.

A .tar.gz and a .tar.bz2 can be found on
http://bernd.petrovitsch.priv.at/olsr-ng/.

To quote from the changelog:
----  snip  ----
QUAGGA by Immo 'FaUl' Wehrenberg <immo.olsr <at> do.bundessicherheitsministerium.de>
- updated to svn version 33

BMF PLUGIN  by Erik Tromp <erik_tromp <at> hotmail.com>
- updated to 1.5.1
- updated to latest plugin interfaces changes and killed warnings (by Bernd
  Petrovitsch <bernd <at> firmix.at>)

PATCH by Hannes Gredler <hannes <at> gredler.at> which rewrites the route handling.
To quote him:
----  snip  ----
change list:
- get rid of separate routing tables for HNA and per-node routes, everything is
  now unified in an AVL routing tree (&routingtree)

- introduce walking macros (OLSR_FOR_ALL_RT_ENTRIES()) that hide the internal
  structure of the RIB for making life of the plugin authors easier.

- get rid of different SPF implementations for LQ and non-LQ code paths. a
  non-LQ edge is simply substituted with a cost of 1.0

- get rid of host masks - a new data type olsr_prefix is introduced which is
  basically an ip address plus a prefix length.

  do not install the metric in the kernel FIB - for the kernel its pointless
  if the route gets installed with a metric of N or M.

  we do not need to update the kernel FIB if we have hop count only changes
  (for example if there is a reroute action further downstream)

  the only things which triggers a kernel FIB route update is a next hop
  change (a next hop is neighboring gateway router plus an interface).

  all OLSR routes are installed with a metric of 2

- separate between rt_entry and rt_path - the former is a route installed in the
  kernel with an next hop. the latter is a candidate for best path selection
  after SPF calculation has been done. in the rt_entry we keep a pointer to the
  best_path and also to the next hop that was installed in the kernel FIB.

  we always keep all originator of a route, if a route originator goes away we
  can easy recompute the best path for the route.

  the next hop in the rt_entry gets only updated upon a successful route_add
  call - that way we always remember what next hop to delete.

  stray routes should be history now.

- tweak the linked list toolkit to operate on circular lists.

- get rid of malloc calls for building the kernel update list. the list node is
  now embedded in the rt_entry.

- introduce three queues (add/chg/del) for kernel updates.

- for neighbor route dependency tracking the neighbor routes are queued first or
  last (depending on which queue you work on)

- rework all the plugins which directly manipulate rt entries.

- rework the plugins that read from the routing table (most notably nameserver,
  httpinfo and quagga plugin)

- lots of comments that explains the intentions and purpose of this code-piece.

non RT related stuff:
- use a list rather than a tree for storing the post-SPF results, which further
  improves the raw-SPF runtime.

- add display of SPF runtime (masked behind #ifdef SPF_PROFILING)
----  snip  ----
And Sven-Ola Tuecke <mail2news <at> commando.de> fixed an instability issue on interface
up/down operations (see 102-olsrd-rt-refactoring-fixes.patch below).

PATCH by Hannes Gredler <hannes <at> gredler.at> which "consolidates
the link-state database and the spf-calculation in order
to calculate routes more efficiently".
To quote him (more):
----  snip  ----
- use the link-state (tc) database for SPF calculations rather than
  replicating the notion of vertices and edges for a SPF run.
  this heavily reduces malloc() calls and shrinks the total CPU
  load of the route calculation path between 60%-80%.
----  snip  ----

PATCHES by Sven-Ola Tücke <mail2news <at> commando.de> to be found on from
http://download-master.berlin.freifunk.net/sven-ola/nylon/packages/olsrd/files/
- 102-olsrd-rt-refactoring-fixes.patch
  Because you changed a lot of basics: It's time to handle a general
  flaw in the routing system. Plase take a look at chk_if_changed(). This
  will free() any "struct interface" pointer without warning at any time.
  This is why it's possile to SEGV olsrd with a simple "ifdown xxx". 
  The patch replaces the (maybe) invalid pointer with an index reference
  "iif_index". You can always ask the OS for a name. Please note, that I do
  not have a working BSD toolchain, so I've placed an #error in the IPv6
  BSD-part where the author/porter has started to hack something funny.

- 110-olsrd-double-wlancard-neigh-hack.patch:
  This is a hack for Nodes having to wifi cards with the same channel,
  bssid, IP-Range etc. If two nodes can see each other by means of two
  possible links (here: two wifi cards with equal config), a bug is  triggered
  with the Neigh-is-SYM detections. This small little hack prevents this.

- 112-olsrd-nameservice-fixemptyname.patch:
  This is an addon to my lat/lon stuff which will prevent olsrd from
  running (oops?) if no hostname is given and the nameservice plugin
  is loaded.

- 113-olsrd-dyngwplain-pluginvers5.patch:
  This updates the dyngwplain plugin to the new Plugin Iface

- 140-olsrd-arprefreshed.patch:
  This is a new one. Opens a packet socket and listen to UDP(698), extract
  the sender MAC and refreshes the ARP cache whith that. Should speedup
  especially in cases, if you initially try to use a longer routing path which
  normally triggers a "ARP-Lookup-Chain".
- 106-olsrd-nameserviceparams.patch:
  This patch converts more plugins to the new interface version.
- 104-olsrd-policy-routing.patch
  Reworked this one to discard GPL helper functions. Also checked IPv6 and
  re-included the IPC hookup. The patch adds a "RtTable [number]" for
  /etc/olsrd.conf which is simply the Linux
  policy routing table to use. Defaults to 254 (== main). 
  This patch was modified/clenaed up by <bernd <at> firmix.at> to use "#if"
  instead of "#ifdef" as it's more robust against typos.

PATCH by Arnd Hannemann <hannemann <at> i4.informatik.rwth-aachen.de>
olsr_makefile_make_use_of_exename.patch
- This patch makes sure that the EXENAME variable of Makefile.inc is used
  in Makefile.

PATCHES by John Hay <jhay <at> meraka.org.za>
- update to new FreeBSD WLAN API
- do not require /bin/bash, use /bin/sh

PATCHES and CLEANUPS by Bernd Petrovitsch <bernd <at> firmix.at>
- Made a function from the ME_TO_DOUBLE() macro (in src/mantissa.h).
  This saves code throughout the code even on i386 and will even more
  on architectures without floating point units and "-msoft-float".
- And the mathemathics in src/mantissa.h is reformulated to minimize
  floating point operations to save CPU power - especially on embedded
  devices.
- I rewrote the half of src/lq_packet.[ch] which deals with incoming
  packets. This was triggered with performance output of gcc produced
  by Sven-Ola Tuecke at CCCamp07.
  This kills *lots* of (more than) superflous malloc()s and the same
  number of (free()s). And it also kills some code and copying around of
  data.

- converted the dyn_gw plugin to plugin interface version 5 (which leaves
  the quagga plugion as the last with the old one).
- paving the way to activate -Wshadow, much more to do
- const-ify parameters here and there
- use NULL for pointers (and not "0")
- Killed "extern" declarations in (not generated) .c files

- Based on a patch by Gianni Costanzi <gianni.costanzi <at> gmail.com> (so credits
  and thanks have to go there):
  added OS_CFLAG_PTHREAD Makefile variable since gcc (on Linux) requests this
  in the manual page.
  Changes/additions:
  - I added definitions to all OS-specific Makefile.$OS with the value similar
    to the value in OS_LIB_PTHREAD (either empty or "-pthread").
  - The variable is added to CPPFLAGS (and not CFLAGS) since CPPFLAGS is used
    for all cpp and gcc calls (and gcc's man page indicates that it sets
    variables for both of them).
----  snip  ----
Have fun!

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

--

-- 
Olsr-announce mailing list
Olsr-announce <at> lists.olsr.org
http://lists.olsr.org/mailman/listinfo/olsr-announce

Gmane