|
|||||||||||
|
/etc/rc: pf vs. dhclient ... lockd, too
From: Chris Jepeway <jepeway(at)blasted-heath.com>
Date: Mon Nov 25 2002 - 13:11:50 EST
I've recently moved from an ISDN line to a 'net spigot provided by my cable company. In the ISDN days, my connection was managed by a NetGear router. It handled the ISDN line and most all of the packet mangling I wanted, filters and NAT and such. What with a cable modem to handle the link, I now mangle packets with OpenBSD and pf. The cable co hands out IP addrs via DHCP, so I must run both dhclient and pf. They don't play very nicely together: the default "block in all / block out all" pf rules in /etc/rc kills the DHCP and ICMP packets dhclient needs to obtain a lease. Here's a patch that adds RULES to /etc/rc that let dhclient do its thing. It works for me, but I think it should be considered as an illustration of what needs fixing rather than as a "swear to God, this is the right way to do it." I'm not at all sure, eg, what the preferred method of grotting through the hostname.if files in /etc should be. /etc/netstart came to mind, but cut-n-paste didn't seem like the right thing. Oh, and the patch also changes lockd_flags from a boolean into a set of real flags, useful for debugging NFS locks as in "lockd_flags=-d". This patch is against /etc/rc version 1.185 distributed w/ OpenBSD-3.0. Should I submit this via 2X sendbug? One for lockd, one for RULES? Chris <jepeway@blasted-heath.com>.
@@ -272,8 +289,8 @@
echo -n > /var/db/mountdtab
echo -n ' mountd'; mountd
echo -n ' nfsd'; nfsd ${nfsd_flags}
- if [ X${lockd} = X"YES" ]; then
- echo -n ' rpc.lockd'; rpc.lockd
fi Received on Mon Nov 25 13:12:56 2002 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:48:27 EDT |
||||||||||
|
|||||||||||