Date: Sat, 20 Jun 2020 10:08:53 -0400 From: mike tancsa <mike@sentex.net> To: "freebsd-pf@freebsd.org" <freebsd-pf@freebsd.org> Subject: altq on tun interfaces ? Message-ID: <e4747dbb-49be-9e0b-5ab1-366710def920@sentex.net>
next in thread | raw e-mail | index | archive | help
I think it used to work, but am wondering when things got changed to
tuntap in the driver, did it break altq or something else ?
I have a simple set of rules as
altq on tun504 bandwidth 960Kb hfsc queue { offsite, alltraff }
queue alltraff bandwidth 70% priority 8 qlimit 500 hfsc (realtime 60%)
queue offsite bandwidth 20% priority 7 qlimit 100 hfsc (realtime
20%,default)
pass out log on tun504 proto tcp from $inthosts to $BZone keep state
queue (alltraff)
pass out log on tun504 proto tcp from $inthosts to $dumpzone keep state
queue (offsite)
Generating traffic from $inthosts across this box exiting on tun504 sees
the bandwidth max out (10Mb) instead of anywhere near 1Mb or max queue
total.
man altq | grep tun
The tun(4) and ng_iface(4) pseudo drivers also do support ALTQ.
Anyone have a working example of altq on a tun interface for a recent
releng11 or releng12 ?
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4747dbb-49be-9e0b-5ab1-366710def920>