From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Tom Gundersen <teg@jklm.no>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Tue, 21 Oct 2014 16:18:51 -0700 [thread overview]
Message-ID: <87siih9fl0.fsf@toke.dk> (raw)
In-Reply-To: <CAG-2HqVgYzMF9WiQOtAqPY2xXT7yG+UPZ_qjAnUCpqk-hvymXw@mail.gmail.com> (Tom Gundersen's message of "Tue, 21 Oct 2014 19:24:28 +0200")
Tom Gundersen <teg@jklm.no> writes:
> I have now subscribed to cerowrt-devel (long overdue), and I would
> very much appreciate any comments you guys may have on our networking
> work in systemd. In particular, if there are any more tweaks like
> making fq_codel the deafult, which would be the reasonable choice for
> 95% of users (most of whom don't know about these things and would
> otherwise never touch them), we are very open to suggestions.
One thing that has gone into openwrt recently but is not supported in
systemd-networkd is source-specific routing. Since I got an internet
connection too fast for the WNDR to keep up, I've transitioned to an x86
box running Arch Linux for that link. It uses systemd-networkd to setup
most of the networking (which works very well!), but one thing missing
is support for source-specific routing.
Right now, I have a systemd unit to set up my IPv6 tunnel with this in
it:
ExecStart=/usr/bin/ip tunnel add he-ipv6 mode sit remote 216.66.80.90 ttl 255 dev enp2s0
ExecStart=/usr/bin/ip link set he-ipv6 up
ExecStart=/usr/bin/ip addr add 2001:470:xx::2/64 dev he-ipv6
ExecStart=/usr/bin/ip route add default via 2001:470:xx::1 from 2001:470:yy::/48 proto static
ExecStart=/usr/bin/ip route add default via 2001:470:xx::1 from 2001:470:xx::2/128 proto static
ExecStart=/usr/bin/ip route add default from ::/128 dev he-ipv6
The top three lines I can replace by a file in /etc/systemd/network, but
not the bottom three.
Also, having a way to make systemd units depend on network interface
availability (and configuration state) would be neat; to do things like
start up a VPN daemon when the WAN connection becomes available. :)
-Toke
next prev parent reply other threads:[~2014-10-21 23:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03 ` Dave Taht
2014-10-20 17:41 ` Valdis.Kletnieks
2014-10-21 14:50 ` Michal Schmidt
2014-10-21 16:27 ` Valdis.Kletnieks
2014-10-21 16:57 ` Dave Taht
2014-10-21 17:05 ` Michal Schmidt
2014-10-21 17:24 ` Tom Gundersen
2014-10-21 17:44 ` Michal Schmidt
2014-10-21 17:52 ` David Personette
2014-10-21 18:00 ` Michal Schmidt
2014-10-21 18:06 ` Tom Gundersen
2014-10-21 19:21 ` Dave Taht
2014-10-21 19:51 ` Dave Taht
2014-10-21 20:59 ` Dave Taht
2014-12-04 16:09 ` Tom Gundersen
2014-12-04 18:24 ` Dave Taht
2014-10-21 23:18 ` Toke Høiland-Jørgensen [this message]
2014-12-04 15:05 ` Tom Gundersen
2014-12-04 15:08 ` Toke Høiland-Jørgensen
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=87siih9fl0.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=teg@jklm.no \
/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