Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-21 Thread Simon Kelley
On 21/01/2019 08:59, Harald Dunkel wrote: > On 1/18/19 10:36 AM, Harald Dunkel wrote: >> >> Do you think dnsmasq could watch/ping its IP address range while it is >> idle, caching the result? It might examine the local arp table as well: >> If there is an entry with matching MAC and IP address,

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-21 Thread Simon Kelley
On 21/01/2019 11:49, Roy Marples wrote: > >> Will dnsmasq offer another IP address in case it receives a decline? > > It does with my testing, unless I hardcode the hardware address to a > fixed IP. This results in an infinite loop, but there's no real way > around that. It's supposed to gi

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-21 Thread Roy Marples
On 21/01/2019 08:59, Harald Dunkel wrote: But AFAICS strongswan's dhcp plugin doesn't, and surely it is not alone. Use another DHCP client that does then? There's no reason why dhcpcd can't work with StrongSwan. You even get a DHCPv6 client for free which StrongSwan doesn't support. Will dn

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-21 Thread Harald Dunkel
On 1/18/19 10:36 AM, Harald Dunkel wrote: Do you think dnsmasq could watch/ping its IP address range while it is idle, caching the result? It might examine the local arp table as well: If there is an entry with matching MAC and IP address, isn't it reasonable to assume that the IP address is not

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-18 Thread Geert Stappers
On Fri, Jan 18, 2019 at 10:36:19AM +0100, Harald Dunkel wrote: > On 1/17/19 11:58 PM, Simon Kelley wrote:> } } http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q1/012822.html } } } ... VPN ... > > The delay is while dnsmasq tests the address it's about to allocate in > > case some host

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-18 Thread Harald Dunkel
Hi Simon, On 1/17/19 11:58 PM, Simon Kelley wrote:> > The delay is while dnsmasq tests the address it's about to allocate in > case some host is already using it. It sends a ICMP echo request > (essentially a ping) and if it gets a reply, the test fails. After a 3 > second timeout the test succee

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-18 Thread Roy Marples
On 17/01/2019 22:58, Simon Kelley wrote: The delay is while dnsmasq tests the address it's about to allocate in case some host is already using it. It sends a ICMP echo request (essentially a ping) and if it gets a reply, the test fails. After a 3 second timeout the test succeeds and the address

Re: [Dnsmasq-discuss] 3 secs dhcp delay

2019-01-17 Thread Simon Kelley
On 17/01/2019 10:30, Harald Dunkel wrote: > Hi folks, > > I see a 3 to 4 secs delay for dnsmasq's dhcp protocol. Example: > > Strongswan's dhcp plugin obtains an IP address on behalf of the peer (a > road warrior laptop). The strongswan logfile on the host says > > : > Jan 14 10:48:07 18[IKE]

[Dnsmasq-discuss] 3 secs dhcp delay

2019-01-17 Thread Harald Dunkel
Hi folks, I see a 3 to 4 secs delay for dnsmasq's dhcp protocol. Example: Strongswan's dhcp plugin obtains an IP address on behalf of the peer (a road warrior laptop). The strongswan logfile on the host says : Jan 14 10:48:07 18[IKE] peer requested virtual IP %any Jan 14 10:48:07 18[CFG] send