Author Topic: New Patch/Primary/Linksys/Room List (Read 2386 times)

HalOfBorg · « **on:** September 23, 2008, 02:36:17 am »

I was hoping that the new patch would help the Linksys router limiting chatroom list to about 400, but it seems to be having the opposite affect - now I get no rooms at all with Primary - and only about 500 with secondary.

Yes, my ports are forwarded correctly.

Me Here · « **Reply #1 on:** September 23, 2008, 02:52:51 am »

Hi HalOfBorg,

Hun make sure that in the Oledlg.ini file that has been placed in your WInMX folder that you have disabled upnp forwarding

/enableupnp 1 set this to 0

No spaces after it, and restart, some routers I know have conflict problems and the upnp is set active by default for ease with new users.

nylly444 · « **Reply #2 on:** September 23, 2008, 05:05:53 am »

it's simply your router deciding that such a lot of udp packets is too many, I get the same with my netgear, i.e. I only get around 500 results on primary.

HalOfBorg · « **Reply #3 on:** September 24, 2008, 02:23:20 am »

Yeh, I was hoping that they fixed it. Maybe slowed it down, or added a throttle.

Me Here · « **Reply #4 on:** September 24, 2008, 09:31:55 am »

I'm not entirely sure that can be done in the patch itself, maybe something we can discuss with EaglE. If anything the faster better working pirmaries and caches I think the problem maybe intensified by that returning those results even faster causing it to be worse... although just typing that out makes it sound like an oxymoron... lol

Did you get things operational HalOfBorg ?

wonderer · « **Reply #5 on:** September 25, 2008, 01:46:32 am »

Backup the modems config to a place where you can find it back

In the config file, look for the section:

(protect
(udpflood
(enabled(1))
(rate_limit(30))
)
(icmpflood
(enabled(1))
(rate_limit(30))
)
(synflood
(enabled(0))
(rate_limit(30))
)
(winnuke(0))
)

set the udpflood "enabled(1)" to "enabled(0)", and reload the configuration into the router. It appears to remove the Steam issue (although the flood of packets still results in some NAT failures, probably due to the large amount of traffic). Try it out, and see if it works for you.

if it works you can try to enable and try a higher value in rate_limit(30))