D-Link Forums
D-Link Wireless Routers for Home and Small Business => DIR-3060 => Topic started by: kp9928 on March 02, 2020, 08:58:23 PM
-
Hi there, just bought a new DIR-3060...
Story goes like this, my ISP in malaysia provides a generic DIR-842. They hardcode some really SSID suffix to the wireless SSID and I can't flash it somehow even resetting it doesn't help - so I went out and got a DIR-882. The DIR-882 i believe is faulty, as it constantly disconnects from the pppoe connectivity like 3-5 mins after its on. There's something wrong with the router I believe. The DIR-842 is *rock solid* - 24/7 no issue, no reboot, but the SSID suffix thing is difficult to work with as i have a lot of wifi stuff that is difficult to re-program to attach to new SSIDs. Believe me I tried cables, reboots, flash different firmwares, no dice. The DIR-882 is either faulty or really bad or something.
Fast forward to today, after being frustrated with the DIR-882, I went out and got a DIR-3060. The PPPoE connectivity held, MOSTLY. However I'm still seeing a self-reboot happening a day or so...roughly every day there's 1 or 2 reboots. I want to know - is there a way I can find out why the router is rebooting? The DIR-842 is such an amazing rock solid router, the DIR-882 just plain out died on me Im gonna return it for replacement, I had hopes for the DIR-3060 ... its not bad but this random reboots is driving me nuts. I'm running the latest 1.02 fw, hw revision A1... no special features turned on... not even the SPI. 4 static port forwarding.
Any help would be much appreciated!!
-
What modem are you using? Make sure you reboot the modem (remove battery backup if it has one for 1 minute).
If you go to Management > System Log, you can either download the txt log file and see if you can see the reboot there or set up a syslog server.
Manual - pages 103-104 - https://www.dlink.com.br/wp-content/uploads/2019/06/EXO_Manual_v1.00WW.pdf (https://www.dlink.com.br/wp-content/uploads/2019/06/EXO_Manual_v1.00WW.pdf)
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=49573.0)
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interference's?
- Any other WiFi routers in the area that maybe causing interference's? Link> Use a WiFi Scanner (http://forums.dlink.com/index.php?topic=48327.0) to find out. How many?
Check the 882's power supply. Could be faulty. Hope replacement 882 works better though.
-
Firmware is 1.02
No other 2.4ghz/5ghz house phones or wifi - I'm connected via LAN by the way
There are other wifi routers in the area - but again i'm connected via LAN and its still rebooting.
The modem is a Huawei GPON HG82450H5
Regarding the 882 - you reckon its a power supply issue? It seems like there's trouble passing the packet from the LAN to WAN side .. pinging the router local lan interface is fine, pinging the internet gets wonky after 5 mins.. packet loss slowly increase from a few to many then to completely timing out and the router just dies after that.
For the 3060... I did enable logging now and I am seeing a constant repeat of ... this.... whats causing it ???
(and yes, i did factory reset after i upgrade the firmware)
03-04-2020 12:10:36 User.Warning 192.168.1.1 Mar 4 12:10:37 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:36 User.Warning 192.168.1.1 Mar 4 12:10:37 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:35 User.Warning 192.168.1.1 Mar 4 12:10:36 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:34 User.Warning 192.168.1.1 Mar 4 12:10:35 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:33 User.Warning 192.168.1.1 Mar 4 12:10:34 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:30 User.Warning 192.168.1.1 Mar 4 12:10:31 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:30 User.Warning 192.168.1.1 Mar 4 12:10:31 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:29 User.Warning 192.168.1.1 Mar 4 12:10:30 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:28 User.Warning 192.168.1.1 Mar 4 12:10:29 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:27 User.Warning 192.168.1.1 Mar 4 12:10:28 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:24 User.Warning 192.168.1.1 Mar 4 12:10:25 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:24 User.Warning 192.168.1.1 Mar 4 12:10:25 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:23 User.Warning 192.168.1.1 Mar 4 12:10:24 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:22 User.Warning 192.168.1.1 Mar 4 12:10:23 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:21 User.Warning 192.168.1.1 Mar 4 12:10:22 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:18 User.Warning 192.168.1.1 Mar 4 12:10:19 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:18 User.Warning 192.168.1.1 Mar 4 12:10:19 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:17 User.Warning 192.168.1.1 Mar 4 12:10:18 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:16 User.Warning 192.168.1.1 Mar 4 12:10:17 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:15 User.Warning 192.168.1.1 Mar 4 12:10:16 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:12 User.Warning 192.168.1.1 Mar 4 12:10:13 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
-
Well, your GPON has a built in router and wifi already. Has this been bridged and wifi disabled?
- If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT (http://www.practicallynetworked.com/networking/fixing_double_nat.htm) and How NAT Works (http://computer.howstuffworks.com/nat.htm). Call the ISP and ask to see if the ISP modem can be bridged. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ (http://www.dslreports.com/shownews/Networking-101-The-DMZ-137550). Disable ALL WiFi radios on the modem. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address of 192.168.0.1. Check to see if this is the same on the ISP modem, and if modem can't be bridged, change the DIR router to 192.168.1.1 or .0.254.
Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on a Router (http://forums.dlink.com/index.php?topic=56344.msg219023#msg219023)
Might find a newer power supply for the 882 and see. One user just posted he was having problems with his 882, however his came with a sub standard non OEM power supply. Once he got the correct PS, his started working. Worth a try. Might ask D-Link about an RMA if you feel the 882 is faulty though.
-
The GPON unit wifi is disabled - yes. The router functionality is disabled. And yes I'm using it in bridge mode, connecting the router to the modem.
So the 3060 rebooted itself 4 times today, seems to be getting worse.
The syslog showed nothing different.. the last few messages is the same as what I posted prior. This can't possibly be yet another faulty purchase can it ??...
For the time being I swapped back to the 842 and again it is *rock solid* so far... :(
Two dlink purchases, two disappointments :( Anything else I could do ?
The ONLY reason I haven't switch to other routers yet is because i love the QuickVPN functionality.
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. Ask about an RMA for both.
Link> Tech Support Contact Information (http://forums.dlink.com/index.php?board=635.0)
We find that phone contact has better immediate results over using email.
Let us know how it goes please.
-
I have to keep the 3060 for the time being even though its rebooting itself once :(
I can't keep using the 842 due to the silly ssid suffix my ISP added. Had I known the 882/3060 would be so problematic i would have opted for a store-bought 842 instead..
Looks like I will have to RMA them one at a time, and my other problem is that these routers are being used at a place 300km from the city center where I can do the actual physical RMA. This is beyond frustrating :(
Btw just off topic - the 882 works fine when i use it purely as a wifi AP connected to the 842(router)... could this still be related to power adapter on the 882? It would be surprising if it was..
-
My adventures with the 3060 continues...
Yesterday after a recent amount of reboots that got 'stuck'.. I begin to worry. Previously the reboot that happened the router returned back to its connected state. Yesterday a series of reboot caused the router to remain 'stuck' and inoperable. I had to manually power cycle the device. I also tried to check if its a heat issue by putting a giant fan underneath it - no dice, the router still reboots itself.
Today I decided to downgrade the firmware to 1.01 and factory reset again from scratch - only to be greeted with a message box "forcing" me to upgrade. Luckily I was able to circumvent this and go to my settings via some direct URL to configure some syslog and system changes - the "dnssd_clientstub" error remains and continues to flood the syslog server endlessly. not sure if this is an issue.
At this point I'm thinking of going to get a different brand of router or going to buy a store version of 842 where i can manually configure my own ssid....
(the isp provided me a 842 with a custom 3.01TM firmware which I tried to put the router into recovery mode but seems like its not working - 192.168.0.1 returns nothing even though the power LED blinks, seems like my ISP may have jacked up this unit to make it impossible for people to flash other official firmware)
Edit : 4+ hours in and stable so far.. hoping this firmware holds....
Edit : Moments after I type that .. it rebooted. Sigh.. guess I'm returning both 882 and 3060...
-
Seems like this units are faulty. Need to be returned or RMAd.
Good luck.
-
Sounds like some incompatibility with the modem. I had a similar issue with multiple routers (from same vendor/chipset family) rebooting randomly, ISP techs at my house a lot. I bought a different modem and it has been solid since.
Did you contact tech support? If you do not want to call at least send an email, refer them to this forum thread and cut n paste the log errors. Also give them the exact modem model number and ISP info. They can open a ticket with the engineers (d-track).
I do have a BETA firmware that fixed an issue with Guest network but it jumps from version 1.02 to 1.11. I requested complete release notes to see what else they fixed. If you want to try it, download here --> ftp://FTP2.DLINK.COM/PRODUCTS/DIR-3060-US/REVA/FIRMWARE/DIR3060A1_FWV111B02_Beta_for_Guest_zone_connect_issue_20200119%280119115953%29%280120145544%29.bin (ftp://FTP2.DLINK.COM/PRODUCTS/DIR-3060-US/REVA/FIRMWARE/DIR3060A1_FWV111B02_Beta_for_Guest_zone_connect_issue_20200119%280119115953%29%280120145544%29.bin)
After you upgrade, your router will request you to upgrade the firmware back to 1.02, just ignore or turn off auto update.
-
So I got a total replacement unit back from the local distributor. They totally replaced my unit.
Plugged it in - its been running for a day+ now.
A thing about the router upgrade is that - if an upgrade is available, there's no way to bypass or ignore the upgrade - I can't get to my settings and stuff if i don't upgrade? So it sorta forced me to go to 1.11 now - and I can't find any release notes of it anywhere! It was doing fine yesterday but since I upgraded to 1.11, I have had one instance of disconnect in the last 10 mins and some minor 1-2 packet loss (which my previous dlink totally did not have) - I hope it doesn't continue to be like this.. fingers crossed its just a one time thing. I even got a fan blowing underneath it this time just in case it was getting too hot. This unit does run rather warm!
I got another unit of the DIR-882 at the standby just in case.
Update : with 1.11 ... im still seeing these errors in the logs
I reached out to dlink support before - but they just tell me "oh just send it back to the local distributor they'll replace it for ya".. i gave them *all* the detail and info the last time i reached out to them but it seems like they just went with the fast track route to get my unit replaced... not that I'm not appreciative of it getting replaced but .. do they have an engineer looking at these issues??...
2020-06-18 14:46:06 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:09 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:10 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:11 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:12 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:12 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:15 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:16 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:17 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:18 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:18 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:21 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:22 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:23 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:24 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:24 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:27 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:28 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:29 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:30 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:30 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:33 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:34 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:35 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:36 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:36 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:39 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:40 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:41 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:42 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:42 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:45 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:46 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:47 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:48 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:48 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:51 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:52 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:53 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:46:54 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
2020-06-18 14:46:54 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-06-18 14:46:57 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-06-18 14:46:58 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-06-18 14:46:59 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-06-18 14:47:00 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
-
I would reach out one more time to D-Link support. Try Chat support. I would include this thread about these logs events you're seeing. Try to point them to the log post. Let us know how it goes.
-
Having similar issues with my router and have reached out to tech support multiple times, have had my router replaced as well, but it hasn't solved the problem. Sorry to say but it seems like D-Link has no clue what these syslog errors mean and why they are getting logged.
-
Any progress on this?
Firmware is 1.02
No other 2.4ghz/5ghz house phones or wifi - I'm connected via LAN by the way
There are other wifi routers in the area - but again i'm connected via LAN and its still rebooting.
The modem is a Huawei GPON HG82450H5
Regarding the 882 - you reckon its a power supply issue? It seems like there's trouble passing the packet from the LAN to WAN side .. pinging the router local lan interface is fine, pinging the internet gets wonky after 5 mins.. packet loss slowly increase from a few to many then to completely timing out and the router just dies after that.
For the 3060... I did enable logging now and I am seeing a constant repeat of ... this.... whats causing it ???
(and yes, i did factory reset after i upgrade the firmware)
03-04-2020 12:10:36 User.Warning 192.168.1.1 Mar 4 12:10:37 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:36 User.Warning 192.168.1.1 Mar 4 12:10:37 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:35 User.Warning 192.168.1.1 Mar 4 12:10:36 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:34 User.Warning 192.168.1.1 Mar 4 12:10:35 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:33 User.Warning 192.168.1.1 Mar 4 12:10:34 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:30 User.Warning 192.168.1.1 Mar 4 12:10:31 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:30 User.Warning 192.168.1.1 Mar 4 12:10:31 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:29 User.Warning 192.168.1.1 Mar 4 12:10:30 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:28 User.Warning 192.168.1.1 Mar 4 12:10:29 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:27 User.Warning 192.168.1.1 Mar 4 12:10:28 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:24 User.Warning 192.168.1.1 Mar 4 12:10:25 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:24 User.Warning 192.168.1.1 Mar 4 12:10:25 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:23 User.Warning 192.168.1.1 Mar 4 12:10:24 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:22 User.Warning 192.168.1.1 Mar 4 12:10:23 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:21 User.Warning 192.168.1.1 Mar 4 12:10:22 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:18 User.Warning 192.168.1.1 Mar 4 12:10:19 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
03-04-2020 12:10:18 User.Warning 192.168.1.1 Mar 4 12:10:19 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:33 Err:-1 Errno:0 Success
03-04-2020 12:10:17 User.Warning 192.168.1.1 Mar 4 12:10:18 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
03-04-2020 12:10:16 User.Warning 192.168.1.1 Mar 4 12:10:17 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
03-04-2020 12:10:15 User.Warning 192.168.1.1 Mar 4 12:10:16 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
03-04-2020 12:10:12 User.Warning 192.168.1.1 Mar 4 12:10:13 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
-
Ok, so I took a dive into this with my 2680. Though I do have the 3060 model router. I'm seeing the same thing. Just had 1 wired PC and wireless was disabled. Even tried with just 1 browser and tab open to the routers web page. Rebooted and these entries continue soon after the router is back to ready. I got with on online chat support and got a bit more steps to try. I disconnected the router from ISP services and rebooted the router. After giving 3-5 minutes, these log entries are NOT seen. Only 5 lines are seen. One the modem services was re-connected, the log entries began again. Support feels this is a router/FW side issue.
So they would like me and any other users experiencing this, to send support@dlink.com an email with all your information, troubleshooting steps, FW version loaded and anything else you think would help them review this more. Include any other D-Link routers that you may have and tried to compare. Also ISP service and modem mfr and model would be helpful as well. Send this off in a email and let see if we can get D-link to take a look and make a correction regarding this.
Other than this, the router seems to work ok. If users are experiencing other problems that I don't see, please include that as well.
-
Here is what I got from D-Link support about these log entries:
"Date of Reply: 8/10/2020 2:54:17 PM
Products: DIR-2680-US
I have been told that it is just some debugging info that is leaked into the syslog that will be removed in the next firmware release. It is nothing to be concerned about. "
-
Sorry to reply a couple months late.
I finally got it running stable - how? Putting a fan underneath the unit. I suspect heat is an issue with this unit running in tropical countries like mine (eg. Malaysia) . Everytime the fan is off, the unit would start to drop packets, and after awhile reboots itself. So I manage to get it running stable by putting a usb fan underneath. However this is not what I wanted :( If you guys are having it reboot and drop packets and stuff, I Would love it if you guys try and put a fan underneath it to keep it cool or something and let me/us? know the result if it runs better.
I love the QuickVPN feature of Dlink routers which I simply can't find in any other routers thus far. I only wish it did not heat up so quickly that it requires moving parts like a fan to use. :( Previously was using DIR-842 and that one was great in terms of heat management.
-
You might contact D-Link support for your region and let them know this. The router should run well however if your in a tropical region where there is more heat and humidity, these could be impacting any router though seems like the 3060 maybe more vulnerable. Glad the fan under the router helps. I've always kept a fan under my routers. Seems to help extend life as well. Heat will slowly degrade electronics over time. :-\
-
Came to check if there's any new firmware but ... saw the EOL announcement.
Can't believe this router launched in June 2020 .. is now EOL on the website. 1 year????... unbelievable Dlink!!....
-
Actually launch in June 2019. Still seems kinda short though. Free support for this product will end on 12/29/2021
FW update was 3 months ago...
-
This router launched March 2019 but I agree they discontinued this line of routers pretty quick. I am not sure exactly why it was discontinued after under 2 years but (happens with other companies) could be due to vendor issues, vendor-manufacture relationship, vendor closing, chipset shortage/price, inventory issues or flat out sales are low (business decision). Again I do not know why this router line got discontinued but these are reasons products go bye bye.
-
Found another issue with the router today. If you run a lot of connections eg. torrents - after awhile the router kinda limits your local network peer to peer connectivity - kinda like a guest mode wifi where you cannot talk to any other equipment on your LAN... until you reboot.
What's a good replacement router these days that don't overheat and reboot itself and don't have all these funny little issues... ? I run a Linksys velop mesh in another house and that one has been flawless for me for 3 years running.
-
I like D-Link LX1870. Works well and scalable too. Price even dropped too. I bought two earlier this year.
One thing I do and recommend, get a laptop cooler for your router. Any router I put online has a laptop cooler running 24/7. Helps with heat and extends life as heat will degrade electronics over time.
-
Found yet another quirk - after running for awhile, the router would stop giving out DHCP addresses, I only have a few devices. After rebooting - my devices would be able to get IP again. Sigh.. its getting worse.
I'll look at this LX1870. Thanks furryNutz!
One thing I do prefer though not to use a laptop cooler - I'm running one now for this DIR3060 and its just a dust magnet... after awhile below the cooler is an accumulation of tons of dust. Still, the main reason I buy Dlink routers is for the QuickVPN where I can quickly establish L2TP with it from my ios devices.
-
- Was a Factory Reset performed before and after any firmware updates then set up from scratch?
Link> >FW Update Process (http://forums.dlink.com/index.php?topic=42457.0)
Just have to keep the cooler vacuumed out is all.
-
Yup factory reset performed multiple times.
Anyway, if i can avoid taking out the vacuum that would be a plus. Anyhow, I tested some asus vpn router server so maybe I'll go that route and see how it goes.
Thanks for all the support here
-
;)