All of lore.kernel.org
 help / color / mirror / Atom feed
From: marco tozzini <lists@java-system.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Unable to connect to internet
Date: Sat, 14 Mar 2009 09:52:40 +0100	[thread overview]
Message-ID: <49BB7058.2070100@java-system.com> (raw)
In-Reply-To: <200903112214.44339.onelektra@gmx.net>

elektra wrote:
> Hi .
>
>   
>> Any Hints?
>>     
>
> sure: You are not announcing a default route.
>
> On mesh router connected to ADSL:
>
> batmand -g 1000 ath0
>
> On other mesh router:
>
> batmand -r 1 ath0
>
> You have to NAT towards the internet on the gateway.
>
> Cheers,
> elektra 
>   

After this hint I have
node 203 = batman node not connect to internet
node 200 = batman node gateway connect to wired lan and internet

 >From the batman node client 203 (not connected to internet)
root@OpenWrt:~# ping -c 2 192.168.2.200 (= ath0)
PING 192.168.2.200 (192.168.2.200): 56 data bytes
64 bytes from 192.168.2.200: seq=0 ttl=64 time=3.330 ms
64 bytes from 192.168.2.200: seq=1 ttl=64 time=2.902 ms
--- 192.168.2.200 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.902/3.116/3.330 ms

root@OpenWrt:~# ping -c 2 192.168.0.200 (= br-lan)
PING 192.168.0.200 (192.168.0.200): 56 data bytes
64 bytes from 192.168.0.200: seq=0 ttl=64 time=4.780 ms
64 bytes from 192.168.0.200: seq=1 ttl=64 time=2.944 ms
--- 192.168.0.200 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.944/3.862/4.780 ms

root@OpenWrt:~# ping -c 2 192.168.0.1 (= router ADSL)
PING 192.168.0.1 (192.168.0.1): 56 data bytes
--- 192.168.0.1 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

root@OpenWrt:~# ping -c 2 192.168.0.80 (= other openwrt station 
connected through lan cable)
PING 192.168.0.80 (192.168.0.80): 56 data bytes
--- 192.168.0.80 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss


further; from GATEWAY batman node 200 (connected to wired lan and internet)
I can ping everything

So this means:

 From the CLIENT batman node 203 (not connected to wired lan and internet)
I can ping wireless interface of the batman node connected to wired lan
I can ping br-lan wired interface of the batman node connected to wired 
lan (so I think routing exist)
I CAN'T ping other nodes seen by br-lan wired interface of the batman 
node connected to wired lan

I suspect the problem could be elsewhere batman, isn't it?

thanks
Marco



  parent reply	other threads:[~2009-03-14  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 20:57 [B.A.T.M.A.N.] Unable to connect to internet marco tozzini
2009-03-11 21:14 ` elektra
2009-03-12 21:40   ` marco tozzini
2009-03-13  2:11     ` Marek Lindner
2009-03-14  8:13       ` marco tozzini
2009-03-14 11:01         ` Marek Lindner
2009-03-14  8:04     ` marco tozzini
2009-03-14  8:52   ` marco tozzini [this message]
2009-03-14  9:14     ` elektra
2009-03-16 22:54 ` Sven Eckelmann
  -- strict thread matches above, loose matches on Subject: below --
2009-03-17  9:39 Marco Tozzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49BB7058.2070100@java-system.com \
    --to=lists@java-system.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.