Print

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

[Reinvented]

In 1.02, I could have my SPI Firewall on, and have it set to Port and Address Restricted, and connection could be fine all day long.

Now, in 1.15 I can set it like that, but get HORRIBLE lag spikes still, even with ports forwarded and what not.  I shouldn't have to lower my settings, or completely turn them off to get this to work.  Please look into this, and get it to work PROPERLY.

Also, my posts regarding Intel Wireless 2200BG have gone unanswered, and I'm trying to get support for my adapter.  It still cannot connect with any type of encryption, be it WEP or WPA/WPA2.

Fix it, please. 

[chrisnclovis]

Here's a few things I'd try if you haven't already:

Uninstall and let windows automatically reinstall the driver for the wireless adapter on you computer.

Disable SPI on the router.

Disabled WiFi Protected setup on the router

and disable mulitcast streams.

These things do not always work for everyone but I have seen it work for people having the same issue you're describing.

[Reinvented]

Here's a few things I'd try if you haven't already:

Uninstall and let windows automatically reinstall the driver for the wireless adapter on you computer.

Disable SPI on the router.

Disabled WiFi Protected setup on the router

and disable mulitcast streams.

These things do not always work for everyone but I have seen it work for people having the same issue you're describing.

I'm not sure how I should reply to you....not even in the slightest bit...

I shouldn't HAVE to disable the SPI firewall to get something to work.  Especially if it was fine with it on before on previous firmwares.  1.13 and up were horrible regarding this latency.

Multicast streams are disabled by default...doesn't make a damn difference.

And Windows can't properly identify the adapter by itself...hence why you have to install the driver in the first place.

It's been an ongoing problem, even on the DGL-4300 I had.  And it's still yet to be resolved. 

So, to recap...  Still very bad latency, and no I shouldn't have to turn off a damn firewall or any other settings that worked previously, to NOW get it to work.  That's just [exploitive deleted].

And the SPI firewall is pretty important...and you are making us shut it off?  Please...

Fix it soon...

[Puffnstuff]

Having run the 1.15fw for since it became available I now am having problems with it not accepting changes.  I can reboot it all day and this doesn't change.  I'm about to return to the 1.12fw which did allow for me to make and save changes whether it was a fresh reboot or several days up.

[Dragonslore]

You know, seeing as the firmware is nothing more than an operating system which in most cases is a custom version of Linux. Not sure what OS they are using with these routers seeing as Ubicom are the ones behind the firmware, but seeing as this poroblem first occurred with v1.13 and as we are now finding out, is still happening with v1.15 this sounds very much like there may be a memory leak in the Firmware. More accurately, a memory leak in one of the modules of the Operating System contained within the Firmware.

Either that, or something was not configured correctly before it was released as a firmware so the Operating System is writing Temp Files to memory and Failing to Delete the temp files.But when you look at it this way, where would the temp files be writen to in Linux of Similiar Operating Systems? They would be writing to a Temp directory or to a Swap partition. If this is the case, then maybe it's somehow using available space within the firmware.

This last would explain why no changes can be made after a while cause little by little the available space in the firmware would be used up leaving no room for any changes to be made as you need temp files to do this.

This speaks volumes about a setting having been incorrectly configured as the operating system should be using the system (router) memory for this and it should be deleting temp files. Even just shutting down the router should be able to clear temp files from memory if it was configured correctly.

So it would seem someone overlooked or missed a setting before using the Operating System to build the new firmware.

Now this is all theoretical conjecture from someone who has run Linux, but I feel it should be looked into.

[anon]

Just let us have fw 1.02 back.

[funchords]

And the SPI firewall is pretty important...and you are making us shut it off?  Please...

No, it's not.  It's a feature that had a sliver of value, but it's a feature that makes comparison shoppers go, "Ooooooh!"

Turning off SPI doesn't forward your unforwarded ports, it doesn't halt the detection of attacks, it doesn't keep NAT table entries open after the conversations have ceased -- it just blocks state mistakes.  It is intended to prevent TCP packet injection that requires the attacker to know who you are talking to on what ports.  Your TCP/IP stack already detects and prevents this attack in exactly the same way as the router.   

