From: "sch tel" <telsch@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: traffic shaping on vlan make wireguard stop working
Date: Mon, 10 Jun 2019 21:58:06 +0200 [thread overview]
Message-ID: <trinity-3e3baf09-be1e-485c-b0f4-055e0b04701b-1560196686030@3c-app-gmx-bs07> (raw)
Hello list!
i tried to applied tc traffic shaping rules to limit outgoing traffic (independent of wireguard or not) on external vlan interface but after short time i applied that rules i can't even ping the other host through wg0 interface.
I have following setup:
eth0: external link
eth0.1: vlan1 fast uplink (primary)
eth0.2: vlan2 slow uplink (backup)
wg0: wireguard interface
eth1: internal link
My goals was to shape all traffic goes to one of the 2 vlan interfaces witch has different speeds. So i applied the rules on eth0.1 (and eth0.2):
tc qdisc del dev eth0.1 root 2>/dev/null
tc qdisc add dev eth0.1 root handle 1: htb default 17
tc class add dev eth0.1 parent 1: classid 1:1 htb rate 10mbit
tc class add dev eth0.1 parent 1:1 classid 1:16 htb rate 2mbit ceil 10mbit burst 4m
tc class add dev eth0.1 parent 1:1 classid 1:17 htb rate 8mbit ceil 10mbit burst 4m
tc qdisc add dev eth0.1 parent 1:16 handle 16: sfq perturb 10
tc qdisc add dev eth0.1 parent 1:17 handle 17: sfq perturb 10
tc filter add dev eth0.1 parent 1: protocol ip handle 0x64 fw flowid 1:16
iptables -t mangle -A OUTPUT -o 'wg+' -j MARK --set-mark 0x64
In iptables i see that packets are marked and packet counters count up, also in in tc:
tc -s class ls dev eth0.1
On server side udp packetes are still received.
Any hints whats i'm doing wrong with this kind of setup?
Thanks for help!
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-06-18 15:20 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-3e3baf09-be1e-485c-b0f4-055e0b04701b-1560196686030@3c-app-gmx-bs07 \
--to=telsch@gmx.de \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).