From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] vpn fw question
Date: Fri, 3 Oct 2014 15:41:00 +1300 [thread overview]
Message-ID: <CAKiAkGT_+BU4Bp8ZQezVdLt0qbom7g9-uwdkv-hbf+_qLn0uAA@mail.gmail.com> (raw)
In-Reply-To: <CAKiAkGT6mXN+dxQxseF2R=3LiuxoRY5ducOyDbV_h2dt9L1ofg@mail.gmail.com>
Most of the time, they just want to access a remote VPS/Torrent
Seedbox or $service from their local network.
On 3 October 2014 15:38, Joel Wirāmu Pauling <joel@aenertia.net> wrote:
> Yup - Routing is going to be better on performance. But is definately
> the more advanced/less common use case from my experience helping
> users do this.
>
> What I've got there tends to be what most users who ask this question
> are actually after.
>
>
>
> On 3 October 2014 15:36, Dave Taht <dave.taht@gmail.com> wrote:
>> On Thu, Oct 2, 2014 at 7:24 PM, Joel Wirāmu Pauling <joel@aenertia.net> 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.
>>
>> I'm not sure this is actually the case. What I used to do (not using openvpn
>> currently, took it down during heartbleed) was push out and pull in a
>> route or set of routes.
>>
>> 'course that requires a routing protocol on the other end...
>>
>>>
>>>
>>> -Joel
>>>
>>>
>>>
>>> On 3 October 2014 14:32, Eric S. Johansson <esj@eggo.org> wrote:
>>>> I was trying to setup my cerowrt box as an openvpn client. everything seems
>>>> to be working. The VPN link comes up, tun0 is created. I can access machines
>>>> on the far end of the link from the AP and vice versa. the openwrt
>>>> incantation for the vpn says to create an interface called vpn0
>>>>
>>>> network.vpn0=interface
>>>> network.vpn0.proto=none
>>>> network.vpn0.ifname=tun0
>>>>
>>>> ifconfig says tun0 exists but no vpn0. fw3 reload says:
>>>>
>>>> Warning: Section @zone[1] (lan) cannot resolve device of network 'lan'
>>>> Warning: Section @zone[2] (guest) cannot resolve device of network 'guest'
>>>>
>>>> sometimes it says: Warning: Section @zone[1] (lan) cannot resolve device of
>>>> network 'vpn0'
>>>>
>>>> tcpdump sees the ICMP request at se00 and tun0 but not at the remote target.
>>>> this leads me to believe that it's probably a firewall problem but I don't
>>>> know where the logs are.
>>>>
>>>> This brings me to one of the problem with had making changes in cerowrt,
>>>> namely, how the $##$& do you debug this thing? I've had to reflash this box
>>>> way too many times because I did something that effectively bricked it.
>>>> right now, I would settle for knowing where to find where logs are put.
>>>>
>>>> thanks
>>>> --- eric
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Cerowrt-devel mailing list
>>>> Cerowrt-devel@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>> _______________________________________________
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>>
>>
>> --
>> Dave Täht
>>
>> https://www.bufferbloat.net/projects/make-wifi-fast
next prev parent reply other threads:[~2014-10-03 2:41 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 [this message]
2014-10-03 3:05 ` Eric S. Johansson
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=CAKiAkGT_+BU4Bp8ZQezVdLt0qbom7g9-uwdkv-hbf+_qLn0uAA@mail.gmail.com \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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