--cvVnyQ+4j833TQvp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 2006-10-25 02:15, Cristian KLEIN <cristi@net.utcluj.ro> wrote:
> Talking about /etc/rc.d/ipfw, when using dummynet and ipfw, both
> compiled as modules, /etc/rc.d/ipfw is unable to load "pipe"s in the
> ruleset, because there is no place dummynet is loaded. On the contrary,
> loading dummynet also loads ipfw.
>=20
> Few people encounter this problem, as dummynet is usually compiled into
> the kernel. I solved the problem by changing "kldload ipfw" with
> "kldload dummynet" in /etc/rc.d/ipfw. I wouldn't know a general way of
> solving this problem. Perhaps ipfw should load dummynet when
> encountaring a "pipe" rule?
AFAIK, a good and general way of solving this is to load dummynet from
`/boot/loader.conf', so it will be available when the `/etc/rc.d/ipfw'
script fires up.
--cvVnyQ+4j833TQvp
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFFR1dt1g+UGjGGA7YRAn9IAJsEgsQOpwDro+ZigT/nFNk+3lCGqwCgxTnl
xD8WEM6hMqXYQUQKWRoQcpw=
=wCmG
-----END PGP SIGNATURE-----
--cvVnyQ+4j833TQvp--