[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NAT and DHCP
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: NAT and DHCP
- From: Henning Brauer <lists-openbsd_(_at_)_bsws_(_dot_)_de>
- Date: Sun, 4 Aug 2002 21:49:59 +0200
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Sat, Aug 03, 2002 at 07:24:55PM +0200, Nick Nauwelaerts wrote:
> On Sat, 3 Aug 2002 19:01:31 +0200
> Holger Weiss <lists_(_at_)_jhweiss_(_dot_)_de> wrote:
> > Well, I actually _do_ use a script because I'm using the IP in my
> > pf.conf
why? use the interface name there, too.
> , but for reloading the NAT rules it should be enough to put
> > !bg /sbin/pfctl -N /etc/nat.conf
...and !bg /sbin/pfctl -R /etc/pf.conf...
> > in /etc/ppp/ppp.linkup.
> Aahh yes, like that. Indeed we were talking about different things. This
> will work with (most) dial-up and ADSL, but will fail on (most) cable
> modems. The -current solutions fits all problems.
well, actually, the solution we have right now has several limitations -
most specifically, the interface name only expands to the "first" address of
the interface. we didn't see a sesible way around this limitation even after
revisting that issue and thinking about it for a looooooong time, so, you
just have to know and keep in mind about it - it's fine for the ppp case,
may lead to undesired results on "normal" statically configured ethernet
interfaces with multiple IPs.
Visit your host, monkey.org