On 11/08/15 21:09, Mart van de Wege wrote:
cat /proc/net/vlan/config gives no such file
That would mean that the 8021q module is not loaded.
So your interfaces don't have VLANs at all, as the VLAN driver isn't
even loaded.
So somehow there is some configuration left that refers to
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
Andrew Wood and...@perpetualmotion.co.uk writes:
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
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
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
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
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
On Fri 07 Aug 2015 at 20:00:33 +0100, Andrew Wood wrote:
On 07/08/15 19:49, Brian wrote:
apt-get purge avahi-daemon
That wants to remove all of Gnone too. Im starting to think this is related
to systemd and that Id be better going back to Wheezy. Things are not
behaving as expected.
Oh
On 07/08/15 19:49, Brian wrote:
apt-get purge avahi-daemon
That wants to remove all of Gnone too. Im starting to think this is
related to systemd and that Id be better going back to Wheezy. Things
are not behaving as expected.
--
To UNSUBSCRIBE, email to
On Fri 07 Aug 2015 at 19:46:09 +0100, Andrew Wood wrote:
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.
On 04/08/15 07:11, Bonno Bloksma wrote:
Hello Andrew,
When you use VLANS essentialy what you are doing is creating different
networks. So all should have their own ip address range. If not you get
problems when you want to connect them via a router which would then see the
same ip range on
Hello Andrew,
On 03/08/15 14:44, Bonno Bloksma wrote:
I have a similar setup but the untagged network is the management
network for the APs. All traffic on the WiFi network is done in VLANS. That
is how I have it setup.
So in that case you should have 3 definitions on eth1 (assuming
Hi,
On 30/07/15 23:14, Arno Schuring wrote:
This configures an untagged connection, which is not the same as vlan
1. Also, there's no need to set that broadcast address manually, it's
inferred from the netmask.
auto eth1.2
iface eth1.2 inet static
address 192.168.100.254
netmask
On 03/08/15 14:44, Bonno Bloksma wrote:
I have a similar setup but the untagged network is the management network
for the APs. All traffic on the WiFi network is done in VLANS. That is how I
have it setup.
So in that case you should have 3 definitions on eth1 (assuming traffic for the
On 8/1/2015 1:30 AM, Andrew Wood wrote:
On 30/07/15 23:14, Arno Schuring wrote:
This configures an untagged connection, which is not the same as vlan
1. Also, there's no need to set that broadcast address manually, it's
inferred from the netmask.
auto eth1.2
iface eth1.2 inet static
On 30/07/15 23:14, Arno Schuring wrote:
This configures an untagged connection, which is not the same as vlan
1. Also, there's no need to set that broadcast address manually, it's
inferred from the netmask.
auto eth1.2
iface eth1.2 inet static
address 192.168.100.254
netmask 255.255.255.0
On 30/07/15 22:34, Matt Ventura wrote:
Could you post the DHCPD config?
default-lease-time 7200; #2 hours
max-lease-time 7200;
option web-proxy code 252 = text;
#Subnet 192.168.10.d our private network
#As a convention we're using d values 1 to 199 for DHCP (192.168.10.1
etc), 200
and
On 07/30/2015 01:43 PM, Andrew Wood wrote:
Can I please clarify the correct way to configure VLANS on Jessie as
Im having problems with DHCPD giving out IP addresses for the wrong
VLAN subnet but only for certain clients - Windows 7, Apple iOS
whereas Debian clients and Windows XP clients are
Date: Thu, 30 Jul 2015 21:43:25 +0100
From: aw...@comms.org.uk
Ive got a Jessie machine acting as a router with eth0 being the WAN
connection to the internet and eth1 being the LAN connection with 2
VLANS on it (VLAN1 has addresses 192.168.10.x and VLAN2 192.168.100.x)
Your /e/n/interfaces
19 matches
Mail list logo
