Date: Tue, 23 Dec 2003 15:39:45 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Lee Dilkie <lee@dilkie.com> Cc: freebsd-questions@freebsd.org Subject: Re: ipfw2 Message-ID: <20031223153945.GB36128@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <006a01c3c95b$f02884a0$c10133ce@dilkie.com> References: <18400343353.20031223094425@mari-el.ru> <006a01c3c95b$f02884a0$c10133ce@dilkie.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--BwCQnh7xodEAoBMC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Dec 23, 2003 at 08:51:57AM -0500, Lee Dilkie wrote:
> > I think that it's right:
> > ipfw 1000 add permit all from 192.168.1.1/24{3,5,9} to any
> > but I see follwing:
> > ipfw: bad width ``243''
=20
> 192.168.1.1/24{3,5,9} translates to 192.168.1.1/243, 192.168.1.1/245 or
> 192.168.1.1/249.
Uh, at least, not in ipfw2 rulesets it doesn't. Where it does expand
like that is in csh(1), bash(1), zsh(1) and similar shells (but not
sh(1)):
% echo 192.168.1.1/24{3,5,9}
192.168.1.1/243 192.168.1.1/245 192.168.1.1/249
Perhaps the original poster was typing the rules in at the command
prompt? In which case, simply use a few quote marks to stop the
shell interfering:
# ipfw add 1000 permit all from '192.168.1.1/24{3,5,9}'
Or load the rules out of a file.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--BwCQnh7xodEAoBMC
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/6GHBdtESqEQa7a0RAvHPAJ9eY0ls/YmcH9Z6mjBYIcnCotfbYACfWXuA
R2EKJJMxwgjjy0tzrC9Xmmk=
=SjHT
-----END PGP SIGNATURE-----
--BwCQnh7xodEAoBMC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031223153945.GB36128>