public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: David Beaumont <djb31st@gmail.com>
Subject: Re: [B.A.T.M.A.N.] Nat Question
Date: Thu, 12 Aug 2010 13:29:28 +0200	[thread overview]
Message-ID: <201008121329.29995.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <AANLkTimnri5HYfhPWEhvwGsoaKzhSn6d2MvrRjV8KVQg@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 544 bytes --]

David Beaumont wrote:
> Hopefully attachments come though ok?
> 
> net_ is from the router connected to the internet
> mesh_ is the other side of the mesh

to the mesh thing:

 * Why has ath0 an IP... which also conflicts with the ip range of bat0 and
   br-lan?

 * Why has bat0 an ip when it is part of br-wan.

 * Why has the ath0 device iptables entries?

to the net thing:

 * why has bat0 an ip when it is part of br-lan?


Why don't I see masquerade anywhere in the iptables output (-t nat)?

Best regards,
	Sven

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

  reply	other threads:[~2010-08-12 11:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.375.1281525844.17951.b.a.t.m.a.n@lists.open-mesh.org>
     [not found] ` <AANLkTim-RfupM1iHH-dFwtDiN5RLFVaP=AWK9=MH-dGK@mail.gmail.com>
2010-08-11 11:48   ` [B.A.T.M.A.N.] Nat Question David Beaumont
     [not found]     ` <AANLkTinhcpamuMGApH9D5SPn3VNkEi9BDCYwGkRcDdJq@mail.gmail.com>
2010-08-11 12:50       ` David Beaumont
2010-08-12  9:31     ` Marek Lindner
2010-08-12  9:38       ` David Beaumont
2010-08-12  9:50         ` Sven Eckelmann
2010-08-12 10:11           ` David Beaumont
2010-08-12 10:16             ` David Beaumont
2010-08-12 10:33               ` Marek Lindner
2010-08-12 10:41                 ` David Beaumont
2010-08-12 10:50                   ` Marek Lindner
2010-08-12 11:08                     ` David Beaumont
2010-08-12 11:29                       ` Sven Eckelmann [this message]
2010-08-12 11:41                         ` David Beaumont
2010-08-12 13:14                           ` David Beaumont
2010-08-12 13:19                             ` Marek Lindner
2010-08-12 13:26                               ` David Beaumont
2010-08-12 13:27                                 ` David Beaumont
2010-08-13  5:45                                   ` David Beaumont
2010-08-14 14:46                                     ` Marek Lindner
2010-08-16 13:11                                       ` David Beaumont
2010-08-16 16:32                                         ` Sven Eckelmann
2010-08-17  8:14                                           ` David Beaumont
2010-08-20  9:53                                             ` David Beaumont
2010-08-20  9:57                                             ` David Beaumont
2010-08-20  9:58                                               ` David Beaumont
2010-08-20 11:27                                                 ` Sven Eckelmann
2010-08-23  7:05                                                   ` David Beaumont

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=201008121329.29995.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=djb31st@gmail.com \
    /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