Я новичок в работе системного и сетевого администратора, и мне нужна помощь.
Моя компания купила два новых маршрутизатора, потому что маршрутизатор ISP слишком прост для наших будущих потребностей (не может устанавливать маршруты и vlan на этом устройстве) и для расширения распространения Wi-Fi на два этажа компании (1 маршрутизатор на каждый этаж) .
После настройки маршрутизаторов мы отключили службу DHCP на ASUS, чтобы управлять ею на сервере Debian с двумя сетевыми адаптерами и такими службами, как bind9 и isc-dhcp-server, поскольку маршрутизаторы ASUS не сохраняют журналы (no / var / log / системный журнал, найденный на этих маршрутизаторах).
Я также помещаю интерфейсы VLAN на DNS-сервер DHCP, потому что компьютеры иногда получают неправильный IP-адрес (они получают IP-адрес от сервера ISP, но я отключу Wi-Fi и службу DHCP позже, потому что все подключены к ISP, когда мы закончим устанавливать маршрутизаторы).
Чтобы исправить это, я установил VLAN на коммутаторе Netgear (GS308T). Этот коммутатор не поддерживает IP-маршрутизацию или маршрутизацию VLAN. Наш план для VLAN:
Я думаю, что напортачил с VLAN, потому что после настройки маршрутов на обоих маршрутизаторах проблема такова:
Это странно, маршруты кажутся прекрасными при просмотре таблиц маршрутизации, поэтому я не знаю, неправильная ли конфигурация VLAN или нужно переделывать всю сеть ...
Я сделал несколько тестов:
Вот схема сети и конфигурация VLAN
И несколько файлов conf и команд:
DNS DHCP server interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
auto eth1
allow-hotplug eth1
#VLAN 103
auto eth1.103
iface eth1.103 inet static
address 192.168.141.2
netmask 255.255.255.0
gateway 192.168.141.1
vlan_raw_device eth1
#VLAN 104
auto eth0.104
iface eth0.104 inet static
address 192.168.140.2
netmask 255.255.255.0
gateway 192.168.140.1
vlan_raw_device eth0
DNS DHCP файл dhcpd.conf:
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name "kelenn.lan";
option domain-name-servers netcenter.kelenn.lan;
default-lease-time 600;
max-lease-time 7200;
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# The DRBL client class: PXE, Etherboot or DRBL client
class "DRBL-Client" {
match if
(substring(option vendor-class-identifier, 0, 9) = "PXEClient") or
(substring(option vendor-class-identifier, 0, 9) = "Etherboot") or
(substring(option vendor-class-identifier, 0, 10) = "DRBLClient");
}
#DHCP KT_NET_A
subnet 192.168.141.0 netmask 255.255.255.0 {
#interface eth1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.141.255;
option routers 192.168.141.1;
option domain-name-servers 192.168.141.2;
pool {
deny members of "DRBL-Client";
range 192.168.141.24 192.168.141.252;
}
}
#DHCP KT_NET_B
subnet 192.168.140.0 netmask 255.255.255.0 {
#interface eth0;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.140.255;
option routers 192.168.140.1;
option domain-name-servers 192.168.140.2;
pool {
deny members of "DRBL-Client";
range 192.168.140.24 192.168.140.252;
}
}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.example.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.example.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
Таблица маршрутизации DNS-сервера DHCP:
Destination Gateway Genmask Indic Metric Ref Use Iface
0.0.0.0 192.168.141.1 0.0.0.0 UG 0 0 0 eth1.103
192.168.140.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0.104
192.168.141.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1.103
ASUS RT-AC66U_B1 ip команда:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether b0:6e:bf:6f:80:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.139.2/24 brd 192.168.139.255 scope global eth0
3: dpsta: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether b0:6e:bf:6f:80:20 brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether b0:6e:bf:6f:80:24 brd ff:ff:ff:ff:ff:ff
6: vlan1@eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether b0:6e:bf:6f:80:20 brd ff:ff:ff:ff:ff:ff
7: vlan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether b0:6e:bf:6f:80:20 brd ff:ff:ff:ff:ff:ff
14: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether b0:6e:bf:6f:80:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.141.1/24 brd 192.168.141.255 scope global br0
Таблица маршрутизации ASUS RT-AC66U_B1:
Destination Gateway Genmask Flags Metric Ref Use Type Iface
192.168.139.1 * 255.255.255.255 UH 0 0 0 WAN0 eth0
192.168.139.0 * 255.255.255.0 U 0 0 0 WAN0 eth0
192.168.141.0 * 255.255.255.0 U 0 0 0 LAN br0
192.168.140.0 192.168.141.1 255.255.255.0 UG 1 0 0 LAN br0
default 192.168.139.1 0.0.0.0 UG 0 0 0 WAN0 eth0
ASUS 4G-AC68U ip команда:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 2c:fd:a1:38:ff:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.139.3/24 brd 192.168.139.255 scope global eth0
3: dpsta: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 2c:fd:a1:38:ff:60 brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 2c:fd:a1:38:ff:64 brd ff:ff:ff:ff:ff:ff
6: vlan1@eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 2c:fd:a1:38:ff:60 brd ff:ff:ff:ff:ff:ff
7: vlan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 2c:fd:a1:38:ff:60 brd ff:ff:ff:ff:ff:ff
9: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 62:52:00:e5:6a:46 brd ff:ff:ff:ff:ff:ff
13: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 2c:fd:a1:38:ff:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.140.1/24 brd 192.168.140.255 scope global br0
Таблица маршрутизации ASUS 4G-AC68U
Destination Gateway Genmask Flags Metric Ref Use Type Iface
192.168.139.1 * 255.255.255.255 UH 0 0 0 WAN0 eth0
192.168.139.0 * 255.255.255.0 U 0 0 0 WAN0 eth0
192.168.141.0 192.168.140.1 255.255.255.0 UG 1 0 0 LAN br0
192.168.140.0 * 255.255.255.0 U 0 0 0 LAN br0
default 192.168.139.1 0.0.0.0 UG 0 0 0 WAN0 eth0