Re: ppp and pf interacting badly?
On Fri, Jan 27, 2006 at 07:12:14PM -0500, Peter wrote: > --- cpghost <[EMAIL PROTECTED]> wrote: > > Is there any way to tell pf startup script to wait for ppp > > until all needed interfaces have really come up? > > >From the OpenBSD 3.8 manpage (should be good for you): > > Host name resolution and interface to address translation are done > at ruleset load-time. When the address of an interface (or host > name) changes (under DHCP or PPP, for instance), the ruleset must > be reloaded for the change to be reflected in the kernel. Sur- > rounding the interface name (and optional modifiers) in parentheses > changes this behaviour. When the interface name is surrounded by > parentheses, the rule is automatically updated whenever the inter- > face changes its address. The ruleset does not need to be reload- > ed. This is especially useful with nat. Ah, good point! I'll try this on the next maintenance window! Thanks for the valuable hint. Are you sure it also works for interfaces that don't exist yet? It's not a question of tun0 changing addresses (static IP in this particular case), but of tun0 not existing before ppp has a chance to start at all? -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp and pf interacting badly?
--- cpghost <[EMAIL PROTECTED]> wrote: > Hello, > > has anyone else seen this strange interaction between > (user-)ppp and pf (on RELENG_6)? > > When configuring tun0 as external interface in pf.conf, > pf won't start when booting, because ppp has not yet had > time to initialize tun0. Result is, that pf is then > disabled (!). > > After booting, calling > /etc/rc.d/pf start > manually works well though, since tun0 is now there > and pf can initialize. > > Am I the only one seeing this happen? > > Is there any way to tell pf startup script to wait for ppp > until all needed interfaces have really come up? >From the OpenBSD 3.8 manpage (should be good for you): Host name resolution and interface to address translation are done at ruleset load-time. When the address of an interface (or host name) changes (under DHCP or PPP, for instance), the ruleset must be reloaded for the change to be reflected in the kernel. Sur- rounding the interface name (and optional modifiers) in parentheses changes this behaviour. When the interface name is surrounded by parentheses, the rule is automatically updated whenever the inter- face changes its address. The ruleset does not need to be reload- ed. This is especially useful with nat. -- Peter __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ppp and pf interacting badly?
Hello, has anyone else seen this strange interaction between (user-)ppp and pf (on RELENG_6)? When configuring tun0 as external interface in pf.conf, pf won't start when booting, because ppp has not yet had time to initialize tun0. Result is, that pf is then disabled (!). After booting, calling /etc/rc.d/pf start manually works well though, since tun0 is now there and pf can initialize. Am I the only one seeing this happen? Is there any way to tell pf startup script to wait for ppp until all needed interfaces have really come up? Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
