[Olsr-users] trouble with NAT and smart gateway

[Arjun]

Markus,
The three nodes in the mesh are as follows:

Node A:
Intel Centrino Ultimate-N 6300 wireless chipset on PCI-Express.
Ubuntu 10.10, kernel 2.6.35.
driver:
iwlagn, iwlcore (Intel wifi driver)

Node B:
Atheros AR9285 wireless adapter on PCI-Express
Ubuntu 10.04, kernel 2.6.32.
driver:
ath9k atheros driver

Node C (embedded computer)
Marvell 88W8686 wifi chip on SDIO.
Ubuntu 10.04, kernel 2.6.39.
driver:
libertas

Can you suggest a good Wifi USB adapter that is known to work well with
olsrd and Linux. I think I'll buy three of those Wifi chips and run olsr on
them. It might be better than running olsr on these different chipsets that
I use now.

Thanks much!
Arjun.


On Tue, Feb 14, 2012 at 1:58 AM, Markus Kittenberger <
(spam-protected)> wrote:

>
>
> On Tue, Feb 14, 2012 at 12:49 AM, Arjun <(spam-protected)> wrote:
>
>> Markus,
>> I am trying to get the setup to work with just 3 mesh nodes for now. The
>> node that runs the application to control the toy has a good wifi chipset.
>>
> based on wifi specs like bad, fast, good and decent, i really can't say
> anything,..
>
> either u tell us chipset and driver (and, especially if its a slow
> one, cpu-type and speed of the router) or leave it,..
>
> also how many pps/kpbs your application needs/peaks.
>
> furthermore even if u have the best wifi&driver in the node in the middle,
> bandwith manageable over 2 hops is still less than 1/2 of one hop
>
> (except if the node in the middle has 2 wifis on different channels)
>
>> The Toy itself has a decent wifi chipset. So I am planning to get a fast
>> wifi chipset only for the intermediate mesh node. Is it necessary for all
>> the mesh nodes to use the same wifi chipset for this to work?
>>
> no
>
> but usually it works best,.. (-;
>
> All my mesh nodes now use different wifi chipsets although I make sure
>> that their cell no. and channel is the same.
>>
> (which u have to do anyways,..)
>
>> Thanks!
>> Arjun.
>>
>>
>> On Mon, Feb 13, 2012 at 5:27 PM, Markus Kittenberger <
>> (spam-protected)> wrote:
>>
>>> hmm if u replace only one wifi, this might change quite nothing
>>> (as it cant use higher bitrates if the others arent compatible to this
>>> bitrates)
>>>
>>> Markus
>>>
>>>
>>> On Mon, Feb 13, 2012 at 10:54 PM, Arjun <(spam-protected)> wrote:
>>>
>>>> Markus and Henning,
>>>> I bought a faster wifi usb adapter to replace the wifi interface on my
>>>> intermediate mesh node. I am also trying to lower the bandwidth usage of my
>>>> application running in the mesh. I am hoping this will improve things. I
>>>> will keep you guys posted.
>>>> Thanks a lot!
>>>> Arjun.
>>>>
>>>>
>>>> On Sun, Feb 12, 2012 at 2:22 PM, Markus Kittenberger <
>>>> (spam-protected)> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Sun, Feb 12, 2012 at 7:14 PM, Arjun <(spam-protected)> wrote:
>>>>>
>>>>>> Hi Markus,
>>>>>> Yes, In the case when A is two hops away, I can still ping toy D from
>>>>>> B, C and A. But the bandwidth becomes so low and "I think" the TC/Hello
>>>>>> packets also get dropped along with the traffic from my application. So,
>>>>>> when A is two hops away and I run my application, I notice that the ETX
>>>>>> value (from txtinfo) to node C quickly becomes very high and goes to
>>>>>> Infinity. When I stop my application, the ETX value comes back down again.
>>>>>>
>>>>> i think, you have found the reason,..
>>>>>
>>>>> sounds like your wifi links (esepcially if they have to repeat on node
>>>>> B) are simply too slow for (the bandwidth needed) by your application.
>>>>>
>>>>> and as you likely do not protect olsrd packets with QOS rules, they
>>>>> suffer from heavy packetloss aswell, and so the complete mesh breaks apart
>>>>> too (due to infinite costs)
>>>>>
>>>>> anyways you have to improve the throughput of your links, or reduce
>>>>> the traffic,..
>>>>>
>>>>> Markus
>>>>>
>>>>> -Arjun.
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 12, 2012 at 11:49 AM, Markus Kittenberger <
>>>>>> (spam-protected)> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 12, 2012 at 3:48 PM, Arjun <(spam-protected)> wrote:
>>>>>>>
>>>>>>>> Hi Henning,
>>>>>>>> Node C is the default gateway to toy D. I have not set any routes
>>>>>>>> by hand from C to D, although one interface of C is on the same subnet as
>>>>>>>> the toy D. The other interface on C is on the same subnet as the mesh. I
>>>>>>>> have noticed that when olsrd is not running on C, I cannot ping toy D from
>>>>>>>> the mesh, although I can ping the mesh interface of C.
>>>>>>>>
>>>>>>> (only if u are one hop away from C,..)
>>>>>>>
>>>>>>>> However, when I run olsrd on C, with the HNA4 setting, I can ping
>>>>>>>> toy D from the mesh. I can also run my full application from node A, when C
>>>>>>>> has the iptables NAT rule and is only one hop away from node C in the mesh.
>>>>>>>> The same setting does not work when node A is two hops away from node C,
>>>>>>>> i.e. node B is between A and C in the mesh.
>>>>>>>>
>>>>>>> and in this case, can B or C reach D?
>>>>>>>
>>>>>>>> Thanks again!
>>>>>>>> Arjun.
>>>>>>>>
>>>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20120214/a7379aeb/attachment.html>