Print

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

[Hard Harry]

Hmm, that's odd. Do you know why Hardware version D isn't listed on Dlink's support page? They seem to have every hardware version BUT D. Main difference seems to be D was Ralink CPU and didn't have USB. See link or text below.

Revisions   CPU   Ram   Flash   Network   Gigabit   USB   Serial   JTag
A1   Marvell   32MB   8MB   4x1   No   No   Yes   Yes
B2   Ubicom   8MB   2MB   4x1   No   No   Yes   Yes
C1, C2   Atheros   32MB   4MB   4x1   No   Yes*   Yes   No
D1 - D5   Ralink   32MB   4MB   4x1   No   No   Yes   No
E1, E2   Atheros   32MB   4MB   4x1   No   Yes*   Yes   Yes
E3,E4,E5   Atheros   32MB   4MB   4x1   No   Yes*   Yes   Yes
F1, F2   Realtek   16MB   2MB   4x1   No   No   Yes   Yes
G1   Ralink   32MB   8MB   4x1   No   No   Yes   ?
H1, H2   Ralink   32MB   4MB   4x1   No   No   Yes   Yes
I1 - I3   Atheros   32MB   4MB   4x1   No   No   Yes   Yes
J1   Realtek   16MB   2MB   4x1   No   No   Yes   Yes
K1   Broadcom   32MB   4MB   4x1   No   No   No   Yes
K2   Broadcom   32MB   4MB   4x1   No   Yes   Yes   ?
M1   Realtek   32MB   4MB   4x1   No   No   No   Yes
N1   Realtek   32MB   4MB   4x1   No   ?   Yes   No
Q2   Realtek   32MB   4MB   4x1   No   No   Yes   Yes

[FurryNutz]

Ya, I wish I knew. I had a hard time trying to keep up with all these different Revs. Each region with in D-Link does there own thing in development and marketing. Some regions don't market the same Rev models. I don't know. Same thing happened on the DIR-868L Rev B, sold in Canada and EU but not here in the USA where Rev A is. Rev B has the new UI, where the Rev A had the old.  Rev C of the same router was only marketed in China. 

Seen many revs with the 615. Been a low budget work horse around the work. I think I have a Rev C or E.

[Hard Harry]

One mini mystery solved. Looks like firmware for hardware version D is only available on Dlink's Danish support site. Wonder who "Michael Messner" is?  Could "http://<IP>/bsc_wlan.php" patch be relevant? Suggest upgrade. Release notes for latest firmware are


 D-Link Corporation confidential

 DIR-615Firmware Release Notes
Firmware:FW414B04
Hardware: Dx
Date:2013/10/29
Note:
1. FW version is advanced to v4.14

Problems Resolved:
1. Fixed the UPnP exploit.
2. Fixed thereported issue from Michael Messner

 OS Command Execution:

http://<IP>/tools_vct.xgi
http://<IP>/tools_system.xgi
 Cross-Site Scripting (XSS)

http://<IP>/bsc_wlan.php
http://<IP>/tools_log_setting.php
 Security Misconfiguration

Telnet Service is open with Authentication.
 Sensitive Data Exposure

http://<IP>IP/DevInfo.txt
 Cross-Site Request Forgery

http://<IP>/tools_admin.php
Enhancements:
None
Known Issues:
None

[FurryNutz]

Why I suggested it earlier. 

Regarding Messner:
http://www.s3cur1ty.de/node/672

[Hard Harry]

I know you did, and I agreed it's a good idea and OP said they will try it, but my gut is telling me firmware won't fix it. It's more something we are doing to rule it out as a possible issue. I am wondering if the factory reset function(broken button?) isn't working correctly and some settings are still left over from OP's brother. Suggest factory resetting using the soft button in the DIR-615 Tools > System as seen here.. Other than that, trying to connect the Dlink to the TP-Link's LAN will show for sure if it's DHCP server is working correctly. If it does, I strongly think MAC cloning will be the primary solution.

[mads920d]

Will do all this stuff within the hour hopefully.

[Hard Harry]

Why I suggested it earlier. 

