On 18/05/2021 21:15, Nick Howitt wrote:
On 18/05/2021 20:57, Geert Stappers wrote:
On Fri, May 14, 2021 at 08:30:42AM +0100, Nick Howitt wrote:
On 13/05/2021 22:30, Geert Stappers via Dnsmasq-discuss wrote:
On Thu, May 13, 2021 at 09:31:21PM +0100, Nick Howitt wrote:
On 13/05/2021 19:26,
On 18/05/2021 20:57, Geert Stappers wrote:
On Fri, May 14, 2021 at 08:30:42AM +0100, Nick Howitt wrote:
On 13/05/2021 22:30, Geert Stappers via Dnsmasq-discuss wrote:
On Thu, May 13, 2021 at 09:31:21PM +0100, Nick Howitt wrote:
On 13/05/2021 19:26, Geert Stappers via Dnsmasq-discuss wrote:
On Fri, May 14, 2021 at 08:30:42AM +0100, Nick Howitt wrote:
> On 13/05/2021 22:30, Geert Stappers via Dnsmasq-discuss wrote:
> > On Thu, May 13, 2021 at 09:31:21PM +0100, Nick Howitt wrote:
> > > On 13/05/2021 19:26, Geert Stappers via Dnsmasq-discuss wrote:
> > > > On Thu, May 13, 2021 at 01:05:0
On 13/05/2021 22:30, Geert Stappers via Dnsmasq-discuss wrote:
On Thu, May 13, 2021 at 09:31:21PM +0100, Nick Howitt wrote:
On 13/05/2021 19:26, Geert Stappers via Dnsmasq-discuss wrote:
On Thu, May 13, 2021 at 01:05:07PM +0100, Nick Howitt wrote:
I am trying to help someone who has a set u
On Thu, May 13, 2021 at 09:31:21PM +0100, Nick Howitt wrote:
> On 13/05/2021 19:26, Geert Stappers via Dnsmasq-discuss wrote:
> > On Thu, May 13, 2021 at 01:05:07PM +0100, Nick Howitt wrote:
> > > I am trying to help someone who has a set up with three LAN's, all on
> > > different subnets and all
The most obvious explanation for this is that the two LANs in question
have becomes bridged together at level 2.
Simon.
On 13/05/2021 13:05, Nick Howitt wrote:
> I am trying to help someone who has a set up with three LAN's, all on
> different subnets and all acting as DHCP servers. He is getting
On 13/05/2021 19:26, Geert Stappers via Dnsmasq-discuss wrote:
On Thu, May 13, 2021 at 01:05:07PM +0100, Nick Howitt wrote:
I am trying to help someone who has a set up with three LAN's, all on
different subnets and all acting as DHCP servers. He is getting an odd
result that when a device on
On 13/05/2021 21:01, Horn Bucking wrote:
According to dnsmasq documentation, it would seem neither dhcp-option
nor dhcp-range (at least for IPv4) would accept an interface:
-O,
--dhcp-option=[tag:,[tag:,]][encap:,][vi-encap:,][vendor:[],][|option:|option6:|option6:],[[,]]
-F,
--dhcp-rang
According to dnsmasq documentation, it would seem neither dhcp-option
nor dhcp-range (at least for IPv4) would accept an interface:
-O,
--dhcp-option=[tag:,[tag:,]][encap:,][vi-encap:,][vendor:[],][|option:|option6:|option6:],[[,]]
-F,
--dhcp-range=[tag:[,tag:],][set:,][,|][,[,]][,time>]
On Thu, May 13, 2021 at 01:05:07PM +0100, Nick Howitt wrote:
> I am trying to help someone who has a set up with three LAN's, all on
> different subnets and all acting as DHCP servers. He is getting an odd
> result that when a device on the enp2s0 LAN requests an IP, both enp2s0 and
> enp3s0 respon
I am trying to help someone who has a set up with three LAN's, all on
different subnets and all acting as DHCP servers. He is getting an odd
result that when a device on the enp2s0 LAN requests an IP, both enp2s0
and enp3s0 respond with IP's. I've never seen this before and my own
server does n
11 matches
Mail list logo
