From: Axel Neumann <axel@open-mesh.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: Tue, 4 Dec 2007 10:05:46 +0100 [thread overview]
Message-ID: <200712041005.46329.axel@open-mesh.net> (raw)
In-Reply-To: <20071204040309.GA3827@apoderado.ometepe.net>
Hi,
On Dienstag 04 Dezember 2007, Jan Hetges wrote:
> 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 ;-)
Interesting to know that this is possible, because (as I understand):
- Internet Uplink packets are MASQUERADEd (*) when being entunnelled at Bs'
bat0 interface and a second time at your upstream GW interface
A B C
eth0 eth0 bat0 bat0 dsl0 Internet
>---------->*===============>*--------->
MASQUERADE MASQUERADE
- Downlink packets are de-MASQUERADED (*) at Cs' upstream interface (dsl0).
But using one-way-tunnel, the Downlink packets are NOT routed via the
bat-tunnel, therefore downlick packets will not come out of Bs' bat0
interface and (I thought) would not be de-MASQERADEd (?) !
A B C
eth0 eth0 wlan0 wlan0 dsl0 Internet
<----------<?---------------<*---------<
de-MASQUERDE? de-MASQUERADE
catched my draft ? Please correct me if I misunderstood!
ciao
/axel
>
> > - 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
next prev parent reply other threads:[~2007-12-04 9:05 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
2007-12-04 9:05 ` Axel Neumann [this message]
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=200712041005.46329.axel@open-mesh.net \
--to=axel@open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox