D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: Woogie on August 15, 2008, 08:50:24 AM
-
I would like to create a route to a machine on my network - my 2Wire gadget from ATT internet services. I have the 2Wire set up to pass all data on to my DGL-4500. The 2Wire is on a different IP structure, and is connected via my WAN interface.
In firmware 1.03, I could easily do this by specifying the destination IP, a netmask, and a gateway of 0.0.0.0 (per the help item in the DGL-4500 help).
In firmware 1.12, if I try to create this exact same route, I get an error message telling me that I cannot create a route on the WAN interface without a gateway. Specifically it says "The route for 192.168.1.254 on interface INTERNET may not be created - only routes via gateways may be created on this interface"
This is a regression compared to 1.03 (in which it worked beautifully). How am I supposed to do this now? Further, the DGL-4500 help does not indicate a change in the requirements for the route - quite the opposite - the help indicates that the above is perfectly acceptable.
Please help.
-
DON"T INSTALL 1.12 if you need functionality like the above post!!!!
D-Link tech support has informed me that this is a known issue in 1.12, and will be removing that firmware from being downloaded. Currently 1.20 is in the works.
They are supposedly shipping me a new router.....
-
Another little nugget.....
IF you install 1.12, you WILL NOT be able to install 1.20, according to technical support.
Basically, if you install 1.12, you are looking at a bunch of time spent on the telephone and an RMA.
Recommend you DON"T DO IT!!!
-
After trying the betas and not getting burned and having problems with my DWA-160s (A&B). I flash to a supported 1.12 and now hosed?
Can one of the mods verify this? Can I be put on the waiting list for RMAs?
Version 1.12 is still on the web and ftp sites.
-
I'd like some confirmation too...I'm not all that hot on trading in my brand new router for a refurb. If I can upgrade to 1.20 and all is well then that's much better for me.
All I'm doing is passing along what I've been told by technical support - who was supposedly in touch with a 2nd tier tech and a technical manager.
-
First there is no 1.20 for the 4500. Second, thats FAR from a known issue. Can you please PM me the name of the technician that gave you this information?
-
First there is no 1.20 for the 4500. Second, thats FAR from a known issue. Can you please PM me the name of the technician that gave you this information?
PM Sent
-
Lycan,
I sent you another PM....could you please confirm what you say above is correct or not?
I need to know the right answer so that I can determine whether or not to keep my router or the RMA one....
Thanks.
-
We're working to come up with a test scenerio. Please be patient as we are very busy.
-
OK - are you referring to the firmware upgradability or my routing issue?
I figured out a way to create the route I needed in Windows, so the route issue isn't that critical. I just want to make sure that my router is OK w.r.t. upgrading to future firmware releases.
-
As far as we know, other then the XboX issue i'm looking at that code should be good.
-
OK, so I will just return the RMA and keep my current router.
I'm pretty sure that 1.12 will no longer let you create a WAN route with a gateway of 0.0.0.0 (direct connect) like you could previously. Can someone check that out?
-
looking in to it now.
-
Cool, thank you.
-
I know I'm bumping an old topic.
But this is the exact problem I'm having.
I've got a cable modem that acts as a bridge AND is reachable by it's own IP.
It's obviously connected to the WAN port.
The router DHCP'd the bridge IP settings, but I also want to be able to access my cable modem (to see the signal ranges and error logs).
So logic would suggest I enter my cable modems IP 192.168.100.1 with sub 255.255.255.0 and no gateway (0.0.0.0) on the WAN port.
Unfortunately this is not accepted.
"only routes via gateways may be created on this interface"
Seeing as this was obviously available before (seeing this thread), I would really like this feature restored.
I'm using a D-Link DIR655 A4 with firmware 1.32NA, this problem might've been restored on the DGL4500 already.
(my apologies, just realised this is the wrong subforum).
-
The feature was removed because of compatiblity issues.