Re: Wait for interface existence?
Roy <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.network |
|---|---|
| Message-ID | <[email protected]> |
You would write an arrival and departure script for ifwatchd. Each one would test for the existence of non existence of your requirements using ifconfig or any other tools and then take whatever action is required. We have devpubd which does similar for other devices. Using scripts is how you put your reactive requirements in. Roy On 28 August 2023 18:14:52 BST, Mouse <[email protected]> wrote: >>> I find myself wanting a tool that waits until a certain set of >>> network interfaces exists. (I want this so I can, for example, have >>> a boot-time script wait until tap0 and tap1 both exist, then do >>> whatever is appropriate.) >> ifwatchd? > >Related, but I don't see any way to get what I want out of ifwatchd >without significant additional tooling around it. > >ifwatchd can run something when tap0 is created and when tap1 is >created, but unless I've missed something it would take additional >tooling to notice that both those events have happened and shut down >the ifwatchd process. > >/~\ The ASCII Mouse >\ / Ribbon Campaign > X Against HTML [email protected] >/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B