From: "Eric S. Johansson" <esj@eggo.org>
To: "Joel Wirāmu Pauling" <joel@aenertia.net>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] vpn fw question
Date: Thu, 02 Oct 2014 23:05:11 -0400 [thread overview]
Message-ID: <542E1267.1000208@eggo.org> (raw)
In-Reply-To: <CAKiAkGRVLi_KpG0YyvQV5oOuoxyv8CorGfNCB1uSPCpZL0p8+g@mail.gmail.com>
On 10/2/2014 10:24 PM, Joel Wirāmu Pauling wrote:
> I.e Your topology looks like this :
>
> [(Remote LAN) - VPN Client]---[INTERNET]---(Local LAN)[WAN][LAN][REMOTE-LAN])
>
> Your Local LAN knows nothing about Remote LAN and Vice versa. There is
> just a single Inteface/Client member that is a member of REMOTE-LAN.
> So to get traffic from Local LAN to Remote LAN all Local-LAN traffic
> needs to be masqueraded to that Single interface.
ah, thanks for the clarification. my function oriented topology looks
like this:
[ 34-38 target lan - vpn server - fw ] - - - [ I ] - + -( fw - vpn
client - - - lan - - - workerbees(6) )
+ -( rw worker bee )
+ -( rw worker bee )
+ -( cerowrt worker bee ) ...
I don't think the natted form is going to work terribly well because all
the WB's need access to all the target machines. Also our routing tables
are… significant
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
0.0.0.0 73.38.246.1 0.0.0.0 UG 0 0 0
ge00
10.42.66.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.1.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.2.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.3.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.4.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.5.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.6.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.7.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.8.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.9.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.10.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.11.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.12.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.13.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.14.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.43.15.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.199.188.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
10.199.188.193 0.0.0.0 255.255.255.255 UH 0 0 0
tun0
73.38.246.0 0.0.0.0 255.255.254.0 U 0 0 0
ge00
172.30.42.0 0.0.0.0 255.255.255.224 U 0 0 0
se00
172.30.42.0 0.0.0.0 255.255.255.0 ! 0 0 0 *
172.30.42.64 0.0.0.0 255.255.255.224 U 0 0 0
sw00
172.30.42.96 0.0.0.0 255.255.255.224 U 0 0 0
sw10
192.168.9.0 10.199.188.193 255.255.255.0 UG 0 0 0
tun0
and WTH is this?
172.30.42.0 0.0.0.0 255.255.255.0 ! 0 0 0 *
--- eric
next prev parent reply other threads:[~2014-10-03 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 1:32 Eric S. Johansson
2014-10-03 2:02 ` Dave Taht
2014-10-03 2:16 ` Eric S. Johansson
2014-10-03 2:21 ` Joel Wirāmu Pauling
2014-10-03 2:24 ` Joel Wirāmu Pauling
2014-10-03 2:33 ` Joel Wirāmu Pauling
2014-10-03 2:36 ` Dave Taht
2014-10-03 2:38 ` Joel Wirāmu Pauling
2014-10-03 2:41 ` Joel Wirāmu Pauling
2014-10-03 3:05 ` Eric S. Johansson [this message]
2014-10-03 3:38 ` Dave Taht
2014-10-03 4:09 ` Dave Taht
2014-10-03 4:12 ` Eric S. Johansson
2014-10-03 4:32 ` Dave Taht
2014-10-03 5:38 ` Eric S. Johansson
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542E1267.1000208@eggo.org \
--to=esj@eggo.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=joel@aenertia.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