DHCP lease stuck on 2 hours 43minutes 29 seconds

[Capt.Nemo]

Thank you for that. The engineers might also like to know that I have also tried disabling the dhcp server on the Billion for the main network and have another dhcp server issue leases in the range 192. 168.2.xxx while leaving the dhcp server on the billion guest network active issuing leases in the range 192.168.1.xxx. The results are

1) The ethernet screen of the LAN section correctly switches between the main and guest networks showing the one dhcp server disabled and the other enabled.

2) The dhcp menu item in the status section disappears, no matter which ip address is used to access the router [192.168.2.254 for the main network, 192.168.1.254 for the guest network].

3) The ARP table correctly shows machines on both networks with ip addresses issued by both dhcp servers.

Many thanks for you help, I hope that this will all be resolved in a new firmware release.

[billion_fan]

Thank you for that. The engineers might also like to know that I have also tried disabling the dhcp server on the Billion for the main network and have another dhcp server issue leases in the range 192. 168.2.xxx while leaving the dhcp server on the billion guest network active issuing leases in the range 192.168.1.xxx. The results are

1) The ethernet screen of the LAN section correctly switches between the main and guest networks showing the one dhcp server disabled and the other enabled.

2) The dhcp menu item in the status section disappears, no matter which ip address is used to access the router [192.168.2.254 for the main network, 192.168.1.254 for the guest network].

3) The ARP table correctly shows machines on both networks with ip addresses issued by both dhcp servers.

Many thanks for you help, I hope that this will all be resolved in a new firmware release.

Thanks for that, lets see what our engineers come up with

[frogfoot]

I'm Having similar problems, but with a 8800axl.
I have a guest WiFi network set up, and separated from the LAN by creating a separate LAN group containing only the guest network.
(so my kids friends don't infect my network )
However the DHCP table is showing lots of leases expiring in 2 hours, 43 minutes, 29 seconds
In addition attempting to view the DHCP table locks up the router for up to 3 minutes, during which time SNMP requests fail and Telnet is unavailable.
Finally... one last annoyance is the Syslog seems to incorrectly tag some events as ERROR which are informational only, and is not tagging the entry with the hostname so they appear with no name on the remote server

Code: Select all

Apr 18 20:36:13 daemon err syslog: dhcpd:sending ACK to 192.168.2.5
Apr 18 20:38:37 daemon err syslog: dhcpd:sending OFFER of 192.168.2.8
Apr 18 20:38:37 daemon err syslog: dhcpd:sending ACK to 192.168.2.8
Apr 18 20:43:39 daemon err syslog: dhcpd:sending OFFER of 192.168.2.8

Currently running 2.32d.dh13 firmware

[billion_fan]

I'm Having similar problems, but with a 8800axl.
I have a guest WiFi network set up, and separated from the LAN by creating a separate LAN group containing only the guest network.
(so my kids friends don't infect my network )
However the DHCP table is showing lots of leases expiring in 2 hours, 43 minutes, 29 seconds
In addition attempting to view the DHCP table locks up the router for up to 3 minutes, during which time SNMP requests fail and Telnet is unavailable.
Finally... one last annoyance is the Syslog seems to incorrectly tag some events as ERROR which are informational only, and is not tagging the entry with the hostname so they appear with no name on the remote server

Code: Select all

Apr 18 20:36:13 daemon err syslog: dhcpd:sending ACK to 192.168.2.5
Apr 18 20:38:37 daemon err syslog: dhcpd:sending OFFER of 192.168.2.8
Apr 18 20:38:37 daemon err syslog: dhcpd:sending ACK to 192.168.2.8
Apr 18 20:43:39 daemon err syslog: dhcpd:sending OFFER of 192.168.2.8

Currently running 2.32d.dh13 firmware

I have just pushed our engineers again, waiting for a reply now

[Capt.Nemo]

Any news on when we can expect a resolution to this problem so that I can properly use a guest network?

[billion_fan]

Any news on when we can expect a resolution to this problem so that I can properly use a guest network?

Try firmware 2.32e

[Capt.Nemo]

Better, in that it now does not freeze with a fixed time, but still not correct.

I attach screenshots of the ARP and dhcp tables.
The arp table shows the permanent (static) dhcp leases and the ip addresses of those devices currently operating and linked to the router (completed). Please note specifically ip address 192.168.2.3 (the ip addresses 192.168.2.1xx have been issued by a different dhcp server the Billion router issues only leases from 192.168.2.1 to 192.168.2.100).

The dhcp table on the other hand lists only 192.168.2.1 (not listed in the arp table as it is an internet radio which at the time was switched off so this is correct) and does not list 192.168.2.3.

The dhcp table should of course keep a record of leases issued until they expire, the device must at this time have been disconnected for at lease half the lease period and should not therefore be in the arp table. The device in question was in fact connected and in use so was correctly listed in the arp table and incorrectly missing from the dhcp table; so I regret to say that the Billion is still unreliable when it comes to issuing dhcp leases, as it could still issue the same lease twice.

[Capt.Nemo]

And I've just received the first complaint that an ip address is already in use!

[ricke17]

Have you tried returning the router and getting it replaced with a new one - your issue with this has been dragging on for too long!

[frogfoot]

And I've just received the first complaint that an ip address is already in use!

Interesting, I flashed the 2.32e firmware last night and have now had two instances of windows machines complaining that the address in already in use. Now gone back to 2.32d.dh65, due to this and the fact that I lost 1.5M upload throughput.