On Apr 17, 2014, at 3:21, David Chisnall <theraven_at_FreeBSD.org> wrote: > Hi all, > > For a little while, I've had an issue with the machine that sits on the edge of my network deciding to start avahi as soon as a network is available, meaning that it then runs mDNS advertisements on the external interface and not the wireless one, requiring a manual restart once the machine boots. I'm now seeing something similar with pf - it manages to start before the external interface comes up and so silently ignores all of the rules for routing packets off the network. > > Do we have a mechanism for stating that certain services should not be started until ALL of the interfaces are up, rather than just the first one? Or even of restarting them when a new network appears? > I always thought the proper solution here was pf's built-in keywords "egress" and "ingress" interface names so you don't have to specify interface names that may or may not exist at the time the pf rules load.Received on Mon May 12 2014 - 10:51:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:49 UTC