Print

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

[peharri]

As I posted in the R15 thread, I'm having a recurring issue where my extender (but not my main R15) keeps crashing. I gave up as I hadn't heard anything, and got an E15 to see if that would be more reliable - I assumed the silence about the issue implied nobody else was having the same problem.

Unfortunately, no, the E15 is crashing regularly (every day or two) as well. In both cases the E15 and R15-extender are running the latest firmware update (E15 is running 1.04.04 from here:  https://support.dlink.com/resource/PRODUCTS/E15/REVA/FIRMWARE/E15_REVA_FIRMWARE_v1.04.04_HOTFIX.zip, and R15 from here: https://support.dlink.com/resource/PRODUCTS/R15/FIRMWARE/R15_REVA_FIRMWARE_v1.05.01_HOTFIX.zip); in both cases, after updating the firmware, I did a factory reset, before configuring them to join my network.

The device (whichever I use) has a fairly standard set up - there are a couple of devices plugged into the Ethernet port (a security camera and a Roku) but otherwise everything connects wirelessly, and it's just some regular laptops and mobile phones that are connected at the moment.

There is no pattern to the crashes. They've happened at 2 in the morning, and happen at lunchtime. This morning it crashed at about 6.30am, when the only thing using it was probably my laptop.

The crashes always follow the same pattern: the device stops responding to pings and stops routing traffic. Nothing is sent to the devices connected to indicate Wi-Fi is down. After 2-3 minutes the device has rebooted and starts responding to everything again.

Is this problem on D-Link's radar right now?

[FurryNutz]

What's the distance between the R15 and E15? 30 feet would be a good starting distance, depending on building materials.

What channels are you using on the R15?
Any wifi neighbors near by? What channels are they using?

Has a factory reset and setup from scratch been performed on either R or E unit since last FW update?

[peharri]

I think you've misunderstood. To be fair I did forget to mention I was using either extender in Mesh mode (with another R15.)

But the key point is that they're crashing. It is not about signal quality, it's about the E15, and R15 before it, spontaneously rebooting. Anything connected via them loses connectivity for 2-3 minutes, and if I ping the crashing device from my wired network, they're not available for the first minute or two. I haven't been able to watch the E15 when it crashed, but when I was using the R15 I was around to see it crash, with all lights turn off, one red light for a minute or two, and then the rest slowly come back.

(I did answer the other question you asked in the original post - yes, I did a factory reset after upgrading the firmware on both devices.)

This literally about newly set up E15s (and R15s in extender mode), linked in a mesh network with another R15, with the latest firmware, and factory reset, with defaults set, crashing every day or two. Not the network signal being poor, but actually rebooting.

[GreenBay42]

I haven't seen this issue much at all with the BETA firmware that has been released. We are still waiting for new official releases for both E15 and R15. Things to try to narrow down the issue:

Do you have a mix of newer and older clients?
What security are you using? WPA2/WPA3 mixed or only WPA2 personal?

I know an earlier glitch with the R15 was at 2am it would check for a firmware upgrade and when in mesh mode it would drop whatever it was connected to. That was fixed in 1.04.04. Does this issue happen when you downgrade the R15 firmware to 1.04.04? I wonder if the issue is with 1.05 on the R15.

[peharri]

I'm using WPA2 Personal. For the Extender R15, the crashes were happening under 1.04.01, 1.04.04, and the current 1.05.01. For the E15, I upgraded straight to 1.04.04 (and did a factory reset) before I put it in operation.  As far as I can see 1.04.04 is the latest firmware version for the E15.

The firmware on the Master/Router R15 is 1.04.04, I'd been holding off upgrading it., but if you think it might be telling the other mesh nodes to do firmware updates (at weird times, these crashes aren't happening at the same time each day) I can upgrade it. If it is doing firmware updates that's weird because... well, it isn't updating the firmware ;-) (I also have "Automatic upgrade" disabled FWIW.)

(As an aside, and completely unrelated to this issue, the Master Router R15 seems unsure as to whether the E15 is a mesh extender or not. It shows 0 extenders on the Home tab, but does show the "icon" for the extenders anyway. Click on that and it shows the E15 (and shows what's connected via the E15, so it is treating it as a mesh node, not merely a generic extender.). It was showing the Mesh Extender R15 when I was using that as an extender without issues. Likewise the firmware status screen did show the extender R15, but isn't showing the E15.  I did set them up differently, going into the web UI to set up the  Extender R15 while I used the WPS button to set up the E15. It's all a little odd.)

[davevt31]

We had issues during the testing of these, I don't remember exactly but the web interface wouldn't show the extender in MESH mode while the app did or the other way around.  I would go ahead and update to latest.

[peharri]

EDIT: A day later the E15 is suddenly appearing as the extender R15 did previously, so contrary to the below it does appear that the 1.05.01 firmware fixed that issue. Thanks! Now to figure out the more important one, why it's crashing...


Thanks, I upgraded to 1.05.01 on the Master R15 and alas it's still showing the E15 weirdly ("Extenders: 0" on the http://<routerip>/Home.html page but click on that and it shows it, and click on the E15's icon and it shows what's connected to it.) I'm wondering if the best approach might be to factory reset the E15 again and manually set it up (like I did with the Extender R15 which showed as a Mesh extender from the beginning)

Anyway not a critical issue, the crashing is the issue that I really want resolved and suspect D-Link does too as I assume it affects everyone. I've offered to send logs before from the master/router R15 when the mesh extender R15 crashed (I can't get the logs from the extender for obvious reasons) but haven't had a response. I still have them if they'd help.

[peharri]

So the current situation is... with the 1.05.04 firmware, only one apparent crash in a week of testing.  Upgraded to 1.05.05 on Saturday and it's too early to tell (but no crashes so far. So something is causing crashes still, but not as frequently, which is great!

[RickHarley]

Create the frontend of your app for both riders and drivers https://mlsdev.com/blog/how-to-outsource-web-development . This involves building the interfaces that users interact with. Make sure the design is consistent, responsive, and optimized for various devices. Mapping and Navigation Integration: Integrate mapping and navigation services to provide real-time tracking for both riders and drivers. Services like Google Maps or Mapbox can be useful for this purpose.