Andrew Wood <and...@perpetualmotion.co.uk> writes:
>>
>> On 04/08/15 07:11, Bonno Bloksma wrote:
>>>
>>>
>>> If you have the option, as in this case, it might make sense to use
>>> the same number for the VLAN and for the address range. It does not
>>> NEED to be so, and most cases it will not be so. But if it is a
>>> simple situation like this, one can take advantage of it.
>>> Remember to set the VLANs correctly on the ports to the Debian
>>> router / firewall / dhcp server and on the ports to the WiFi
>>> APs. In this case untagged VLAN 1, tagged VLAN 10 and 11.
>>>
>>>
>>> Bonno Bloksma
>>
>>
> I think avahi is causing some problems how do I disable it completely?
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
--
"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/86wpx6j26s....@gaheris.avalon.lan
