Print

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

[Lycan]

I've been taking notes on all these issues. I will attempt to test these problems and forwarding the cases to PM.

[Balthazor]

If any of this may get back to D-Link, let me be a bit more specific:

Using the 1.02 firmware I had my DSL modem set up in a PPP IP Connect mode, which basically limits the DSL modem to just being a modem; it uses DHCP to pass configuration information to the router (in this case the DGL-4500.)  It passes the external WAN IP from my ISP, DNS servers and allows the DGL-4500 to perform NAT and firewall functions, elegantly allowing me to NOT have to worry about port forwarding twice, for example.

When I upgraded to the 1.12 firmware the DGL-4500 would still receive the correct external IP as assigned by my ISP and then delegated via DHCP to the DGL-4500; it would receive correct DNS server information and gateway info also.  To all appearances it looked right.  But I couldn't access my DSL modem, and couldnt' access the internet.  It was like NAT traversal just doesn't function any longer, or something. 

I had to enable NAT on my DSL modem (previously unused due to the aforementioned PPP IP Connect bridging-type mode) in order to access anything via the DGL-4500's WAN port.  I then put the DGL-4500 in the DMZ of the DSL router to work-around having to port forward twice through the DSL modem through the DGL-4500. 

Port forwarding is acting very funny.  On some games it works fine still for hosting games (Warcraft 3.)  However, Company of Heroes doesn't work at all.  CoH developer info says to forward UDP 6112 & 30260; if I do so, I can't access their online matchmaking service Relic Online at all.  If I disable the port forward rule I can access Relic Online but can't host games (without port forwarding.)  This port forward rule worked in 1.02.

The only thing I can think that is different between Warcraft 3 / Blizzard.net and Company of Heroes / Relic Online is that Relic uses UDP 30260 for outgoing communication and UDP 6112 for incoming, wheras Blizzard.net uses TCP 6112 for both incoming and outgoing (I think.)  I tried setting up the Company of Heroes rule for just UDP 6112, but with the same result - no connection to Relic Online at all, like the port was blocked to my computer. 

I did have success in setting up a port triggering rule, using UDP 30260 as the trigger to open UDP 6112.  What I don't understand is why the port forward rule worked prior to the firmware upgrade and why it doesn't now; and why does it work still with Warcraft 3 and not with Relic Online?  I don't know enough about networking to tell you the answer to that one.

My vonage phone worked with the 1.02 firmware without any port forward rules or any special setup.  Just plug and play.  Now with the 1.12 I was able to receive calls but outgoing communications were either blocked completely or blocked after a few seconds.  I could call out, speak for a few seconds, and then lose outgoing voice comms (but be able to hear the other person.)  Most of the time I just couldn't call out at all, although I'm still receiving calls, although I would still either be unable to talk or only be able to talk for a few seconds before losing outgoing voice altogether.

Port forward rules based on the Vonage help site (they say a random UDP port 10000 to 20000 is selected for in/out voice communications) blocked my phone from working at all.  Port triggering didn't work.  Disabling SPI on the firewall finally allowed me to use my phone most of the time, although I still occasionally get some dropped voice comms or can't dial out; I am still receiving calls. 

GoToMyPC, a remote PC access service, also ceased to function on the 1.12 firmware (I am using my computer as a client to help my Mom keep her computer updated.)  Their help site says port forwarding isn't required, and only list some outbound ports that are required for communication, so I don't see how I can fix that. 

For troubleshooting purposes I turned off all software based firewalls to prevent this from being a factor.

DHCP IP Reservation seems to function properly; my first thought was that maybe all these problems are caused by incorrect IP assignments.  But everything seems to be assigned the correct IPs. 

The DSL modem I am using is Paradyne (now Zhone) 6112-I2 using the latest 03.01.08 firmware (from May 2008 or so.)  Again, it worked fine with the 1.02 firmware.

[Balthazor]

For further clarification, NAT filtering is set to endpoint independent, the same as when I had the 1.02 firmware.

I have tried resetting to factory defaults (both through the software GUI and by doing the reset-to-default reset button / power disconnect methods) and manually entering in all the settings with no change in the router's performance.

[FromAtoN]

Switched back to 2.4GHz and so far only one client disconnect in two days using two DWA-160Bs and my 2 year old hasn't complained using the DWA-652 on her laptop.  I would love to go back to 5GHz because my throughput isn't up to snuff on the crowded band.  I've never had this many disconnects with 802.11a before.

Make that a second disconnect with the DWA-160B.

[phat78boy]

I am seeing the same issues Balthazor has mentioned. On 1.02, none of this was a problem. I really wish there was a way to go back to 1.02.

[arod]

I also wanted to add that 1.12 will go into a reboot cycle for me if I attempt to load the hurricane coverage page from http://www.livenewscameras.com/map.html. This has never happened to me before flashing to the 1.12 firmware.  So far I'm not happy with the lost functionality I'm experiencing.  I hope that d-link can address these issues soon with a revised firmware.

I have the latest firmware on my DGL-4500 and I thought I'd give the link you provided a try and as of right now I see 8 live cameras regarding the hurricanes at the same time posting this comment while my GF is myspacing on her macbook.. No issues so far with my router.

[Puffnstuff]

Anyway I tried loading the page again using firefox 3.0.1 instead of ie7 and the site loaded just fine with no problem. Why would firefox not crash the router but ie7 does?  Firefox also shows a blue band across the top of the router menu pages and ie7 doesn't.  Does the firmware have an issue with the way that ie7 handles it?  Now I'm curious to the real cause if this problem.

[Balthazor]

I am seeing the same issues Balthazor has mentioned. On 1.02, none of this was a problem. I really wish there was a way to go back to 1.02.

I wish so, too.  I'm RMAing my router since it isn't very functional in this state.

[MPDamon]

Any further updates on the PSP to PS3 issue?  Are they planning another firmware release? 

[Lycan]

We've contacted Sony and are working to locate and resolve this and other Sony related issues.
Any information and further testing done by you guys that you wanna share is welcomed.

[Huddadudda]

BTW anyone notice that on the LCD under date and time it shows "SUP" for the month instead of "SEP" However in the time area the month is selected as September. Just thought someone should let it be known.

[Lycan]

Confirmed. Correction pending.

[Balthazor]

BTW anyone notice that on the LCD under date and time it shows "SUP" for the month instead of "SEP" However in the time area the month is selected as September. Just thought someone should let it be known.

That isn't the month.  'SUP' is slang shorthand for 'What'S UP?'  It is just trying to be cool with you.

They're going to correct it in the future to read 'SUP HOMEY?'

[Lycan]

LOL. I wish.