All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Steen <ks@kevinsteen.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Connecting through Batman advanced interface
Date: Sun, 06 Feb 2011 22:18:25 +0000	[thread overview]
Message-ID: <4D4F1E31.4040200@kevinsteen.net> (raw)
In-Reply-To: <201102041638.54751.clemens-john@gmx.de>

On 04/02/11 15:38, Clemens John wrote:
> Am Dienstag 01 Februar 2011, 11:51:16 schrieben Sie:
>> If your non-batman clients don't need incoming connections, you could
>> NAT outgoing connections :
>>     [client]-->[adhoc ath1]-->NAT-->[br-mesh]
>> You would have to run a DHCP server on the ath1 interface to give those
>> clients a private IP and tell them to use the private IP on ath1 as
>> their router.
> What do I have do insert into iptables to NAT ath1 to br-mesh? I´m a complete
> firewall noob.
There might be an easier way using the config files of the distribution 
you're using, but from a script it would look something like this:

#! /bin/sh
modprobe iptable_nat
## Work-around for bad ISPs which drop ICMP Fragmentation Needed 
packets: (Needs to be early in list)
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS 
--clamp-mss-to-pmtu
iptables -t nat -A POSTROUTING -o br-mesh -j MASQUERADE

-Kevin


  reply	other threads:[~2011-02-06 22:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 22:46 [B.A.T.M.A.N.] Connecting through Batman advanced interface Clemens John
2011-01-29 17:45 ` Bjoern Franke
2011-01-29 18:00   ` Marek Lindner
2011-01-31 18:32     ` Clemens John
2011-02-01  5:49       ` wayne
2011-02-01 10:51       ` Kevin Steen
2011-02-04 15:38         ` Clemens John
2011-02-06 22:18           ` Kevin Steen [this message]
2011-02-08 23:37             ` Clemens John
2011-02-01 12:12       ` Bjoern Franke

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=4D4F1E31.4040200@kevinsteen.net \
    --to=ks@kevinsteen.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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.