Just a little FYI, hope it helps those that couldn't get it goin.
http://www.practicallynetworked.com/support/linksys_router_help_pg2.htm#Firmware

------------------
FRAGMIESTER

[This message has been edited by FRAGMIESTER (edited 09-20-2000).]

posted 08-15-2000 01:06 AM          

Thanks FRAGMIESTER.

GOD is good - always!

Pe@ce and Victory to all - i'm out

I know a few people have reported this as being a problem too, but I thought I already read someone on this forum suggesting that you use a different port for each client. As for the 27660, I think that's just a miss-print - I think it should read 27960, surely the 6 can't make a difference can it?

Maybe I'm missing something.

Barry.

posted 08-17-2000 07:16 AM          

I'm suprised with all the crying over the LinkSys problem we don't have more posts on this topic.

Don't you guys be crying to me about your LinkSys problems and then fail to post here about the fix!

Pe@ce and Gladitude to you - i'm out

I amazed as well, we had several very long threads going at the time I was trying to get my Linksys working. This thread should have started a serious discussion going. I'm also surprised that it took so long for someone to reply to my post.

If the port number really does make that much difference then it's quite amazing. I hope we get a few responses from those who still own a Linksys.

I know there are a lot of people over in the technology and troubleshooting forum who are still having problems with their Linksys.

BTW, personally I still believe that the 27660 port number is a simple mistake. The only people who know 27960 off by heart are those who run a Quake server and I doubt if Tim Higgins has ever run a game server - therefore it would be very easy to type 27660 instead of 27960 by accident. The main reason I think this is because it has no relevance to the problem that he trying to fix. If you re-read the post you'll see that it has nothing to do with running a server, just several clients simultaneously from behind a firewall. It is my understanding that the solution to that problem is to use a different port number for each client, this has been addressed already. However, I hope I'm wrong with my assumptions because it would be awesome to see the Linksys working properly.

Barry.

---------------------------------------------
Note the "dropped delta packets", this I believe is the cause of the 10 second disconnect, re-read again and consider his fix, I did and it worked for me, maybe it'll work for you 2

posted 08-18-2000 11:49 PM          

quote:

---

Originally posted by FRAGMIESTER:
Hiya Barry :
Note the "dropped delta packets", this I believe is the cause of the 10 second disconnect, re-read again and consider his fix, I did and it worked for me, maybe it'll work for you 2

------------------
FRAGMIESTER

---

Lol, he might except he was kind enough to give it to me.

Thank You Barry, God Bless You!

Pe@ce and Joy to you - i'm out

Yep, you could be right. Plus, if it worked for you then that's great - I guess there must be something weird going on that I don't understand.

Unfortunately, I don't have the Linksys anymore otherwise I would have tried this out to see what happened. if I still had the Linksys I would have tried the fix before posting anything on here - whenever I am able, I prefer to post facts rather than just speculation. However, speculation can be fun too to, sometmes, to see what kind of repiles I get

It does appear as though we are gradually seeing some of the Linksys bugs being ironed out. In terms of the problems with Quake3, I am becoming more sympathetic towards Linksys actually. Since a few other routers have had similar problems (and with only Quake3, other games seem to be ok) it does seem to be an Id software problem.

(just added)
Zxel, your post wasn't there when I started mine. Yes, you have the Linksys now do maybe you could try this out

Barry.

posted 08-19-2000 12:20 AM          

I'll certainly give it a whirl soon, the game server has just been hopping so heavily lately I haven't been willing to take it down to re-route the LAN, right now all the stations are behind two NAT "firewalls" so re-routing (changing the LAN topology) is required for me to test this solution - but I will do it!

Pe@ce and Love to you - i'm out

posted 08-21-2000 02:33 AM          

Pe@ce and Joy to all - i'm out

Your help and sharp eye are GREATLY appreciated. PLEASE keep posting anything that you think might be relevant and not yet covered. Unfortunately, you did not come across THE solution this particular time. I sent an email to Linksys last week with a possible solution and answer to what was going wrong, but got only one (less than useful) reply. Standard fare... and I am a network analyst by profession, and as such I know a good deal about routing, forwarding, and filtering.

I think the Linksys threads are dying down because people (like Barry, tomp, and myself) are giving up on Linksys and going with alternate solutions. If a buttload of product returns doesn't spur Linksys to fix this, I don't see a little ol' email from me getting much attention.

UJ

I run a webserver, FTP server, and Quake 3 server, all from behind the Linksys Router without using DMZ host or any of the other workarounds. I even do videoconferencing through it although I have to enable DMZ host during the session for that.

Since other people have reported similar problems with other routers besides the Linksys, I still tend to think the ISP plays a big part in creating problems. I don't plan to flash any of the lastest firmware since my router has been working great and my server is always full.

I ran a web server and ftp server too with my Linksys and also "abused" it in every way I could think to thoroughly test it. The only problem I had was clients getting disconnected from my Q3 server. Everything else worked fine, and I never had any client side problems (from behind the firewall) such as data corruption during downloads etc.

I'm still using the same ISP but I'm now able to run a Q3 server using the Umax Ugate 3000 router.

