On 07/08/15 21:03, Mart van de Wege wrote:
Because even with nothing in /etc/network/interfaces dhcpd is seeing eth1.1 and eth1.2 and there are entries like this in syslog:Why do you think that? Avahi does multicast DNS, which, as far as I know, has nothing to do with VLANs. So what makes you think Avahi is the culprit? That said, if you want to disable it completely: systemctl stop avahi-daemon.service systemctl disable avahi-daemon.service systemctl stop avahi-daemon.socket systemctl disable avahi-daemon.socket Then edit /etc/nsswitch.conf and remove all references to mdns4 Mart
avahi-daemon[687]: Withdrawing address record for 192.168.10.254 on eth1.Aug 7 19:34:09 sentrybox avahi-daemon[687]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.10.254. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Interface eth1.IPv4 no longer relevant for mDNS. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.10.254. Aug 7 19:34:09 sentrybox avahi-daemon[687]: New relevant interface eth1.IPv4 for mDNS. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Registering new address record for 192.168.10.254 on eth1.IPv4. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Withdrawing address record for 192.168.10.254 on eth1. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.10.254. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Interface eth1.IPv4 no longer relevant for mDNS. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.10.254. Aug 7 19:34:09 sentrybox avahi-daemon[687]: New relevant interface eth1.IPv4 for mDNS. Aug 7 19:34:09 sentrybox avahi-daemon[687]: Registering new address record for 192.168.10.254 on eth1.IPv4.
It seems that the old settings are persisted somewhere and I suspect either avahi or systemd.