Hi guys,
I hope that is the right forum for the DLINK DIR-615. I am not 100% sure. Don't hesitate to tell me if I am wrong here.
Due to lack of functionality of the DLINK firmware I flashed my DIR-615 router with the latest dd wrt firmware (thank you guys for that cool stuff!!!).
But I didn't do it that way:
1. 30/30/30 reset
2. hex edit the .bin-file?
(What exactly do I have to insert? I have read at http://www.dd-wrt.com/phpBB2/viewtopic.php?p=435276 that I have to insert my model number. Is that the MAC-ID?)
3. upload and flash .bin file
4. let it reboot
5. when dd-wrt gui is loaded do another 30/30/30 reset
I simply flashed it via the management interface to the device. Could that cause the error mentioned below?
My goal is to make my webserver accessible via the internet with it's DynDNS hostname.
First I set up static DHCP to ensure my webserver will always get the same IP (image 1 below).
After that I set up my router to work with DynDNS (image 2 below). After that my router was accessible with my DynDNS hostname from the LAN (port forwarding is not yet setup).
But unfortunately my webserver is not accesible from the internet. I only get the message "page not found". Besides port range forwarding I also tested port forwarding. But it doesn't work either.
Most people used "solved" when the problem is actually fixed. I just wouldn't consider going back to an older version a real "fix". I think the port forwarding is still a very valid issue without a current fix for the newer builds.
I put up a ticket but they closed it due to being a "duplicate" of some other issue (which I don't agree with) and no answer, so knows if and when we'll have a fix for the DIR615.
I put up a ticket but they closed it due to being a "duplicate" of some other issue (which I don't agree with) and no answer, so knows if and when we'll have a fix for the DIR615.
I was hoping you'd follow the breadcrumb trail from the original ticket to the post in the Broadcom forum but now I'll explain it a bit more directly. You should be able to still access all of your port forwards from the WAN side with recent builds because loopback itself is functional, but loopback functionality was removed so you can not access the port forward from inside your LAN. The original ticket now explains how you can fix it with iptables rules.
First you should test to make sure that your port forwards are accessible from the WAN side making sure to use the exact same settings from a "working build."
If it works then you should test the port forwards from inside your LAN which should fail. Then add iptables rules to your firewall script to fix loopback and retest to make sure that you can once again access the port forwards from within your LAN.
You should find that only loopback is broken and that the iptables rules fix it. If so then please spread the word more in the Ralink forum since I only occasionally come to this section. If not then I'll investigate further because I do have a WHR-G300N to test with. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
.
