[Olsr-users] Help in mesh configuration

[Markus Kittenberger]

thats why i already wrote to John in my last mail: u might need nat (on devB
for traffic leaving towards the gateway) (-;

or static routes from the gateway back to all ipranges used in the mesh

(but honestly what he really needs is a "network adminstrator")

Markus

On Wed, Aug 17, 2011 at 2:52 PM, Michel Blais <(spam-protected)>wrote:

> **
> We have exchange some mail outside of olsr-user mailling list since
> everything was looking fine for olsr and I think that it a static route
> problem. Is gateway is 192.168.1.1/24 and is olsr mesh in the
> 192.168.3.0/24 subnet. He can ping the IP address of Dev B in the
> 192.168.1.0/24 subnet but not is gateway. I think is gateway just don't
> have any route for subnet 192.168.3.0/24 pointing at Dev B 192.168.1.168
> IP address.
>
> Michel
>
> Le 2011-08-17 03:23, Markus Kittenberger a écrit :
>
>
>
> On Wed, Aug 17, 2011 at 12:28 AM, John Tobias <(spam-protected)>wrote:
>
>> Hi Guys,
>>
>> I ping google.com using its IP address (74.125.224.50). Unfortunately, I
>> am still no luck.
>> # ping 74.125.224.50 returning "ping: sendto: Network is unreachable"
>>
>
>  Network unreachable is strange,..
>
>  hmm txtinfo reported a defaultroute already some mails ago:
>
>  > Table: Routes
>  > Destination     Gateway IP      Metric  ETX     Interface
>  > 0.0.0.0/0       192.168.3.4     1       1.066   wlan0
>
>  if this is still true, network unreachable should not happen, worst case
> would be no ping replies, as u likely need NAT on devB.
>
>  check with ip route, which default routes (0.0.0.0/0) u actually have on
> devB.
>
>  Markus
>
>
>> Here's the tcpdump:
>>
> which shows nothing but oslrd messages *G
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20110817/099ce71a/attachment.html>