problem with dhcp and vlan

Hello,

I have a tumbleweed server with dhcp, named and ntp servers.I use wicked to control the network
The last snapshot with the usrmerge let me an unbootable system and I needed to do a new install.

In YaST network I defined 4 vlans and 4 routes

[FONT=courier new]││Name                                   │IP Address      │Device│Note 
││NetXtreme BCM5719 Gigabit Ethernet PCIe│NONE            │eno3  │     
││NetXtreme BCM5719 Gigabit Ethernet PCIe│NONE            │eno1  │enslaved in br0   
││NetXtreme BCM5719 Gigabit Ethernet PCIe│Not configured  │eno4  │ 
││NetXtreme BCM5719 Gigabit Ethernet PCIe│NONE            │eno2  
││br0                                    │192.168.1.120/32│br0   │ 
││vlan1                                  │192.168.1.1/24  │vlan1 │parent: eno2 
││vlan2                                  │192.168.2.1/24  │vlan2 │parent: eno2 
││vlan3                                  │192.168.3.1/24  │vlan3 │parent: eno2
││vlan4                                  │192.168.4.1/24  │vlan4 │parent: eno2
Routing Table
┌──────────────────────────────────────────── 
│Destination   │Gateway    │Device│Options 
│192.168.2.0/24│192.168.2.1│eno2  | 
│192.168.3.0/24│192.168.3.1│eno2  │
│192.168.4.0/24│192.168.4.1│eno2  │
│192.168.1.0/24│192.168.1.1│eno2  │[/FONT]

In the dhcpd.conf I defined 4 ranges of addresses

subnet 192.168.1.0 netmask 255.255.255.0 {
  zone pce23.net. { primary 192.168.1.120; key PCEKEY; }
  zone 1.168.192.in-addr.arpa. { primary 192.168.1.120; key PCEKEY; }
  pool {
    option routers 192.168.1.1;
    option domain-name-servers 192.168.1.120;
        #  failover peer "pce23failover";
    range 192.168.1.160 192.168.1.250;
    ddns-domainname "pce23.net.";
    ddns-hostname "hpprol2";
  }
}
subnet 192.168.2.0 netmask 255.255.255.0 {
  zone pce23.net. { primary 192.168.1.120; key PCEKEY; }
  zone 2.168.192.in-addr.arpa. { primary 192.168.1.120; key PCEKEY; }
  pool {
    option routers 192.168.2.1;
    option domain-name-servers 192.168.1.120;
option broadcast-address 192.168.2.255;
    range 192.168.2.100 192.168.2.199;
    ddns-domainname "pce23.net.";
    ddns-hostname "hpprol2";
  }
}
subnet 192.168.3.0 netmask 255.255.255.0 {
  zone pce23.net. { primary 192.168.1.120; key PCEKEY; }
  zone 3.168.192.in-addr.arpa. { primary 192.168.1.120; key PCEKEY; }
  pool {
    option routers 192.168.3.1;
    option domain-name-servers 192.168.1.120;
option broadcast-address 192.168.3.255;
    range 192.168.3.100 192.168.3.199;
    ddns-domainname "pce23.net.";
    ddns-hostname "hpprol2";
  }
}
subnet 192.168.4.0 netmask 255.255.255.0 {
   option routers 192.168.4.1;
   option domain-name "samdom.pce23.net";
   option domain-name-servers 192.168.1.91;
   option broadcast-address 192.168.4.255;
   range 192.168.4.100 192.168.4.199;
   ddns-domainname "samdom.pce23.net.";
   ddns-rev-domainname "in-addr.arpa.";
   ddns-hostname "rasp";
   zone samdom.pce23.net. { primary 192.168.1.91; key PCEKEY; }
 }


A windows pc in vlan3 ask for a DHCP address and receives address 192.168.3.100 but i’m unable to obtain a an address in vlan2: I see via wireshark DHCPDISCOVER frames but the tumbleweed server doesn’t receive it or drop it (No answer in wireshark)