Regarding Messner:
http://www.s3cur1ty.de/node/672

Watch out those eyes don't roll TOO hard. 

[Hard Harry]

Will do all this stuff within the hour hopefully.

Great! Sorry if it seems like we are troubleshooting without you. Just helps for us to brainstorm. Thanks for working with us. 

[FurryNutz]

Doing a factory reset(UI), loading FW and doing another factory reset(UI) will ensure any old configurations are completely gone.

I know you did, and I agreed it's a good idea and OP said they will try it, but my gut is telling me firmware won't fix it. It's more something we are doing to rule it out as a possible issue. I am wondering if the factory reset function(broken button?) isn't working correctly and some settings are still left over from OP's brother. Suggest factory resetting using the soft button in the DIR-615 Tools > System as seen here.. Other than that, trying to connect the Dlink to the TP-Link's LAN will show for sure if it's DHCP server is working correctly. If it does, I strongly think MAC cloning will be the primary solution.

[mads920d]

Well, since only the green ethernet jack gives internet (just tested, neither router works in the red one), that means I can only have one router connected at a time. I'm only able to reach the DIR-615's page while connected to it, but that means having no internet access - thus my attempt at updating the firmware has failed, as it needs a wired connection. Likewise, when using the internet setup wizard for the DIR-615, it works until the end, when you're supposed to save the settings - because of the lack of internet access, it attempts to load but ends up loading a browser page saying the connection timed out or something, but the settings are still saved after that (if that makes sense). No way to access the DIR-615 page while connected to the TP Link?

Logs from the DIR-615:

Jan 1 00:12:22   DHCP: Client send DISCOVER.
Jan 1 00:12:18   DHCP: Client send DISCOVER.
Jan 1 00:12:16   DHCP: Client send DISCOVER.
Jan 1 00:12:02   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:12:02   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:11:32   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:11:32   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:11:02   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:11:02   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:10:32   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:10:32   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:10:02   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:10:02   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:09:33   DHCP: Server sending ACK to 192.168.0.101. (Lease time = 60)
Jan 1 00:09:33   DHCP: Server receive REQUEST from f8:a9:63:88:a2:82.
Jan 1 00:09:33   DHCP: Server sending OFFER of 192.168.0.101.
Jan 1 00:09:33   DHCP: Server receive DISCOVER from f8:a9:63:88:a2:82.
Jan 1 00:09:24   DHCP: Server sending OFFER of 192.168.0.101.
Jan 1 00:09:24   DHCP: Server receive DISCOVER from f8:a9:63:88:a2:82.
Jan 1 00:09:23   DHCP: Server sending OFFER of 192.168.0.101.
Jan 1 00:09:21   DHCP: Server receive DISCOVER from f8:a9:63:88:a2:82.
Jan 1 00:09:08   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:09:08   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:08:38   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:08:38   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:08:09   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:08:09   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:08:09   DHCP: Server sending OFFER of 192.168.0.100.
Jan 1 00:08:09   DHCP: Server receive DISCOVER from ec:08:6b:19:8f:46.
Jan 1 00:06:44   DHCP: Client send DISCOVER.
Jan 1 00:06:28   DHCP: Client send DISCOVER.
Jan 1 00:06:20   DHCP: Client send DISCOVER.
Jan 1 00:06:16   DHCP: Client send DISCOVER.
Jan 1 00:06:14   DHCP: Client send DISCOVER.
Jan 1 00:03:41   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:03:41   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:03:11   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:03:11   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:02:40   DHCP: Server sending ACK to 192.168.0.100. (Lease time = 60)
Jan 1 00:02:40   DHCP: Server receive REQUEST from ec:08:6b:19:8f:46.
Jan 1 00:02:40   DHCP: Server sending OFFER of 192.168.0.100.
Jan 1 00:02:38   DHCP: Server receive DISCOVER from ec:08:6b:19:8f:46.
Jan 1 00:00:42   DHCP: Client send DISCOVER.
Jan 1 00:00:26   DHCP: Client send DISCOVER.
Jan 1 00:00:18   DHCP: Client send DISCOVER.
Jan 1 00:00:14   DHCP: Client send DISCOVER.
Jan 1 00:00:12   DHCP: Client send DISCOVER.
Jan 1 00:00:07   VPN (L2TP) Pass-Through enabled.
Jan 1 00:00:07   VPN (IPSec) Pass-Through enabled.
Jan 1 00:00:07   VPN (PPTP) Pass-Through enabled.
Jan 1 00:00:07   Domain blocking disabled.
Jan 1 00:00:07   URL blocking disabled.
Jan 1 00:00:07   MAC filter disabled.
Jan 1 00:00:04   System started.

    Receive   Transmit
