Re: [B.A.T.M.A.N.] Unable to connect to internet

Sven Eckelmann
2009-03-16T22:54:21Z

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]

On Wednesday 11 March 2009 21:57:34 marco tozzini wrote:
[...]
> As you can see from node 200 I can ping node 203 (wireless interface
> 192.168.2.203 and wired interface 192.168.0.203), but I'm unable to go
> through adsl modem (192.168.0.1)
> But I can connect to adsl modem from node 203
Solution was found today on irc. Marco hadn't setup a NAT on the gateway node
as described in paragraph 4.2 " Why I can’t connect to the Internet after
setting the default gateway?" in
http://downloads.open-mesh.net/batman/misc/batmand_howto.pdf

A different solution was suggested by Simon to set the route to 192.168.2.x
nodes on 192.168.0.x nodes over the gateway node. This way the 192.168.0.x can
send answer packets to 192.168.2.x when it receives packets from 192.168.2.x
nodes without a NAT between the networks. 192.168.2.x could send to
192.168.0.x because the batman gateway node announced it to batman gateway
clients, but packets in the other direction never found their way because the
batman gateway doesn't announce a backward route to the 192.168.2.x nodes
outside the mesh. This wasn't due to a fault of batmand, but a
misunderstanding what the -a option does and what batmand cannot do (set
routing informations on nodes outside the mesh).

Regards,
Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]