Am I correct that there is a rathere severe bug in the DHCP server in the Hub 3 where
(1) leases are renewed daily irrespective of the lease length set in the options, and
(2) instead of extending existing leases every device is disconnected from the network and must re-connect.
This is my experience on two Hub 3s, and it is.
Is this bug fixed in Hub 4 or 5?
Does it exist in Hub 2.
I have the HH3A and use a laptop and printer wirelessly. I have never mucked about with any lease lengths etc and whenever the lappy and printer are turned on they connect to the internet/each other without me doing anything - i just launch firefox or just print away.
DHCP lease requested, my laptop was booted off the wireless network and had to rejoin. It happened to the MacBook Air about half an hour earlier. Even though the lease is set to 20 days the same will happen in 24 hours.
Time and date Message
|16:21:53, 27 Dec.||( 2123.140000) Admin login successful by 192.168.1.89 on HTTP|
|16:21:40, 27 Dec.||( 2110.160000) Lease for IP 192.168.1.89 renewed by host laptop (MAC 00:13:ce:db:53:7d). Lease duration: 28800 min|
|16:21:40, 27 Dec.||( 2110.160000) Device connected: Hostname: laptop IP: 192.168.1.89 MAC: 00:13:ce:db:53:7d Lease time: 28800 min. Link rate: 24.0 Mbps|
|16:21:40, 27 Dec.||( 2110.140000) Lease requested|
|16:21:40, 27 Dec.||ath0: STA 00:13:ce:db:53:7d IEEE 802.11: Client associated|
|16:20:12, 27 Dec.||ath0: STA 00:13:ce:db:53:7d IEEE 802.11: Client disassociated|
|16:07:22, 27 Dec.||( 1251.960000) Admin login successful by 192.168.1.89 on HTTP|
|16:06:18, 27 Dec.||( 1188.520000) OpenWiFi IPSec connection is down|
|15:58:34, 27 Dec.||IN: BLOCK  Remote administration (TCP [220.127.116.11]:46944->[18.104.22.168]:8080 on ppp0)|
|15:53:48, 27 Dec.|
IN: BLOCK  Remote administration (TCP [22.214.171.124]:37822->[126.96.36.199]:8080 on ppp0
I think the answer just shows that poster also has a hh3 and does not experience the problem as you describe. So does not seem to be a general bug
Never heard of that bug before. What evidence do you have that there is a bug in the software. The Homehub 3 has been out for years, why would it just start to be a problem now and only be reported by you? Surely if it was a bug more people, in fact everybody who used the HH3 would have a problem would they not?
I read on here a number of unresolved problems with loss of wireless connectivity to the HH3. My loss of connection always coincides with renewal of the DHCP leases, it affects Win7, MacOX, and Android, and this has been the case on two HH3s.
To quote you "How does that answer either question" that there is a bug in the software?
Do the "number of unresolved problems with loss of wireless connectivity" posters also report that it always coincides with renewal of the DHCP. Could it not be that the renewal is a symptom rather than the cause?
Glad to see you're getting closer to working out what the question is.
You should have been able to find this much faster than I have.
As it would appear that you just want to be sarcastic to anybody that posts on your thread I'll leave you to it.