public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Freifunk Dresden <freifunk@ddmesh.de>
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.] no gateway / tun interface / default route
Date: Sun, 21 Oct 2007 21:41:35 +0200	[thread overview]
Message-ID: <471BAB6F.4000408@ddmesh.de> (raw)
In-Reply-To: <200710212007.56679.axel@open-mesh.net>

Hi,

> If you NAT any forwarded traffic, the source address of related packets is 
> changed :-) Batmand supports asymmetric routing. That means the packets may 
> be routed another way back than they have come. By doing NAT on the forwarded 
> traffic within the mesh you may force packets to also pass along the NATting 
> interface on their way back. But thats not very beautiful. And I am not shure 
> about further side effects. 
Hmm... I'm still confused. For instance I have interface bbs with ip 172.0.0.1
and an interface wlan with ip 10.0.0.1
If I ping a node behind the bbs interface the package will be created with
ip 172.0.0.1. The SNAT of the initiating node will change this to 10.0.0.1.
The next node will receive this package through its bbs interface but sends the
answer back to tho the node with ip 10.0.0.1. The outgoing interface
is determind by the routing table of the second node. This means that
asymetric routing is still possible. Because the routing entries that batman
creates in the second node the package goes over bbs or wlan back to the first
node.
But I see the point that batman internals may be disturbed when I change this
source ip for batman packets. See next comment.

>> They  
>> only go OUT or come IN. because batmand does not use the iptable roles
>> it does not know about the change of the source address.
>> The OGMs are generated for the original interface ip. OGMs that A sends to
>> B will be received via WLAN and also via BBS. When I understand batmand
>> right it uses the interface where the OGMs are comming from 
> (then batman would have to trac the MAC addresses, but it is IP based )
>> to calulate the  routes (not the source ip).
> NO! Batman uses the source IP of each received OGM to identify if the OGM has 
> been received 
> - directly from the originator interface or 
> - from another intermediate interface. 
> This is important for many internal mechanisms. 
If I mark the batman udp packets for the port (4305) and only SNAT all other packages
then batman should be working as designed, isn't it?

You said before that OGMs are not forwarded. So I can setup a firewall rule to avoid
forwarding the port 4305. The ports 4306 and 4307 still must be forwarded. Is this right?

Bye Stephan


  reply	other threads:[~2007-10-21 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 20:14 [B.A.T.M.A.N.] no gateway / tun interface / default route Freifunk Dresden
2007-10-18 23:35 ` Axel Neumann
2007-10-19 10:32   ` Axel Neumann
2007-10-19 10:51   ` Marek Lindner
2007-10-19 17:17     ` Freifunk Dresden
2007-10-19 17:52       ` Marek Lindner
2007-10-19 19:10         ` Freifunk Dresden
2007-10-20 11:00       ` Axel Neumann
2007-10-21 17:35         ` Freifunk Dresden
2007-10-21 18:07           ` Axel Neumann
2007-10-21 19:41             ` Freifunk Dresden [this message]
2007-10-22 12:58               ` Axel Neumann
2007-10-25 10:33                 ` Freifunk Dresden
2007-10-25 11:13                   ` Axel Neumann

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=471BAB6F.4000408@ddmesh.de \
    --to=freifunk@ddmesh.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox