Support DHCP in rc.firewall by default?

[David Wolfskill]

>From: "Roderick van Domburg" <r.s.a.vandomburg at student.utwente.nl>
>To: <freebsd-current at freebsd.org>
>Date: Fri, 13 Jun 2003 11:18:45 +0200
>Subject: Support DHCP in rc.firewall by default?

>Right now, rc.firewall isn't set up to support DHCP configurations although
>it could easily be done so.

More or less, depending on one's requirements.

>Googling comes up with many references, for
>example http://www.freebsddiary.org/firewall.php (section "ipfw with DHCP
>etc" at the bottom of the page).

>Are there any reasons against having rc.firewall contain such lines? I
>reckon it would even come in handy for statically configured users: they'd
>only need to specify their network interface(s) once.

Well, you might consider submitting a PR with a suggested patch.  :-)

That said:  a while back (around the time that the BayLISA meetings
moved to Apple's facility, where they have wireless Internet access
available, and the DHCP server provides routable IP addresses), I
decided that setting up my laptop to make use of ipfw would be A Good
Thing.

The approach I used was to have a default configuration that blocked
everything but DHCP/BOOTP, then, in /etc/dhclient-exit-hooks, once I
know I have received a DHCP lease, invoke a script (with the
newly-assigned IP address as one of the arguments).

Note that I also had set up dhclient-exit-hooks to determine my hostname
(given the IP address) -- if it could, and to try to make use of an NTP
server.

Whether or not all of that comes very close to anyone else's perceived
requirements, I don't know -- but my guess is that it is fairly
idiosyncratic, at best.

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Based on what I have seen to date, the use of Microsoft products is not
consistent with reliability.  I recommend FreeBSD for reliable systems.