Print

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

[Hard Harry]

The more I think about it, the more I am certain it has something to do with local network not releasing use of private IPs. When you connect a device to a network, for example your DIR-615 router, that device pulls a IP from a block allocated by the router's DHCP server. Device 1 gets IP address 1, device 2 gets IP address 2, and so on, with 254 addresses. With a home router, it's not a issue, but few people have more than 200 devices connected to one router. But the router (or LAN) in your complex can easily have 250 devices connected over time. If the network never releases the IPs to be used for other devices, it eventually runs out. With a normal router like the DIR-615 you can release the IP by unplugging the power and plugging it back in. I wonder if the same thing can be done with the router in your apartment complex that you are getting the 10.x.x.x IP from. Ask your HOA to reboot that router. It's probably in a maintenance room somewhere, probably near the electrical circuit breaker or any room you have phone equipment. I'm hoping that will be the magic button fix we are looking for which will make the DIR-615 work automatically.

PS. Funny note, I think your ISP Parknet is related to Nianet, which is parent company to Zen Support, which I used their support page for OS emulators for years. I made them the norm for my support staff so much that the Denmark ISP banned our US IP's. We thought it was hilarious that another ISP across the world caught us with our hand in their support cookie jar. 

[Hard Harry]

Digging a bit more through the Parknet site I found this

"automatic configuration
You must put your computer (or router) to automatically obtain an IP address via DHCP. It is standard.
DNS servers
We recommend automatic configuration (standard). If you are not allowed to do so you can use these two addresses:
80.71.128.11
80.71.128.27"

Doesn't give us much, but that confirms the default DHCP should work and gives possible work around for DNS.

[Hard Harry]

I think what they do with static IP is assign the IP your device is already getting to only that device. So you plug in your router, get IP 10.x.x.1, so they assign 10.x.x.1 to the MAC address of that router. That pulls 10.x.x.1 from the DHCP rotation, making the IP's usable for DHCP even less. So if the complex has 254 IP's, and 200 residents, and 50 of them use static IPs, that only leaves 1.5 IP address to use per other user. With public IP, they assign a new 80.x.x.x IP to the apartment complex from a CIDR block and then configure your router as a hop in that circuit. So the public IP's come from a different block then the private IPs.

Something else to consider is the DIR-635 is NOT IPv6 compatible while the DIR-615 is. I wonder if the DIR-615 is then trying to make IPv6 work, which doesn't with your ISP, which is then breaking the internet. Make sure to disable IPv6 on the router by going to equivalent page on your DIR-615 and setting IPv6 to "Link-local only" and disabling IPv6 on your PC. See here for official methods of disabling IPv6.

[FurryNutz]

Might help if someone connected with this user via Teamviewer and had a look at this PC networking and the 615 to see what is going on. 

Hope maybe his ISP can help.

[mads920d]

Well, the TP Link works with zero problems both wired and through wireless. Hmm? Checked the DIR-615 after the TP Link just to be sure and still no success with it.

[FurryNutz]

You might try upgrading FW:
http://www.dlink.com/dk/da/support/product/dir-615-wireless-n-300-router?revision=deu_revd#downloads

I see v4.14 available for the Rev D version...

If you do please follow this to apply the FW update:
Link> >FW Update Process

[Hard Harry]

Can you show screenshots of the TP-Link and DIR-615 status screens? Either the two models have different default settings or something is physically broken with the DIR-615.

[mads920d]

TP Link status screen https://ibb.co/d3skmF

DIR-615 status screen from earlier page https://ibb.co/jRwpwF

Will try updating the firmware later.

[Hard Harry]

Updating firmware can't hurt, but I am befuddled about what is going on. Also try cloning the MAC address of the DIR-615, or even just changing it to anything but what it is (00:26:5a:x:x:x:x). If that doesn't work, I wonder if the router is malfunctioning somewhere at the firmware level.

Can you explain some more where you got the DIR-615 from? In OP you said you got it from your brother. Does your brother living in your apartment complex? Does he, or did he, also have Parknet for internet? I wonder if the D-link's MAC address is in there system somehow, attached to his account still, so won't allow access on your ethernet jack. A bit of a stretch for an explanation but it's all I can currently think of. TP-Link is also IPv6 compatible, unlike the DIR-635 so it rules that out as a issue too.

Did you still want to troubleshoot the issue or do you now just want to use the TP-Link router? Could I remote in now to look at the DIR-615 default settings and see if I can get it to work? Or have you email Parknet yet like they request? I don't think they would request you to contact them if they didn't think it was something they could fix. Not to say we might not also be able to fix it, it just might be easier for them. Please advise. :-)

[FurryNutz]

I've seen some ISP block routers due to being out of date on FW.
Also seen some MAC address issues in the FW that was old and just needed updating of FW.

I'd try the 615 at a different location, say friend or families place or maybe a neighbor. See if the 615 works with a different ISP service or modem.

I would update FW first though. 

[Hard Harry]

Can you show text or screenshot of logs from Status > Logs and Status > Statistics?  Make sure "debug activity" is checked and then reboot (turn off/on) the DIR-615. Trying to find out why the DIR-615 can't get DHCP to work while the TP-Link can. What does it say when you try to complete the DIR-615 connection wizard?

[Hard Harry]

What I find most relevant is the DIR-615 is getting a IP of 0.0.0.0. That means the DHCP server it is trying to contact is denying the request. I hope the WAN stats will show the packet activity and the logs will show the DHCP denial. I would think if DHCP was breaking (instead of being denied) it would get a invalid IP or give some kind of error at the internet wizard. This makes trying to change the DIR-615 WAN MAC address even more relevant.

PS. What does clicking on "DHCP Renew" do?

[FurryNutz]

He can test the 615 out by connecting the 615 WAN port to the TPLinks LAN port to see if it gets an IP address. He may need to first change the 615s router IP address from 192.168.0.1 to 192.168.1.1 or .2.1 as the TPlink may use the same .0.1 string. This would be a good quick test to try.

[Hard Harry]

"by connecting the 615 WAN port to the TPLinks LAN port to see if it gets an IP address. "

Very good idea. If it can connect to the TP-Link DHCP server but not the apartment complex (or Parknet's) DHCP server, then that pushes the fault back at them. Not that I am trying to point fingers, just isolate where the problem is so we can fix it.

Do you know if IPv4 will still connect if IPv6 fails? I noticed DIR-615 hardware version E1 has a firmware patch with firmware 5.01 that fixed IPv6 over DS-Lite, which I wonder is what Parknet uses for IPv6? The only thing I could find related was this. Doesn't tell much but looks like they added more IPv6 support sometime in July of 2016. Suggest again to disable IPv6 completely in IPv6 to completely rule out.

[FurryNutz]

Yes IPv4 should still connect. He's got a Rev D and not sure if this particular Rev had or has IPv6 features or supports it. If it does, the user needs to set Local Only for it. At least for now until he can get it going.

User needs to update FW as well.