Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: "Eric S. Johansson" <esj@eggo.org>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] vpn fw question
Date: Fri, 3 Oct 2014 15:33:31 +1300	[thread overview]
Message-ID: <CAKiAkGRNqrm9WEKyvuG8ZKniBVzxOi+U65CTF=KhJXc_-0HE1g@mail.gmail.com> (raw)
In-Reply-To: <CAKiAkGRVLi_KpG0YyvQV5oOuoxyv8CorGfNCB1uSPCpZL0p8+g@mail.gmail.com>

Somewhat related question. Is anyone successfully using VxLANs in
Toronto release?

On 3 October 2014 15:24, 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.
>
>
> -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

  reply	other threads:[~2014-10-03  2:33 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 [this message]
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
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='CAKiAkGRNqrm9WEKyvuG8ZKniBVzxOi+U65CTF=KhJXc_-0HE1g@mail.gmail.com' \
    --to=joel@aenertia.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=esj@eggo.org \
    /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