rc.order wrong (ipfw)

Jeremy Chadwick koitsu at FreeBSD.org
Fri Mar 16 21:50:49 UTC 2007


On Fri, Mar 16, 2007 at 06:00:30PM -0300, JoaoBR wrote:
> man, starting ipfw after network does not mean that the network is not up

Okay, imagine this order:

1) Kernel starts
2) Network driver is loaded
3) Link is brought up
4) Interface is configured for IP (manually or via DHCP)
5) Firewall rules (ipfw or pf) are applied

Do you realise that between steps #4 and steps #5 there is a small
window of time where someone may be able to send packets to your machine
and get responses which would normally be blocked by ipfw/pf?

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |



More information about the freebsd-stable mailing list