Print

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

[sk00ter]

I've owned my DGL-4300 for about 4 years now and have never had issue until firmware version 1.8. When FW 1.8 was initially released, I had updated the router. I did not ever realize that D-Link had removed the FW (for security reasons still not specified). I have always made backups of my configuration files. My router never indicated a newer firmware version from the Tools|Firmware page; it only indicated that 1.8 was the latest.

A few weeks ago, I was noticing some general unresponsive issues with the router, so I would reboot the router and everything would be OK again. I went to the D-Link site and noticed that there had been a FW 1.9 released some time ago.

I downloaded the 1.9 firmware and attempted an upgrade, which failed. I then used a packet sniffer to debug while the FW file was being transferred and noticed that the router never sends an ACK to the first packet (of the FW upload) that it receives. This is followed by a few retransmits, then a RST on the connection. The router reboots and does not upgrade (obviously, since it did not transfer the FW image). I also attempted older FW versions (such as 1.7 and 1.6).

After this, I decided to reset the router to default settings (remove power while holding reset and re-apply power). This cleared all of my configuration settings, so I attempted another FW upgrade to version 1.9. Again, the router did not ACK the first packet and eventually the connection was RST. I decided to restore my configuration with my latest backup, and it also fails; the same issue with the router not sending an ACK after receiving the first packet. I tried various other configuration backups I had to no avail. It almost seems as if the router wants the firmware from TFTP (or it is just completely broke).

I am completely stuck, as I need to retrieve some of the configuration data, but I find that the file is encrypted and have not been able to figure out the encryption. I did find someone who had decrypted another D-Link router configuration file, but unfortunately it is not the same encryption (his was an XML file that was bit shifted).

My pleas/questions go out to anyone who can help:
1. How do I get the v1.9 firmware loaded onto the router?
2. How do I get my backup configuration loaded onto the router?
3. How do I decrypt/decode the backup configuration file?
4. How do I get D-Link to fix this issue (since they conveniently dropped support after breaking the product with their FW upgrade)?

05/07/2011:
I still need some help/answers with this. Preferably, someone who has knowledge/experience with the DGL-4300. Especially with #3 (and/or #4). Has anyone ever figured out how to decode the configuration file for the DGL-4300? Someone has done this for the DIR-628 (and some others), which uses a simple encrypted XML file (http://www.shulerent.com/2009/08/21/cracking-the-d-link-settings-file/)

[FurryNutz]

After doing the factory reset, were you able to set up the router and test it out or still experiencing the same problem? How are you connecting to the router? Always connect wired when doing FW updates.
I resommend setting up static IP reserved addresses on the router for all devices. Ensure DNS addresses are being auto filled in under Setup/Internet/Manual. Ensure DNS relay is ON. Disable Advanced DNS services if you have this option.

For FW updates:
Turn off any anti virus and firewall programs on the connected PC.
It's best to disconnect all other devices.
Try the following:
Factory reset of the router 1st.
Unpack and upload the .bin FW file. If you can get past the upload and get success.
Factory reset of the router once more.
At this point I would start from scratch and set up the router. Reason being that the saved config file could be corrupted and present unknown issues with the new FW. It's best to start from scratch, test and then save off to a new config.

Can you reload the same FW version, v1.8? Might have to reload that FW version, then try v1.9.

Config files can only be read by the router or by DLink themselves.

[sk00ter]

I am updating the firmware using a wired connection from a Linux host. There is no anti-virus or firewall.

As I described, I cannot get past the upload due to the router not sending an ACK to the first packet of the FW upload. I have already performed the factory reset which has caused me to lose my configuration settings.

I could easliy start from scratch and setup the router, but I need the old configuration data. It contains the various filters and routes I need for my work. Unfortunately, I trusted the backup configurations and the ability to reload them into the router.

I have tried version 1.6, 1.7, 1.8, and 1.9 FW and each of them exhibit the same behavior. I will attempt to detail the issue in a better way:
 1. Using the web admin, Tools|Firmware: choose FW file (*.bin), then click upload.
 2. The router receives the first packet from my host system, but does not respond with an ACK.
 3. The router receives a retransmit packet (the first packet again), but does not respond with an ACK.
 4. #3 repeats usually 2-3 more times.
 5. My host system receives a RST on the connection.
 6. The router has rebooted itself.
The same thing occurs when attempting to reload any of my previous config files.

The configuration files are nothing more than data (usually encrypted, and sometimes not). My question is in regard to retrieving the data from the config file. I am a network engineer by profession, and yes, my router is plugged in .

[FurryNutz]

Any chance you can try this on a Windows PC? Ya it should update on any PC. However trying to help narrow down the cause here. I presume that if a different PC is exhibiting the same thing, that the router probably has an issue here. I am a SW and HW developer by profession. Glad to know the router is plugged in. LOL.

[sk00ter]

Sure, I could try it from a Windows system, but what does that prove? I honestly don't think that will change the fact that the router is not sending an ACK (which seems to be the underlying problem) to the first packet received.

Network protocol must be observed, regardless of the operating system. All (most) TCP/IP packets must be ACK'd prior to receiving the next packet (I say most because you could have fragmentation). In other words, when my host machine sends the first packet of the firmware upgrade, the router simply does not respond (it acts as if it does not receive anything) and does not send an ACK. This is very different than if the router were to have received a malformed packet (or any other type of bad packet), because then it would reply with _something_. In this case, it does not reply at all, but it _should_ have provided an ACK to that first packet it received. Then, after my host waited (TCP packet timeout), it sent another packer (a retransmit). Again, the router acts as if it did not receive anything.