Internet 0 Packets   0 Packets
LAN    5745 Packets   1315 Packets
WIRELESS 11n   20217 Packets   1421 Packets

[FurryNutz]

What is the GATEWAY IP address for the TPLink router when you connected here?
You can download the FW update file to your PC first when your connected to the TPLink router. Then connect to the 615 to get it updated.

I would change the 615 to 192.168.2.1. You don't need the 615 to be connected to the internet to get to the routers web page. If you can get to 192.168.0.1 first with the PC and teh 615 alone, then change it to 192.168.2.1 then save settings and reboot, then exit the browser after the router reboots then open a browser again, now access the routers web page at 192.168.2.1. Your PCs IP address will be 192.168.2.something. Use a wired lan cable connection between the 615 and PC first. Don't connect the WAN port of the 615 to anything.

[mads920d]

What is the GATEWAY IP address for the TPLink router?
I would change the 615 to 192.168.2.1. You don't need the 615 to be connected to the internet to get to the routers web page. If you can get to 192.168.0.1 first with the PC and teh 615 alone, then change it to 192.168.2.1 then save settings and reboot, then exit the browser after the router reboots then open a browser again, now access the routers web page at 192.168.2.1. Your PCs IP address will be 192.168.2.something.

You mean the address to access its page? 192.168.0.1. Just changed the DIR-615 to 192.168.0.2 but can't connect to it while connected to the TP Link
Edit: nevermind figured it out, trying to update firmware as we speak. Not connecting the DIR-615's WAN made me able to access its page.

[FurryNutz]

Ok, that won't work. Change the 615s router IP address to 192.168.2.1 for now.

What is the GATEWAY IP address for the TPLink router?
I would change the 615 to 192.168.2.1. You don't need the 615 to be connected to the internet to get to the routers web page. If you can get to 192.168.0.1 first with the PC and teh 615 alone, then change it to 192.168.2.1 then save settings and reboot, then exit the browser after the router reboots then open a browser again, now access the routers web page at 192.168.2.1. Your PCs IP address will be 192.168.2.something.

You mean the address to access its page? 192.168.0.1. Just changed the DIR-615 to 192.168.0.2 but can't connect to it while connected to the TP Link

[FurryNutz]

Ok, after you do the factory reset after the FW loads, the router will be back to 192.168.0.1. Log back in and change it back to 192.168.2.1, save settings then reboot. Your PC will have a new IP address 192.168.2.something and you should be able to access the routers UI at 192.168.2.1. Exit and re-start the browser after saving settings.

If you can get to the UI from this point, then connect the 615s WAN port to the TPlinks LAN port. Then look at the 615s Status page and it should get a 192.168.0.something address.

[mads920d]

Ok, after you do the factory reset after the FW loads, the router will be back to 192.168.0.1. Log back in and change it back to 192.168.2.1, save settings then reboot. Your PC will have a new IP address 192.168.2.something and you should be able to access the routers UI at 192.168.2.1. Exit and re-start the browser after saving settings.

If you can get to the UI from this point, then connect the 615s WAN port to the TPlinks LAN port. Then look at the 615s Status page and it should get a 192.168.0.something address.

Done all the resetting and all that. While the TP Link is plugged into the wall and the DIR-615 connected to my PC, I plug a cable from the DIR-615's WAN to the TP Link's LAN, right? The IP address under ''internet'' on the status page is 192.168.0.101 - regardless if the DIR-615 is connected to the TP Link or not.