Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-12 released
Date: Fri, 21 Mar 2014 19:51:43 +0100	[thread overview]
Message-ID: <87lhw38jwg.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw6Y3V29Ynk+2DE+5RrPzSe7X6WeoJK9CcPAHPTRUBsCdQ@mail.gmail.com> (Dave Taht's message of "Fri, 21 Mar 2014 17:47:42 +0000")

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

Dave Taht <dave.taht@gmail.com> writes:

> 2) People using this on an interior gateway on a complex network will
> need to either disable bcp38 or (preferably) add their rfc1918
> network(s) to the exception list on the interior gateway (not on the
> external gateway). For example, the yurtlab lives on subnets
> 172.21.0.0/20.

Well, depending on the topology it might not be needed. There's an
auto-detection mechanism built-in which tries to auto-detect the
upstream network settings. So as long as you only need to access one
upstream subnet, no configuration change is needed.

If it does *not* work, I'd appreciate seeing the output of the following
commands to try to improve the auto-detection feature:

ipset list
ip route
ip addr

along with the network that's being blocked.

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2014-03-21 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:47 Dave Taht
2014-03-21 18:51 ` Toke Høiland-Jørgensen [this message]
2014-03-21 22:00 ` Sebastian Moeller
2014-03-21 22:53   ` Toke Høiland-Jørgensen
2014-03-21 23:04     ` Sebastian Moeller
2014-03-21 23:26       ` Toke Høiland-Jørgensen
     [not found]         ` <608F3E46-3D81-48A3-B60C-E90661DD3AB2@gmx.de>
2014-03-22 11:08           ` Toke Høiland-Jørgensen
2014-03-22 17:09             ` Dave Taht
2014-03-22 18:18               ` Toke Høiland-Jørgensen
2014-03-22 20:20               ` Sebastian Moeller
2014-03-22 19:23             ` Sebastian Moeller
2014-03-22 19:36               ` Toke Høiland-Jørgensen
2014-03-22 20:24                 ` Sebastian Moeller
2014-03-24  0:56 ` Valdis.Kletnieks
2014-03-24 14:35   ` Jim Reisert AD1C
2014-03-26  4:37     ` Kai Yang
2014-03-24 16:32 ` [Cerowrt-devel] upnp oddness (was " Valdis.Kletnieks

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=87lhw38jwg.fsf@toke.dk \
    --to=toke@toke.dk \
    --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