From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] babeld change
Date: Mon, 17 Jun 2013 00:04:27 +0200 [thread overview]
Message-ID: <87a9mppv9w.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw6Up+t6BqReqPReWM+xarNfkngVqvue_+bV9Y3GH=1fKg@mail.gmail.com> (Dave Taht's message of "Sun, 16 Jun 2013 14:55:56 -0700")
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
Dave Taht <dave.taht@gmail.com> writes:
> Hmm. Does this mean you have 6in4 working correctly in your build of
> cero? I'm still just doing it with a script, not netifd.
Yeah. I have this in /etc/config/network:
config interface sixxs
option 'proto' '6in4'
option 'ifname' 'sixxs'
option peeraddr '<sixxs ipv4 endpoint>
option ip6addr '<ipv6 endpoint addr>'
option ip6prefix '<ipv6 prefix>/48'
option mtu '1480'
option ipaddr '<public ipv4 addr as assigned to ge00>'
and each internal interface definition then has a
option 'ip6assign' '64'
optionally with
option 'ip6hint '1'
to force the <prefix>:1::/64 subnet to be assigned to the interface.
> Hmm. We're back at wanting a message bus or std kernel api for dealing
> with the ip rule database again... I fear that things like openvpn or
> strongswan will really mess with this.
Isn't that message bus called netlink?
> Babel head has three branches doing new stuff. In particular, the
> configuration syntax is changing in some respects...
Yeah, I noticed everything is becoming configurable from the config file.
> hah. I just realized that a couple of the commits in babeld head were
> yours. cool. no need for me to lecture.
Well, my setup broke when openwrt did the multi-wan stuff. Had to fix
that... :P
> One thing that always bugged me about previous versions of babeld was
> that it didn't chomp whitespace at the end of a line, hopefully that's
> fixed somewhere in this patch series...
Isn't that something you set your editor to do? :P
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-06-16 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:15 Dave Taht
2013-06-16 21:47 ` Toke Høiland-Jørgensen
2013-06-16 21:55 ` Dave Taht
2013-06-16 22:04 ` Toke Høiland-Jørgensen [this message]
2013-06-16 22:08 ` [Cerowrt-devel] Field Report - installing 3.8.13-7 Rich Brown
2013-06-16 22:29 ` Toke Høiland-Jørgensen
2013-06-16 22:35 ` Dave Taht
2013-06-16 22:54 ` Rich Brown
2013-06-17 8:24 ` Toke Høiland-Jørgensen
2013-06-17 4:15 ` [Cerowrt-devel] babeld change Steven Barth
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=87a9mppv9w.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