I will attempt from a Windows system this evening (I need to find a box to install XP on instead of doing through a VM), even though there is nothing in the packet that identifies what type of OS the host is running.

Anyone have any thoughts regarding the decrypting of the backup configuration files for the DGL-4300? I have started an attempt at decrypting by looking at the differences between 2 known configs. I start to make sense of it, then all of a sudden when I changed my known string from letters to numbers, the data changed in places where there were no previous differences.

[FurryNutz]

Understand man. I'm just check to see if there could be an issue with Linux, or even if Windows fails there too. Then you'll probably know fully that the router has a big issue. Just looking at the support site for this router, Not sure that you'll get any DLink support for it as it's seems to have gone into legacy mode. 

Specially if after doing a factory reset. It should take a FW Update.
I don't think these routers do a 30/30/30 reset either. Could try it.

Feelings on config file is probably proprietary to DLink the routers and how they are programmed. My 2 cents.

[sk00ter]

@FurryNutz:
Yup, D-link decided to drop support for this shortly after the v1.8 FW issue they created.
Don't get me wrong, I _DO_ appreciate your help. I would prefer if I could get the thing updated and replay my old config so that I can get the info that I need, at a minimum, I would like to retrieve the data from the config file. Amazingly, the router does still work (with some minor issues, such as I lost the ability to remote manage and the wireless output power is unstable).

Like I said, I will try the upgrade with Windows (but I need to find a box to use to install XP). I would have no problem getting a new router, but I _really_ need the config data. I will NEVER trust a product's backup implementation again!

[FurryNutz]

Keep us posted man. Let us know if you can get it to setup and load FW on windows.

You can trust product back and I do recommend using it. However I do agree that trying to get the data from the config files could be handled differently at least to let a user gather settings from it. Knowing this, I have resorted to screen captures. They work well. LOL.

[sk00ter]

So, as I expected, there was absolutely no difference when attempting to upgrade the firmware from a Windows box ( I'm still not even sure why I tried that... I guess I'm grasping at straws here  ).

Each time I reset the router, different things happen. At one point, the router would not change the password (I would change the password, then the router would prompt to reboot. Once the router came back, the new password did not work, but the default password did). Fortunately, this router is not on the WAN, so the password doesn't matter much.

Anyway, the same issue happens with the router. The host sends a packet, the router does not ACK the packet. The router will then reboot after a couple of seconds, and the host machine has no clue what is happening, so he is sending retransmit packets waiting for the router to respond. In the meantime, the router is booting up with the old firmware/config. This occurs when attempting to update firmware AND/OR reload an old configuration file.

@FurryNutz: Sorry, no trust there man. The purpose of a backup configuration file is to provide a backup when things go wrong, but when you cannot use the backup file when things _do_ go wrong, then there is no more trust. And, yes, screen captures do work. Unfortunately, I don't have any (since I trusted the backup configuration).

I do remember having some 60+ routes setup and I don't recall the number of filters and port forwards (pinholes). This is the data that I need back. I hope someone could either help with getting the data from the config file or point me to a place I could get a DGL-4300 on the cheap, so I could reload the config and get my data; then ditch this router forever.

I am really upset with the way D-Link played the DGL-4300. From what I have read, they released v1.8 FW, which caused numerous issues with this router, and subsequently removed the binary without explanation. Shortly after, they dropped support for the device (but D-Link is still supporting the older DGL-4100 router). This has completely turned me off to this company, especially for what was supposedly a "high-end" SOHO router.

[FurryNutz]

I can understand your frustration, however I disagree with the no trust on the back up. I would blame the back up process since this seems to be a HW issue. If the HW was working then you normally would be able to perform the back up and apply the settings normally. So the back process does work and should be used on all types of router systems regardless. Were all at the mercy of the HW and regardless of backups, HW can fail. Was there reason for updating FW? I always recommend NOT updating FW until all troubleshooting methods and been exhausted before updating.

I will ask Dlink if they can help you get the data off the config file. You might have to send me the file to relay to them. Might check out Ebay, Craigslist or Amazon for used 4300s.

[sk00ter]

Reason for attempting to update FW from 1.8 to 1.9:
 #1. The fact that D-Link removed the FW v1.8 from their own website and claim security issues.
 #2. Still have various connection issues in which I need to reboot the router in order to fix.

Reason for updating to FW 1.8 from 1.7 (2 years ago):
 #1. NAT filter issues.
 #2. Various stability issues on wireless connection.

You should really read up on the DGL-4300 product/firmware history... it is interesting. Already looked into ebay, craigslist, and amazon, thanks.

[FurryNutz]

Ok was curious. I've contacted Dlink on this issue and will let you know what I find out. Wish we could have found a fix for you. 

[sk00ter]

Thanks

[sk00ter]

Ok was curious. I've contacted Dlink on this issue and will let you know what I find out. Wish we could have found a fix for you. 

Anything from D-Link? Just curious, do you work for D-Link?

BTW, the wireless output died on the router after doing multiple (10+) resets when attempting to fix the password issue (the router would not retain/honor the new saved password). Now the password works but there is no wireless signal (regardless of the router settings). I guess I could try reseting again, but not really worth it. I was primarily using the wireless on the WRT54GL dues to the issues on the DGL-4300.

[FurryNutz]

I have asked. Waiting on response. Just in case they don't have one anymore, I would recommend searching for a back up option just in case.

No I don't work for DLink.