From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave@taht.net>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] upgrading from CeroWRT --- seeking advice on rule testing
Date: Sun, 10 Feb 2019 17:34:49 -0500 [thread overview]
Message-ID: <11926.1549838089@localhost> (raw)
In-Reply-To: <87mun4yilz.fsf@taht.net>
[-- Attachment #1: Type: text/plain, Size: 2455 bytes --]
Dave Taht <dave@taht.net> wrote:
>> systems having DualStack with NAT44.
> I'm under the impression various ipv6 -> ipv4 nat tools are working much
> better now. I can't bring myself to care much about ipv6 until I too can
> get a static IPv6 allocation. I'm so fed up with the deployment that
> I've been working on adding ips to ipv4....
Well, you can get a static IPv6 allocation for a fee, you just need an ISP that
you can speak BGP to. That's really what your issue is more than the allocation.
>> The naming "se00" vs "ethXX" gets in the way. I have weird problems
>> where
>> machines behind the gateway can ping 8.8.8.8, but I can't ping it from
>> the
>> gateway. The details don't matter. I'm mostly writing this for future
>> people
>> googling. I spent another two hours today trying to debug (the first
>> time, I
>> had no working uplink, and I was missing tcpdump on the new unit. I
>> was
>> convinced my ISP had dropped my static routes)...
>>
>> So I will be starting again from scratch (total factory reset), get it
>> going, and then add my custom configuration.
> I generally prototype by having a second router entirely take over the
> functions of the network. Much like you added a pure wifi router, in
> your case I'd have got another router entirely, flashed openwrt, and
> tried to get each feature you needed working that way.
The problem with trying to make it all work in a test bench is that
it has to work with the v6 prefixes that matter, and those are in use.
So I guess I could put two routes in series and move things over VLAN by
VLAN. I have the untagged traffic out of the router go into VLAN3800
on the switch, which I can see from my desktop. At least the replacement
router has a serial console, which I never added to the original.
> I do wish cerowrt's stateless firewall idea had been adopted by openwrt,
> it leads to much less complicated rules to just pattern match for s+,
> g+, etc.
Hmm. I am not sure I understand your point.
It all looks the same to me, but perhaps I'm running into this differences
under the hood which is screwing me up.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-02-10 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 19:08 Michael Richardson
2019-02-09 17:30 ` Dave Taht
2019-02-10 22:34 ` Michael Richardson [this message]
2019-02-11 18:48 ` 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=11926.1549838089@localhost \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.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