After reading the man page and doing research on the web I thought I had
resolved an issue that I was having regarding default gateways, and while
it appears to have corrected my gateway issue I may have introduced an new
issue.
Little history - we are using Dnsmasq to serve dhcp to about 25
-option=net:net4,3,10.192.9.1
If I am understanding correctly this should apply to the ranges including
the option 82 addresses, or do I need to modify the the Option 82
statements to add the GW?
Thanks,
Keith
On Sat, Jul 1, 2017 at 1:37 PM, Keith Lyons <klyon...@gmail.com> wrote:
> In a re
In a recent post I was asking about sending the correct gateway to the dhcp
client, there were two options presented to me
do away with the dhcp-option=option-router statement, which I fear will
render the clients un-pingable or learn how to use tags.
Since this is a production dhcp server and
-2b.plant.ldn01:ge-0/0/18.0:pack1-5-302,10.192.4.41,10.192.4.41,255.255.255.0
dhcp-range=net:05_port_05,temp-2b.plant.ldn01:ge-0/0/9.0:pack1-5-302,10.192.4.51,10.192.4.51,255.255.255.0
Thanks!
On Wed, Jun 28, 2017 at 5:24 PM, Simon Kelley <si...@thekelleys.org.uk>
wrote:
> On 28/06/17 13:25, Ke
I have Dnsmasq configured for option 82 for three different subents:
10.192.4.x, 10.192.5.x and 10.192.9.x, all of the clients get the proper
IP's as expected via the Option 82 statements, but the 10.192.5 and
10.192.9.x clients are getting the Gateway for the 10.19.4.x subnet.
We are using
Hello,
I recently built a DHCP server using Dnsmasq on Centos7 VM and had a
question about having more than one subnet and gateway
We are using Option82 for 15 devices on each subnet, at this time only one
subnet is active but I expect that the other two subnets will need to be
active in the
