From 38df56caf6d7a730ba789f8eeb973a862fc606b1 Mon Sep 17 00:00:00 2001 From: glebius Date: Mon, 10 Oct 2005 15:14:37 +0000 Subject: - Note that ng_iface(4) now supports ALTQ. - Explain when ALTQ should be used on ng_iface(4) and when not. --- share/man/man4/altq.4 | 9 +++++---- share/man/man4/ng_iface.4 | 19 ++++++++++++++++++- 2 files changed, 23 insertions(+), 5 deletions(-) (limited to 'share') diff --git a/share/man/man4/altq.4 b/share/man/man4/altq.4 index 550a0fd..e5baf3f 100644 --- a/share/man/man4/altq.4 +++ b/share/man/man4/altq.4 @@ -25,7 +25,7 @@ .\" .\" $FreeBSD$ .\" -.Dd July 07, 2005 +.Dd October 10, 2005 .Dt ALTQ 4 .Os .Sh NAME @@ -146,9 +146,10 @@ and thus all encapsulated drivers. .Pp The .Xr tun 4 -pseudo driver also does support -.Nm -and includes the required modifications. +and +.Xr ng_iface 4 +pseudo drivers also do support +.Nm . .Sh SEE ALSO .Xr pf 4 , .Xr pf.conf 5 , diff --git a/share/man/man4/ng_iface.4 b/share/man/man4/ng_iface.4 index a35ba6d..39633f5 100644 --- a/share/man/man4/ng_iface.4 +++ b/share/man/man4/ng_iface.4 @@ -35,7 +35,7 @@ .\" $FreeBSD$ .\" $Whistle: ng_iface.8,v 1.5 1999/01/25 23:46:26 archie Exp $ .\" -.Dd February 3, 2005 +.Dd October 10, 2005 .Dt NG_IFACE 4 .Os .Sh NAME @@ -138,7 +138,24 @@ node does go away when all hooks have been disconnected; rather, and explicit .Dv NGM_SHUTDOWN control message is required. +.Sh ALTQ Support +The +.Nm +interface supports ALTQ bandwidth management feature. +However, +.Nm +is a special case, since it is not a physical interface with limited bandwidth. +One should not turn ALTQ on +.Nm +if the latter corresponds to some tunneled connection, e.g. PPPoE or PPTP. +In this case ALTQ should be configured on the interface, that is used to +trasmit the encapsulated packets. +In case when your graph ends up with some kind of serial line, either +synchronous or modem, then +.Nm +is the right place to turn ALTQ on. .Sh SEE ALSO +.Xr altq 4 , .Xr bpf 4 , .Xr netgraph 4 , .Xr ng_cisco 4 , -- cgit v1.1