[Olsr-dev] Propagating a default gateway OLSRv2

[Henning Rogge]

On Wed, Jul 20, 2016 at 3:20 AM, Peter Emanuel <(spam-protected)>
wrote:

> Hi Henning,
>
>
>
> I see what you mean about the there being a default route towards eth0
> anyways. It does exist and points right at the physical router to which
> eth0 is attached which should be the NAT that you refer to. I guess on
> Android, where there is no eth0 but you might want to set up the cell
> device as a NAT, then the iptables should be necessary. I need to spend
> more time to figure out why nslookup wasn’t working without the iptables on
> the Raspberry PI. I will report back, hopefully with good information, when
> I have figure something meaningful out. Thanks for the insights.
>
>
>
> Yes your understanding is correct “ If I understand you correctly you can
> ping 192.168.18.2 from your Android device right? “. What I don’t
> understand is the DUP and flakiness with the ping.
>

Hmm... Dups. That sounds like multiple nodes answering the same address.

Either an IP address conflict (or worse, a MAC address one) or something
really strange.

>
>
> Peter E.
>
>
>
> *From:* Henning Rogge [mailto:(spam-protected)]
> *Sent:* Monday, July 18, 2016 10:43 PM
> *To:* Peter Emanuel
> *Cc:* olsr-dev
> *Subject:* Re: [Olsr-dev] Propagating a default gateway OLSRv2
>
>
>
> On Mon, Jul 18, 2016 at 7:00 PM, Peter Emanuel <(spam-protected)>
> wrote:
>
> Because using iptables was the only way I could make it work with HNA in
> Version 1. I will run another test today to see if it works without it. Why
> is it dangerous in your estimation? All I am doing is using eth0 as a NAT
> to the mesh network. Will this conflict with the olsr routing?
>
>
>
> I admit I am no specialist for NAT scenarios, but wouldn't a normal static
> routing entry combined with the NAT iptables rule be the normal way?
>
>
>
> There should be the default route towards eth0 on the gateway anyways.
>
>
>
> (continued below)
>
>
>
>
>
> *From:* Henning Rogge [mailto:(spam-protected)]
> *Sent:* Monday, July 18, 2016 5:33 AM
>
>
> *To:* Peter Emanuel
> *Cc:* olsr-dev
> *Subject:* Re: [Olsr-dev] Propagating a default gateway OLSRv2
>
>
>
> Hmm?
>
>
>
> You are using IPtables to forward traffic between eth0 and wlan0?
>
>
>
> That sounds dangerous at best. Why do you do this?
>
>
>
> Henning
>
>
>
> On Fri, Jul 15, 2016 at 10:47 PM, Peter Emanuel <(spam-protected)>
> wrote:
>
> I have an update on this. I stumbled into a prior discussion on this forum
> from 2012 about this exact problem. The solution was to change the netmask
> on the WiFi from 255.255.255.0 to 255.255.0.0. This definitely helped as
> there were default gateways specified in each of the nodes in the chain
> pointing at each connected/edge node. (I personally don't understand why
> this changed anything as all of my nodes were on the same subnet -
> 192.168.18.x. This is probably my own lack of understanding).
>
>
>
> My gateway to the Internet was node 192.168.18.2. I was able to ping this
> IP from the last node in my chain of my 6 nodes (192.168.18.201) but
> couldn't get to the Internet although the DNS lookup appeared to work fine.
> I tried accessing youtube.com and google.com. Again, once my edge node
> was 1 hop from the gateway, everything started working as expected
> (192.168.18.201 connected to 192.168.18.3).
>
>
>
>
>
> If I understand you correctly you can ping 192.168.18.2 from your Android
> device right?
>
>
>
> Henning
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20160720/00bdfa59/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6851 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20160720/00bdfa59/attachment.png>