Print

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

[FurryNutz]

Sure doesn't show much. That's all in the syslog capture program?

[scan80269]

My thoughts exactly.  I didn't tweak any settings for the Kiwi syslog server.  Is that necessary?

[FurryNutz]

No idea. Maybe someone at D-Link can see if there are any other settings needed. Logs seems too sparse for any real information.

[FurryNutz]

Send me your email address in a PM. I found the syslog server app i got a few years back. I believe it might have better capture abilities.

[scan80269]

PM sent.  Since 2.4GHz seems to be working, I've reconfigured back to 5GHz and restarted the syslogging.

[FurryNutz]

Same here, 2.4Ghz is working well.

[scan80269]

The DHCP client behind the 880L bridge in 5GHz got its IP address lease renewed once.  Exactly one relevant message was captured into syslog:

DHCP: Client receive ACK from 192.168.1.1, IP=192.168.1.28, Lease time=86400

Previously, when a DHCP client got cut off from the internet, it was often at the 12-hour mark when the client attempted to renew its IP lease but got no response from the DHCP server.  No messages were captured into syslog for this failure, as far as I could tell.

Yesterday the 880L went into a mode where no syslog messages were being seen, so I rebooted the unit.  I thought it was because Windows got upgraded for the client running Kiwi syslog server, but it turned out to be the 880L not sending out syslog messages even when configured to do so.

[FurryNutz]

And all of this is while connected on 5Ghz?

The DHCP client behind the 880L bridge in 5GHz got its IP address lease renewed once.  Exactly one relevant message was captured into syslog:

DHCP: Client receive ACK from 192.168.1.1, IP=192.168.1.28, Lease time=86400

Previously, when a DHCP client got cut off from the internet, it was often at the 12-hour mark when the client attempted to renew its IP lease but got no response from the DHCP server.  No messages were captured into syslog for this failure, as far as I could tell.

Yesterday the 880L went into a mode where no syslog messages were being seen, so I rebooted the unit.  I thought it was because Windows got upgraded for the client running Kiwi syslog server, but it turned out to be the 880L not sending out syslog messages even when configured to do so.

[GreenBay42]

I updated the DTrack with this latest information.

Furry are you seeing any issues when bridging to your 890L?

[FurryNutz]

The 890L doesn't support bridging. Only AP mode.

My 880L is working fine on 2.4Ghz as of yesterday. I can't get it to connect or see the current 5Ghz router due to you know the bug found there. 

I updated the DTrack with this latest information.

Furry are you seeing any issues when bridging to your 890L?

[GreenBay42]

I know. You said you have the 880L bridging to the 890L in router or ap mode.

[FurryNutz]

The 880L is bridge to the COVR router on 2.4Ghz.
My 890L is in its box. 

[scan80269]

Yup!

I may have an opportunity to update the firmware for the Netgear router that my 880L bridges to over 5GHz.  Will see if that changes any behavior.

The 880L bridge has not failed over 5GHz since yesterday's reboot.  I'm still waiting for the failure to hit the connected clients.

And all of this is while connected on 5Ghz?

The DHCP client behind the 880L bridge in 5GHz got its IP address lease renewed once.  Exactly one relevant message was captured into syslog:

DHCP: Client receive ACK from 192.168.1.1, IP=192.168.1.28, Lease time=86400

Previously, when a DHCP client got cut off from the internet, it was often at the 12-hour mark when the client attempted to renew its IP lease but got no response from the DHCP server.  No messages were captured into syslog for this failure, as far as I could tell.

Yesterday the 880L went into a mode where no syslog messages were being seen, so I rebooted the unit.  I thought it was because Windows got upgraded for the client running Kiwi syslog server, but it turned out to be the 880L not sending out syslog messages even when configured to do so.

[scan80269]

This issue now looks like a 5GHz linkage failure between 880L bridge and the host wireless router (Netgear R8000), as opposed to a DHCP IP address renewal failure.  5GHz linkage breakdown explains all the symptoms seen on the clients attached to the 880L.

Unfortunately, neither this 880L bridge nor the host router can be relocated to be closer to each other.

I can look into giving the 880L bridge an IP address reservation in the Netgear router.  There are two DIR-868L (1.12B04_WW firmware) in bridge mode also linked to this router over 5GHz and clients attached to these 868L can access internet continuously.

Some time soon I'll need to roll the 880L firmware back to 1.08B04_WW to maintain internet access for connected clients, or move the clients to the 868L bridges.  In other words, my ability to assist with troubleshooting this 880L issue may be ending...

BTW, does the DIR-895L/R officially support bridge mode?  Just curious...

[FurryNutz]

Well my 880L was with in 20 feet almost line of site and I was able to reproduce that issue on 5Ghz. 2.4Ghz is still running fine.
Yes the 895L supports wireless bridging:
http://forums.dlink.com/index.php?topic=50738.0