https://netplan.io/faq#example-for-an-ifupdown-legacy-hook-for-post- uppost-down-states
You can use a networkd-dispatcherd to hook on vlan0 becoming routeable and then start/restart the dnsmasq service; On Fri, Jun 15, 2018 at 12:36 PM, Hadmut Danisch <had...@danisch.de> wrote: > So it is not possible to have an interface as optional (for other > reasons beyond that example) and still have a dnsmasq running for it? > > In former versions of ubuntu I had my bridges (some containing usb > ethernet interfaces to bridge virtual with physical machines) configured > in /etc/network/if-up.d, and started separate dnsmasq instances for > every single one of these bridges. > > Now there is no regular way to start a daemon like dnsmasq through ifup- > scripts, since netplan does not support them. Some people try to > workaround that problem with udev clauses, starting systemd services, > but then it's overcomplicated and error prone. > > So what is the offical way to have services like dnsmasq run for > optional interfaces under 18.04? > > > "Don't use optional" is a workaround, not a solution to the problem. If there > is no ifup-script anymore, then how are services to be started, once the > interface is up (late or just sometimes)? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777094 > > Title: > dnsmasq started too early, not getting all interfaces > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1777094 Title: dnsmasq started too early, not getting all interfaces Status in dnsmasq package in Ubuntu: Incomplete Status in netplan.io package in Ubuntu: Incomplete Bug description: Hi, I'm still struggling with 18.04 and the move from ifupdown to netplan. I am running a local virtual linux bridge as a network for several virtual machines and containers, which is to be serviced with dhcp and dns by dnsmasq. Conforming to latest designs from Ubuntu the bridge is now started by netplan and configured in /etc/netplan/60-vlan0.yaml straightforward. Since there is no ifupdown-scripts anymore, I've configured the default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that bridge. This works only when started manually. When booting ubuntu the normal way, the bridge is correctly generated, and dnsmasq is running, but it does *not* offer DNS for the bridge and does not occupy its port 53. But just a manual systemctl restart dnsmasq.service make it run as expected, then everything is fine. So my guess is that my configuration is correct, but dnsmasq simply started to early, i.e. before the bridge is created, and thus does not see the bridge when starting up. There's something wrong in the dependencies of the startup configuration. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jun 15 10:59:43 2018 InstallationDate: Installed on 2018-04-30 (45 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
