On 20/12/11 20:55, Thomas Schweikle wrote: > 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? >
That's exactly what happens without --bind-interface, interfaces which are configured in dnsmasq but don't exist at startup generate a warning only, and start to work when they are created. Packets from interfaces which are not configured are ignored. Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
