From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] a start at vething cake for 200 subscribers
Date: Sat, 28 Jul 2018 14:03:11 -0700 [thread overview]
Message-ID: <CAA93jw7y1wW6x13AsW1KcO71LNQWtx9J7+Q2+yT1taz9bccSxg@mail.gmail.com> (raw)
so I was tempted to try. I didn't enable namespaces. just coded this
little bit up...
a very quick test of this setup showed I wasn't routing packets through the
veth interfaces so I figure network namespaces, and... oh look! the sun's out!
#!/bin/bash
# Create the bridge
ip link add cable type bridge
ip link set cable up
# Create network namespaces and veth interfaces
# do I even need to use namespaces?
# do I need ips just to pass it through to the bridge?
ip route flush proto 51
for client in `seq 2 10`
do
c=c${client}
ip netns del $c
ip netns add $c
# probly all this needs to end up in namespaces
ip link add ${c}.l type veth peer name ${c}.r
ip link set ${c}.l up
ip link set ${c}.r up
ip addr add 10.10.0.1/24 dev ${c}.l
ip addr add 10.10.0.$client/24 dev ${c}.r
# fixme add ipv6 subnets
# I kind of wanted the route table to be global tho
ip route add 10.10.0.$client/32 dev ${c}.l proto 51
# fixme add default route back?
tc qdisc replace dev ${c}.l root cake bandwidth 20mbit flows
done
# fixme hook up to the bridge
# fixme hang actual clients off the bridge? or the namespace
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
reply other threads:[~2018-07-28 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7y1wW6x13AsW1KcO71LNQWtx9J7+Q2+yT1taz9bccSxg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@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