Closed marmalodak closed 2 years ago
If you don't want it to wait for network you can set the wait_for_network value to false. https://github.com/chilcote/outset/wiki/NetworkTimeout#removing-the-network-timeout-requirement
Also if you are on an ipv6 network that check may not be valid anymore 😕
I'm sorry, I was obviously unclear.
I want outset to wait until the network is ready. The problem I'm having is that outset aborts because the network is not up yet.
Ah I see. Sorry. The plist you are referencing is the default setting, I think. Is this a ipv6 only network? For whatever reason it doesn't think you're getting an IP.
You may want to turn this to false and then add your own logic for this as a boot-every script and name it such that it runs first alphanumerically (AAA_towing.sh or something) which does its own network wait that is more relevant to the network you're on.
I reviewed that code (and its predecessor, the place we all crib notes when writing python in the macadmin world, munki) and I was surprised that the check doesn't ignore link-local when considering if the network is up (because if an interface that can't route/doesn't have DHCP I don't consider that 'up', in 2021 at least), but we should look at the timeout and confirm the sleep(10) behavior is still firing properly.
I think I figured it out - this only kicks in (as documented on the wiki) for boot-once, not items in boot-every
. I'm not sure why this was decided on in particular with the original design? We can get it changed, I agree it's unintuitive why you'd only want boot-timed actions to have network connectivity when you're running one-and-done actions.
I'm going to close this since outset seems to be doing the right thing for my case and I haven't encountered any more problems like this.
Is there something wrong with my plist? What should I do to get outset to run?
My plist settings seem to be ignored. I get the same output from outset every time:
I don't know if this help, but:
Big Sur 11.2.1