It's very difficult to see any consistency in terms of problems seen by different people. It seems almost impossible to pinpoint the exact cause for each of the problems reported.

These hardware router/switch/firewall boxes are great if you manage to get one to work propery - I'm just glad that the Umax works for me. However, I don't have much confidence in any of them. If I was starting to build my home LAN now, given everyting that I now know, I would go for a software solution using a PC to act as the gateway.

It's very interesting that you haven't seen ANY problems at all with several of the Linksys routers. The fact that they all use the same ISP seems to suggest that the ISP does make some difference. Maybe that particular ISP handles the data differently somehow.

Barry.

UJ

The other possibility is that since all the ones you have sampled are in the same area, its possible you have been purchasing from a "lucky batch", or that area gets supplied from a different manufacturing site that just does something different...

All I know is that it's not my problem any more, but I am happy to try and help others as much as possible, especially after all the frustration I went through.

I would STILL like a crack at all the "advanced" settings that are predetermined behind the scenes by Linksys that customers get no control over...

I've actually developed a minor complex from all the posts about it not working correctly and now I don't like to change any of the settings for fear my luck will run out, hehe

posted 08-24-2000 03:11 AM          

See that you don't!

There is no such thing as luck - hehe.

The wife and I like to play on the same servers together. The settings I described allow that. They allow it because although the NAT makes all the clients behing the Linksys look like the same IP to the Q3 server, the server can send independant data streams via the unique ports. Without the unique ports, the steams collide. And anyone that ever saw "Ghostbusters" knows colliding streams "is a *bad* thing."

See my posts on alt.games.quake3 and comp.dcom.modems.cable and help me gather some for information for troubleshooting the server problem.

Comments or questions are appreciated.

[This message has been edited by Freqq (edited 08-24-2000).]

It seems that I interpreted your original description on timhiggins.com correctly. That was the point that I was orginally trying to make when I said that this fix wasn't relevant to the server problems that a few of us have experienced.

I don't think I explained myself very well. However, it's good to see that I'm not going crazy afterall

If I can find my darned Q3 cd, I was going to throw a server up tonight to start testing. I think the wife stole it.

I still think the solution lies in controlling the number of simultaneous UDP connections allowed, along with the hold-open time for said UDP ports. Regardless, I'd like to be able to change the settings and fiddle with them so at least I can prove to myself that I'm wrong... heh.

I think right now the tech behind some of the stuff in these budget routers is seen as a "competitive advantage." The act of documenting and making them available might help the other's in the market place.

A packet problem with the Linksys, I thought, as it had never happened before the installing the Linksys. Here's the funny part, if I set the max_fps to say, 43 (that jump for the blue stuff), I had no problem. Set it above say 60, and error message is back.

Turns out that lowering the AGP setting from 4x to 2X, and turning off the video bios cache fixed the issue.

My system is based on a P3V4X m/b as well, with a Geforce2. I had a lot of very strange problems (only with Quake3 though, everyting else was fine) until I lowered the AGP 4x to 2x.

Weird huh? It almost seems that Quake3 is the ultimate performance benchmark and stability testing utility, because it can really stress a system like no other software is able to. Either that or it's full of bugs

---------------------------------------

Updated 7/5/00 Problems using PPPoE AND VPN
If you are trying to use either PPTP or IPsec tunnels over a PPPoE connection, you may have problems, even with the 1.30 or 1.30.5 firmware. There appears to be a problem with the router's ability to properly adjust the packet size for a connection that uses BOTH PPPoE and one of the VPN protocols.

Windows users can work around this problem by manually setting a lower MaxMTU value in the Windows registry. A value of 1408 appears to work for an IPsec connection, but PPTP connections require a lower value of 512 or so.

If you need help with setting MaxMTU, see the Speedguide.net page:
http://www.speedguide.net/Cable_modems/cable_registry.shtml
NOTE: This workaround will not be necessary and should be removed once Linksys fixes the problem!
--------------------------------------------------------------------------------

And here are the fixes in the beta release of v1.33 firmware........

It may be used on both the 1 Port BEFSR11 and 4 port BEFSR41 routers.

This version has the following improvements over 1.30.
(It includes improvements that were included in V1.30.5 and fixes the WAN DHCP client problem in 1.32.):

1) Change the setting of filter and forwarding from single entry to range of ports.

2) Solve the ping problem from WAN to a LAN host.

3) Add help contents about IPSec / PPTP pass-thru, remote mangement, and range setting

4) Modifications for the IPSec+PPPoE problem

5) URL Access log is created in the STATUS page

6) Leased time display is in the STATUS page

7) User-defined WAN MAC address setting can now be configured in the SETUP page

8) Add Remote management feature

9) Add Remote management / IPSec pass-thru / PPTP pass-thru disable/enable feature in the FILTER page.

10) Fixed the internal loopback bug under PPPoE or DHCP environment.
------------------------------------------

What I was wondering if the success rate of the Linksys router users for hosting Q3A servers has been the "absence" of the pppoe on their isp, as for me I'm thinking that might have been the prob for me, and since this has been addressed in the latest firmware and more fixes on the way...hehehe, hopefully