My network topology


 ┌────────────────────────┐                      ┌───────┐
 │ Tumbleweed Server with │ eno3 (no IP)         │ CABLE │
 │ DHCP + DNS + firewalld ├───────────ppp0───────│ Modem ├─── Internet
 │                        │                      │       │
 │ do intervlan routing   │                      └────┬──┘
 └───┬────────────────┬───┘                    Gateway│ (192.168.1.1)
 eno2 (No IP)     eno1 (192.168.1.120)                │
     │                │enslaved in br0 (for VM)       │
     │                │                               │     
trunk│ port           │                               │
 ┌───┴────────────────┴───────────────────────────────┴─────────────┐
 │         TL─SG3216         Swithch Level 2                        │
 │                                                                  │
 │                         VLAN  ID                                 │
 │1                 2                  3                    4       │
 │192.168.10/24) (192.168.2.0/24) (192.168.3.0/24) (192.168.4.0/24) │
 └───┬─────────────┬──────────────────┬─────────────────────┬───────┘
     │             │                  │                     │
     │             │                  │                     │
 Samba            PCs                 PCs                  Printer
 192.168.1.91  192.168.2.100─     192.168.3.100─        192.168.4.50
               192.168.2.199      192.168.3.199

The only difference is that the PC in vlan3 is windows 10 professional (works) while in vlan2 they are windows 10 home.(not working)
Active routing

ip route show
default dev ppp0 scope link 
10.24.97.36 dev ppp0 proto kernel scope link src 91.179.230.4 
192.168.1.0/24 dev vlan1 proto kernel scope link src 192.168.1.1 
192.168.2.0/24 dev vlan2 proto kernel scope link src 192.168.2.1 
192.168.3.0/24 dev vlan3 proto kernel scope link src 192.168.3.1 
192.168.4.0/24 dev vlan4 proto kernel scope link src 192.168.4.1 

in sysconfig I defined the interfaces for dhcpd

Current Selection: Network/DHCP/DHCP server
Setting of: DHCPD_INTERFACE
vlan1 vlan2 vlan3 vlan4

Seems that I missed something for DHCP but I’m unable to see what

Any Idea?
Many thanks in advance
Philippe

Obligatory first question - does stopping firewall help?

Thanks,

with firewalld stopped same problem. But I found that the tplink switch has a cable randomly failing. with a new cable the dhcp worked but with a strange error:
I had tested this pc on vlan 3 and i had address 192.168.3.101. Connecting it on vlan2 I see that DHCP accepted the old address

Jun 04 14:43:48 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:43:48 hpprol2 dhcpd[2357]: DHCPACK on 192.168.3.101 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2

thereafter no connection to internet.
I tried multiple time a ipconfig /renew in windows but the address was stil wrong

Jun 04 14:54:55 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:54:55 hpprol2 dhcpd[2357]: DHCPACK on 192.168.3.101 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:54:58 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:54:58 hpprol2 dhcpd[2357]: DHCPACK on 192.168.3.101 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:55:00 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:55:00 hpprol2 dhcpd[2357]: DHCPACK on 192.168.3.101 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:55:03 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:55:03 hpprol2 dhcpd[2357]: DHCPACK on 192.168.3.101 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2

I disconnected the pc from the lan, rebooted it and reconnect to lan==> then DHCP refuses the address and proposes the correct address

Jun 04 14:59:56 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.3.101 from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2: wrong network.
Jun 04 14:59:56 hpprol2 dhcpd[2357]: DHCPNAK on 192.168.3.101 to 30:9c:23:cc:63:40 via vlan2
Jun 04 14:59:56 hpprol2 dhcpd[2357]: DHCPDISCOVER from 30:9c:23:cc:63:40 via vlan2
Jun 04 14:59:57 hpprol2 dhcpd[2357]: DHCPOFFER on 192.168.2.100 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:59:57 hpprol2 dhcpd[2357]: DHCPREQUEST for 192.168.2.100 (192.168.2.1) from 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2
Jun 04 14:59:57 hpprol2 dhcpd[2357]: DHCPACK on 192.168.2.100 to 30:9c:23:cc:63:40 (DESKTOP-CKBLGFD) via vlan2

I don’t know if this is a problem or a normal behaviour from DHCP
This problem is now solved :slight_smile:

Regards
Philippe

Try adding “authoritative” global option.