I don't have a DGL-4500, but I have a DGL-4300 and I have a DIR-655 and SPI has been borked in both in the most recent firmware versions.  Consequently, I run with SPI off. 

As for lags, if these are those kinda random 15-second halts with no apparent reason, see this bug -- http://forums.dlink.com/index.php?topic=2737.msg16066#msg16066 ... I bet you'll find it was a DNS lookup with an NXDOMAIN response (and maybe you'll also see the router blocking an outgoing ICMP packet around that time) -- but if it's generic latency throughout, I'm not sure I've seen that very much.

PS: I agree with you -- you shouldn't have to turn off these features.  These misbehaviors are bugs.  They need to be fixed, not dismissed.

[Lycan]

SPI causes timeout issues with gaming. It's not broken, it's intended.
Disabling SPI completely is impossible. Unchecking the box simply changes the NAT type.

[JackUup23]

BRING BACK 1.02!!!!

[anon]

So was it off in 1.02 even when checked?

[Lycan]

No, you're confusing failures in the UPnP port manipluation and port forwarding issues with SPI. I always suggest changing the SPI for gaming, it lightens the load on the NAT CPU and reduces timeouts.

As for 1.02, you can't go back and theres no way for us to downgrade. The later firmwares changed the Kernel of the OS on the router.

[Reinvented]

Lycan,

So, the way I had it configured before and it worked, is not acceptable?  Was fine on the 4300 I had, and was fine in the 4500 on 1.02 and even 1.03 that I had tried from the FTP.  Was even fine on 1.12, but anything after completely bombed.

SPI enabled
Port and Address Restricted (both for TCP and UDP)
UPnP enabled
Warcraft 3 ports are forwarded in gaming.

These things were pretty much enabled from the get-go.  The only thing that's different, is that I changed the UDP filtering to Port and Address Restricted, and that was it.

And it's always been like that. 

So, why on earth does it fail? 

[Lycan]

I'm not saying that the 1.15 code is correct, in fact I'm agreeing that it's messed up. What I'm saying is games that suffer from disconnects and issues with connectivity usually are resolved by disabling the SPI.
This is how our routers have worked since the 524.
Now, the 4300 is a ip3k CPU @ 275mhz i believe, whereas the 4500 is almost 400mhz. Overhead on the NAT is less likely the issue with the 4500, but as a standpoint for troubleshooting and as a possible workaround I suggested that the SPI should be disabled. If it allow you to play your game properly then thats cool for you and give us an idea of where to look as far as issue resolution.

I run my 655 WIDE open, no one hacks me. I download TONS of stuff via torrent and re-up things via FTP and I require MY NAT to be as free as possible. I have 3 XboX 360's connected and online at ALL times.
I'm not any less protected by the firewall, a closed port is a closed port. If someone figured out how to access my wan VIA a statement in the statetable that was old or corrupt, then my firewalls on my PC's will stop them there. Thats how I do it, I'm not saying it's right for everyone, just makes troubleshooting easier.

I've started a thread in the 4500 forums regarding the 1.15. Go there, list all possible issues and I'll address them with PM.

[funchords]

I agree with Lycan's estimate above.  Turn off SPI.  Nothing bad will happen.  SPI just makes sure that the TCP conversation doesn't change gears -- it's a thin layer of added protection against an attack that won't work anymore anyway.

Unchecking the (SPI) box simply changes the NAT type.

I didn't understand this part -- or did I misunderstand what you said.  Can you explain further?  Why would SPI change NAT?

[Lycan]

It doesn't change the NAT, changes the TYPE of NAT. From full cone to the other one, (can't think of the name right now). NAT is still NAT. Disabling SPI used to be the only to get XBL to show as OPEN.

Need your help guys, read this and reply.
http://forums.dlink.com/index.php?topic=3099.0