Hmmmm. If this is the reason, how to force dnsmasq not to respond on some interfaces, while listening on all others, with different configurations per interface?
Wouldn't it be better to configure dnsmasq even for interfaces not there at startup, and if these interfaces come up take them, if configs match? Avoiding unconfigured interfaces? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/876458 Title: dnsmasq started before all interfaces are up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/876458/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
