From: Jan Hetges <tran@ms20.net>
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.] two-way-tunnel quirks
Date: Mon, 3 Dec 2007 22:03:09 -0600 [thread overview]
Message-ID: <20071204040309.GA3827@apoderado.ometepe.net> (raw)
In-Reply-To: <200712021954.24310.axel@open-mesh.net>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Hi Axel
On Sun, Dec 02, 2007 at 07:54:24PM +0100, Axel Neumann wrote:
> ...
> >
> > > - Can you describe it in way that i can reproduce it ?
> >
> > A---B---C
> >
> > A: your computer
> >
> > B: bmxd_rv804 client node }
> > }running 2-way-tunnel
> > C: bmxd_rv804 gw node }
>
> I am just curious, can you confirm if the following correctly
> describes the HNA/SNAT of your setup:
>
> for the two-way-tunnel setup:
> - you were doing SNAT at Cs' upstream interface AND at Bs' bat0 interface
MASQUERADE
>
> for the one-way tunnel setup:
> - you are only doing SNAT at Cs' upstream interface
no, i still do MASQUERADE also on Bs' bat0, because i was too lazy to
comment it out ;-)
> - and additionally an HNA announcement by B for the address used by A
yes, but also with 2-way-tunnel (because i want net internal routing)
cheers
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-04 4:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 23:28 [B.A.T.M.A.N.] two-way-tunnel quirks Jan Hetges
2007-12-01 17:34 ` Marek Lindner
2007-12-01 20:41 ` Axel Neumann
2007-12-02 5:39 ` Jan Hetges
2007-12-06 3:18 ` Marek Lindner
2007-12-02 4:32 ` Jan Hetges
2007-12-02 18:54 ` Axel Neumann
2007-12-03 17:47 ` Predrag Balorda
2007-12-04 4:03 ` Jan Hetges [this message]
2007-12-04 9:05 ` Axel Neumann
2007-12-04 13:00 ` Jan Hetges
2007-12-04 15:05 ` Axel Neumann
2007-12-04 10:01 ` Axel Neumann
2007-12-04 12:37 ` 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=20071204040309.GA3827@apoderado.ometepe.net \
--to=tran@ms20.net \
--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.