From: Chris Lawrence <lordsutch@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Still trouble with 6in4 tunnel
Date: Mon, 11 Jun 2012 18:52:22 -0600 [thread overview]
Message-ID: <CANJCZG+RmN2FFHxZnbGGQdqWdJbYoes6qnRxQDqQv_2Y2WdX2w@mail.gmail.com> (raw)
In-Reply-To: <CEF5A6A5-C89C-434D-ABEE-B2C9AE711687@intermapper.com>
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
There may be a similar problem with the 6in4.sh script that was in the
6to4.sh script in /lib/network (look for the CeroWRT bug report on 6to4
lossage for my patch). I was having similar 6to4 issues due to there being
multiple LAN side interfaces.
Chris
[-- Attachment #2: Type: text/html, Size: 273 bytes --]
next prev parent reply other threads:[~2012-06-12 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1339182003.1217.cerowrt-devel@lists.bufferbloat.net>
2012-06-10 14:23 ` Richard Brown
2012-06-10 14:33 ` Dave Taht
2012-06-12 0:52 ` Chris Lawrence [this message]
[not found] <mailman.2.1339354802.28006.cerowrt-devel@lists.bufferbloat.net>
2012-06-19 15:26 ` Richard Brown
2012-06-19 16:05 ` Dave Taht
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=CANJCZG+RmN2FFHxZnbGGQdqWdJbYoes6qnRxQDqQv_2Y2WdX2w@mail.gmail.com \
--to=lordsutch@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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