Nightly build - LAN DHCP not working


#1

Hello all,

New to Vyos and trying to get it installed on a Protectli router I have here at home. I have followed the quick setup guide after installing the latest (14 September) nightly build. I have set the LAN to issue ip addresses in the 192.168.2.X range but it fails to assign any ip address at all. The relevant config is as follows:

nat {
source {
rule 100 {
outbound-interface eth0
source {
address 192.168.2.0/24
}
translation {
address masquerade
}
}
}
}
service {
dhcp-server {
shared-network-name LAN {
authoritative
subnet 192.168.2.0/24 {
default-router 192.168.2.1
dns-server 192.168.2.1
domain-name overseas.vyos.home
lease 86400
range 0 {
start 192.168.2.100
stop 192.168.2.200
}
}
}
}
dns {
forwarding {
cache-size 1500
listen-address 192.168.2.1
name-server 8.8.8.8
name-server 8.8.4.4
}
}
ssh {
port 512
}
}

LAN interface (eth1) is statically set to 192.168.2.1/24.

Has anyone else had similar issues. I tried 1.1.8 Stable and DHCP works just fine. However it is not compatible with my router and config changes are lost with a reboot.


#2

Please share your complete config, or add atleast the interface section. DHCP has undergone a rewrite and there could still be an issue. By having a full config it‘s easier to debug.


#4

Sure thing. I just rejiggered the LAN IP range but have the same results - no functioning DHCP on LAN

interfaces {
ethernet eth0 {
address dhcp
duplex auto
hw-id 00:e0:67:09:9e:64
smp-affinity auto
speed auto
}
ethernet eth1 {
address 10.0.2.1/24
duplex auto
hw-id 00:e0:67:09:9e:65
smp-affinity auto
speed auto
}
ethernet eth2 {
duplex auto
hw-id 00:e0:67:09:9e:66
smp-affinity auto
speed auto
}
ethernet eth3 {
duplex auto
hw-id 00:e0:67:09:9e:67
smp-affinity auto
speed auto
}
loopback lo {
}
}
nat {
source {
rule 100 {
outbound-interface eth0
source {
address 10.0.2.0/24
}
translation {
address masquerade
}
}
}
}
service {
dhcp-server {
shared-network-name LAN {
authoritative
subnet 10.0.2.0/24 {
default-router 10.0.2.1
dns-server 10.0.2.1
range 1 {
start 10.0.2.100
stop 10.0.2.200
}
}
}
}
dns {
forwarding {
cache-size 1500
listen-address 10.0.2.1
name-server 8.8.8.8
name-server 8.8.4.4
}
}
ssh {
port 512
}
}
system {
config-management {
commit-revisions 100
}
console {
device ttyS0 {
speed 9600
}
}
host-name vyos
login {
user vyos {
authentication {
encrypted-password $6$ajwtBsL0Bjq$zcUngn9ZRBkC5ABpRfc/frtAQWc84/kh20QEsBtQYaVgfxAQkZWBFwG4Bh9B2Sh3xmnMQBHJMMTwaxTsBT8mw0
plaintext-password “”
}
level admin
}
}
ntp {
server 0.pool.ntp.org {
}
server 1.pool.ntp.org {
}
server 2.pool.ntp.org {
}
}
syslog {
global {
facility all {
level notice
}
facility protocols {
level debug
}
}
}
time-zone UTC
}

/* Warning: Do not remove the following line. /
/
=== vyatta-config-version: “broadcast-relay@1:cluster@1:config-management@1:conntrack-sync@1:conntrack@1:dhcp-relay@1:dhcp-server@5:firewall@5:ipsec@4:mdns@1:nat@4:qos@1:quagga@2:system@9:vrrp@2:wanloadbalance@3:webgui@1:webproxy@1:zone-policy@1” === /
/
Release version: 1.2.0-rolling+201809141130 */


#5

Thanks for reporting.

Will be fixed in our next ISO rolling release. The bug you found is described here: https://phabricator.vyos.net/T845

Thanks!


#6

Most excellent! So just to be clear, tomorrow’s rolling should work correctly? This one issue stands between me and totally committing to vyos as a replacement for my current pfsense box. Well… Assuming vlans, peer to peer Ipsec, openvpn server and client, and PBR all work. Thanks for the quick response and fix!


#7

Correct.

It will be in the ISO image which comes AFTER vyos-1.2.0-rolling+201809141130-amd64.iso


#8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.