[Cerowrt-devel] vpn fw question
Joel Wirāmu Pauling
joel at aenertia.net
Thu Oct 2 22:38:21 EDT 2014
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 at gmail.com> wrote:
> On Thu, Oct 2, 2014 at 7:24 PM, Joel Wirāmu Pauling <joel at 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...
>> On 3 October 2014 14:32, Eric S. Johansson <esj at 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
>>> ifconfig says tun0 exists but no vpn0. fw3 reload says:
>>> Warning: Section @zone (lan) cannot resolve device of network 'lan'
>>> Warning: Section @zone (guest) cannot resolve device of network 'guest'
>>> sometimes it says: Warning: Section @zone (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.
>>> --- eric
>>> Cerowrt-devel mailing list
>>> Cerowrt-devel at lists.bufferbloat.net
>> Cerowrt-devel mailing list
>> Cerowrt-devel at lists.bufferbloat.net
> Dave Täht
More information about the Cerowrt-devel