On 10/05/11 06:47, Takayuki Kaiso wrote:
Hi Simon
Thank you.
I did the test with dnsmasq-2.58test8, which gave me the URL and
got the following problem with DHCPREQUEST.
Mar 4 21:23:17 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]:
DHCPDISCOVER(wlan1) 00:1e:52:ab:77:fd
Mar 4 21:23:17 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]:
DHCPOFFER(wlan1) 192.168.5.161 00:1e:52:ab:77:fd
Mar 4 21:23:18 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]:
DHCPREQUEST(wlan1) 192.168.5.161 00:1e:52:ab:77:fd
Mar 4 21:23:18 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]: DHCPNAK(wlan1)
192.168.5.161 00:1e:52:ab:77:fd wrong network
Mar 4 21:23:18 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]:
DHCPREQUEST(wlan1) 192.168.5.161 00:1e:52:ab:77:fd
Mar 4 21:23:18 RMRZOO-81 daemon.info dnsmasq-dhcp[19120]: DHCPNAK(wlan1)
192.168.5.161 00:1e:52:ab:77:fd wrong network
There's something odd here. The problems we've been chasing are the
result of configured clients renewing leases with a restarted dnsmasq
that has never seen a packet which comes via the relay, but this starts
with a DHCPDISCOVER, which _must_ have come via the relay.
Please could you give us as much information as possible about the
configuration of dnsmasq, the relay, and your networks and addresses. I
think something strange is going on.
Simon.
