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.<br><br>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..
<br><br>either way, ill post more observations/notes as i encounter them<br><br>Thanks,<br>rajesh.<br><br><div><span class="gmail_quote">On 9/5/07, <b class="gmail_sendername">Sven-Ola Tuecke</b> <<a href="mailto:mail2news@commando.de">
mail2news@commando.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br><br>fiddeling with the multi-bss feature of madwifi will cost you devel time and
<br>you may need some kernel hacker skills too (especially ibss and ap<br>concurrently). If you don't know how to debug kernel drivers you will not<br>have much success I fear. Nothing you can blame olsrd for...<br><br>
You may try nbd's patchset (on top of an upcoming newer hal version - maybe<br>avail in madwifi-0.9.4++ if they think it's stable). Which can be found in<br>the openwrt/kamikaze source repo. Kernel oopses and matching patchsets are
<br>welcome there - or on madwifi bugtrack.<br><br>Tip: the init sequence (first ad-hoc then ap) is more a bug than a feature.<br>Check out the beacon handling on chip level - which is a bit dirty if you<br>dig in <ggg>
<br><br>// Sven-Ola<br><br>Rajesh Narayanan wrote:<br><br>> hi,<br>><br>> Here are some notes from trying to mess with dual mode operation.<br>><br>> Got the dual mode operation partly working.<br>> 1. ath0 in adhoc mode
<br>> 2. ath1 in ap mode<br>><br>> Note that the adhoc mode interface needs to be created before the ap. If<br>> you do the other way around, the hardware does not allow you to add it.<br>> (sorry<br>> im not geeky enough to figure that out :-( ). I just tried this on an
<br>> intuition (and a couple of caffeine shots) and it seemed to do the trick.<br>><br>> I got OLSR running on the ath0 and seems to work ok. But still have not<br>> figured the ap mode as yet on ath1. I do get some MAC layer exchanges
<br>> (arps) so I know the interfaces ARE ok. But face a bummer on the IP layer.<br>><br>> ath0 ath1<br>> RouterA <----------> RouterB <--------------> Laptop1<br>>
192.168.50.X 192.168.60.X<br>> OLSR<br>> <--- pings ok ---> <---pings not ok --><br>> <-------- arps ------><br>><br>> Hope someone in the list can help.
<br>><br>> Thanks,<br>> Rajesh.<br>><br>><br>><br>> On 9/2/07, Aaron Kaplan <<a href="mailto:aaron@lo-res.org">aaron@lo-res.org</a>> wrote:<br>>><br>>><br>>> On Aug 31, 2007, at 2:11 AM, Rajesh Narayanan wrote:
<br>>><br>>> > Not sure what the configuration is. But I dont think its likely to<br>>> > work. Atheros supports multiple modes but I didnt see anything<br>>> > related to a dual-mode operation.
<br>>> ><br>>><br>>> Rajesh:<br>>><br>>> As said, I did not try it out myself but try this:<br>>> <a href="http://madwifi.org/wiki/ngFeatures">http://madwifi.org/wiki/ngFeatures</a><br>
>><br>>> Is that what you were looking for?<br>>><br>>> best,<br>>> aaron.<br>>><br>>> > Let me know what the interfaces need to be set to. I have the<br>>> > configuration here and can try it quite quickly.
<br>>> > - R<br>>> ><br>>> > On 8/22/07, Rajesh Narayanan <<a href="mailto:nrajesh71@gmail.com">nrajesh71@gmail.com</a>> wrote: I would<br>>> > be quite interested in this as well. Will test this scenario as
<br>>> > soon as I can get my board (montejade-platform) to behave!<br>>> ><br>>> > Do you know what the dual mode is called?<br>>> ><br>>> > Thanks,<br>>> > Rajesh.<br>
>> ><br>>> ><br>>> > On 8/22/07, Aaron Kaplan <<a href="mailto:aaron@lo-res.org">aaron@lo-res.org</a>> wrote:<br>>> > zeta,<br>>> ><br>>> > basically point 1 to remember is: olsr is more or less agnostic to
<br>>> > what the lower levels are doing since it is level 3.<br>>> ><br>>> > That said, yes there are features in atheros based cards where you<br>>> > can have ad-hoc and managed mode at once in parallel on one card.
<br>>> > However, I never tested that myself. Maybe somebody else can report<br>>> > on that.<br>>> ><br>>> > cheers,<br>>> > aaron.<br>>> ><br>>> ><br>>> > On Aug 22, 2007, at 4:49 PM, zeta zappa wrote:
<br>>> ><br>>> > > Hi all -<br>>> > ><br>>> > > I am a new user experimenting with OLSR for laptop<br>>> > > internet connectivity. After reading the<br>>> > > documentation, is it possible to have a laptop with a
<br>>> > > WLAN card attach to both a 802.11 network in<br>>> > > infrastructure mode (to connect to the Internet), and<br>>> > > a MANET using OLSR? Thus the laptop would be the<br>>> > > gateway between MANET devices and the Internet. Here
<br>>> > > is the catch: the laptop only has one WLAN interface;<br>>> > > there is not the option to connect to the internet via<br>>> > > ethernet.<br>>> > ><br>>> > > Assuming this is possible (perhaps a big assumption),
<br>>> > > which is the best way? Is there a way to do via HNA4<br>>> > > and INTERFACES in olsrd.conf? Or should I be looking<br>>> > > at a different olsrd.conf option?<br>>> > >
<br>>> > > A related question: where is the SSID set? Or in<br>>> > > this scenario, will the gateway laptop propigate the<br>>> > > SSID of the 801.11 AP?<br>>> > ><br>>> > > Thanks for any advice!
<br>>> > ><br>>> > > Zeta<br>>> > ><br>>> > ><br>>> > > ___________________________________________________________<br>>> > > Want ideas for reducing your carbon footprint? Visit Yahoo! For
<br>>> > > Good <a href="http://uk.promotions.yahoo.com/forgood/environment.html">http://uk.promotions.yahoo.com/forgood/environment.html</a><br>>> > ><br>>> > > --<br>>> > > Olsr-users mailing list
<br>>> > > <a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>>> > > <a href="http://lists.olsr.org/mailman/listinfo/olsr-users">http://lists.olsr.org/mailman/listinfo/olsr-users
</a><br>>> > ><br>>> ><br>>> > ---<br>>> > there's no place like <a href="http://127.0.0.1">127.0.0.1</a><br>>> > until we found ::1 -- which is even bigger<br>>> >
<br>>> ><br>>> ><br>>> ><br>>> > --<br>>> > Olsr-users mailing list<br>>> > <a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br>>> > <a href="http://lists.olsr.org/mailman/listinfo/olsr-users">
http://lists.olsr.org/mailman/listinfo/olsr-users</a><br>>> ><br>>> ><br>>><br>>> ---<br>>> C.O.S.H.E.R. - Completely Open Source Headers Engineering and Research<br>>><br>>>
<br>>><br>>><br>>><br><br><br>--<br>Olsr-users mailing list<br><a href="mailto:Olsr-users@lists.olsr.org">Olsr-users@lists.olsr.org</a><br><a href="http://lists.olsr.org/mailman/listinfo/olsr-users">http://lists.olsr.org/mailman/listinfo/olsr-users
</a><br></blockquote></div><br>