DHCP Server only works to OLD/Previous subnet....giving out 192.168.0.x instead of 192.168.1.x
In DHCP Server
Share this post:
Responses (13)
-
Accepted Answer
So update it? Network > Infrastructure > DHCP Server.
BTW, 192.168.0.0/24 and 192.168.1.0/24 are best avoided if you can. There are plenty of other better /24 subnets available in the RFC1918 address space. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
log:
Mar 24 23:32:38 gw systemd: Started DNS caching server..
Mar 24 23:32:38 gw dnsmasq: dnsmasq: failed to bind DHCP server socket: Address already in use
Mar 24 23:32:38 gw dnsmasq[6959]: failed to bind DHCP server socket: Address already in use
Mar 24 23:32:38 gw dnsmasq[6959]: FAILED to start up
Mar 24 23:32:38 gw systemd: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 24 23:32:38 gw systemd: Unit dnsmasq.service entered failed state.
Mar 24 23:32:38 gw systemd: dnsmasq.service failed.
file:
# This file is managed by the API. Please add custom options in dnsmasq.conf.
dhcp-option=enp0s25,1,255.255.255.0
dhcp-option=enp0s25,28,192.168.1.255
dhcp-option=enp0s25,3,192.168.1.2
dhcp-option=enp0s25,6,192.168.1.2
dhcp-range=enp0s25,192.168.1.100,192.168.1.254,12h -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »