On 08/08/15 21:25, Mart van de Wege wrote:
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.
cat /proc/net/vlan/config gives no such file
Given that the issue seems to be centered on dhcpd and it not knowing
which subet relates to which vlan interface why with nothing in
/etc/network/interfaces does syslog show this when trying to start dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: Wrote 13 leases to leases file.
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: No subnet declaration for eth1.2 (no
IPv4 addresses).
Aug 11 12:08:19 sentrybox dhcpd: ** Ignoring requests on eth1.2. If
this is not what
Aug 11 12:08:19 sentrybox dhcpd: you want, please write a subnet
declaration
Aug 11 12:08:19 sentrybox dhcpd: in your dhcpd.conf file for the
network segment
Aug 11 12:08:19 sentrybox dhcpd: to which interface eth1.2 is
attached. **
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: No subnet declaration for eth1.1 (no
IPv4 addresses).
Aug 11 12:08:19 sentrybox dhcpd: ** Ignoring requests on eth1.1. If
this is not what
Aug 11 12:08:19 sentrybox dhcpd: you want, please write a subnet
declaration
Aug 11 12:08:19 sentrybox dhcpd: in your dhcpd.conf file for the
network segment
Aug 11 12:08:19 sentrybox dhcpd: to which interface eth1.1 is
attached. **
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: Not configured to listen on any interfaces!
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: If you think you have received this
message due to a bug rather
Aug 11 12:08:19 sentrybox dhcpd: than a configuration issue please read
the section on submitting
Aug 11 12:08:19 sentrybox dhcpd: bugs on either our web page at
www.isc.org or in the README file
Aug 11 12:08:19 sentrybox dhcpd: before submitting a bug. These pages
explain the proper
Aug 11 12:08:19 sentrybox dhcpd: process and the information we find
helpful for debugging..
Aug 11 12:08:19 sentrybox dhcpd:
Aug 11 12:08:19 sentrybox dhcpd: exiting.
Aug 11 12:08:21 sentrybox isc-dhcp-server[1309]: Starting ISC DHCP
server: dhcpdcheck syslog for diagnostics. ... failed!
With this in dhcpd.conf:
#ddns-update-style interim;
default-lease-time 7200; #2 hours
max-lease-time 7200;
option web-proxy code 252 = text;
subnet 192.168.10.0 netmask 255.255.255.0{
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.10.255;
option routers 192.168.10.254;
range 192.168.10.1 192.168.10.199;
option domain-name-servers 192.168.10.254;
#option web-proxy "http://192.168.10.254/wpad.dat\000";;
option domain-name "commsmuseum.local";
#option ntp-servers 192.168.10.200;
}
With no vlans defined in /etc/network/interfaces and no ip addresses
assigned to the plain eth0 or eth1 how come its still referring to
eth1.1 and eth1.2 even after a reboot?
--
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/55ca0561.3020...@perpetualmotion.co.uk
