Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[scan80269]

As of this morning (Monday 9/10), the single client behind the 880L bridge running the new beta firmware has again lost its IP address lease and internet access.

I was unable to remote access this client yesterday from home, and today the client shows an autoconfiguration IP address of 169.254.100.34.

The "internet global" LED on the 880L panel is solidly lit, but the 5G radio LED blinks slowly.

This 880L bridge still responds to dlinkrouter.local and I can access the configuration pages, so it is not hung, but the attached client has been cut off from the internet.

Attempts to renew the IP address lease for the client using "ipconfig /renew" result in this message:

"An error occurred while reading interface Ethernet : unable to contact your DHCP server.  Request has timed out".

[FurryNutz]

Thanks for letting us know. Will have D-link review this. 

[GreenBay42]

I updated the ticket/dtrack.

[FurryNutz]

I guess revert back to v1.08WW for now if you need the 880L to work in Bridge mode. 

[GreenBay42]

Is there a way to test more than 1 client at the same time? I wonder if they drop at the same time or if it is random.

[scan80269]

I can add a second client behind the 880L bridge.

It appears a client gets dropped whenever its IP address lease expires and the auto-renewal fails.

I just got the client to regain a legit IP address, without power-cycling the 880L bridge:  I went into the 880L Wireless config page, clicked the Scan button and re-selected the same SSID.  The client received a 24-hour IP address lease and is back on the internet.  Also, "ipconfig /renew" works again.

[scan80269]

Second client has been added behind 880L bridge.  Will keep firmware at latest beta (from last week) for now.

I'll monitor both clients to see if they get cut off at the same time or individually based on their IP address lease expirations.

The first client IP lease will expire a few minutes past 11am tomorrow.  The second client IP lease will expire shortly before 1:30pm.  Will report back tomorrow.

[GreenBay42]

Thank you

[scan80269]

Both clients got their IP leases renewed at the 12 hour mark (not sure why, as the leases were for 24 hours), so their internet connections through the 880L bridge are still good as of this morning.  Also, 5G radio LED on the 880L is solidly lit.

Will keep both clients connected to this 880L bridge for continued monitoring.

[scan80269]

Update: both clients behind the 880L bridge still have their IP address leases, but their internet connections are down.

Both clients are still a number of hours away from their current IP address leases expiring.  This looks like the connection breakages can occur before the IP lease expires.

The 880L bridge still responds to "dlinkrouter.local", and the 5G radio LED is solidly lit.  Just no internet for the two clients. 

Apparently clients behind the 880L bridge get internet connections for a day or two then they are cut off.

Meanwhile, the two 868L bridges (running 1.12 firmware) connected to the same 5GHz SSID are working fine.  I'm continuing to monitor these.

[scan80269]

I have just reverted the 880L to 1.08B06 BETA firmware.  Should I roll back to 1.04B04 firmware instead?

[FurryNutz]

Let us know if B06 does the same time, hoping it doesn't. 

[scan80269]

Both clients got cut off behind the 880L bridge running 1.08B06 BETA firmware.  This time the internet connections didn't make it to the 12 hour mark.   

I'm rolling firmware back to 1.08WWb04.

[FurryNutz]

Sounds like the bug came in on B06 then...

[scan80269]

Both clients behind the 880L bridge running 1.08WWb04 firmware have successfully renewed their IP address leases twice, with continued internet access.

These clients have stayed connected to the internet longer then when the 880L was running 1.08B06 BETA or 1.20B01 BETA firmware.

It may be a bit too early to tell, but it is beginning to look like the issue came in starting with the 1.08B06 BETA (2/28/2018) firmware...