Andrew Wood <and...@perpetualmotion.co.uk> writes:
> On 07/08/15 21:03, Mart van de Wege wrote:
>>
>> 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
>>
> Because even with nothing in /etc/network/interfaces dhcpd is seeing
> eth1.1 and eth1.2 and there are entries like this in syslog:
>
<snip logging>
That's just avahi trying to work with an interface it thinks still
exists.
what does the output of cat /proc/net/vlan/config show?
>
> It seems that the old settings are persisted somewhere and I suspect
> either avahi or systemd.
I don't know if it is particularly systemd that's persisting VLAn
ids. VLAN interfaces are meant to persist until you issue a vconfig rem
command, but I don't know if systemd persists the interfaces across
reboots.
As far as I know, it shouldn't. VLANs require an explicit .netdev
service file.
--
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/86d1yxil2x....@gaheris.avalon.lan
