StarDestroyer.Net BBS

Okay, Trillian's bullshit's been sorted, and I flashed the router's firmware. Now I'm getting very frequent disconnects that appear as a 'Network Cable Unplugged' prompt that appears for only half a second. The computer then chugs for two to four seconds right afterward, then I get booted off the AIM chat after a fifteenish-second delay. I'd like this shit fixed ASAP!

This'll sound wierd, but are you running Bittorrent? Not even downloading anything via it, but running it? I've known some routers to conk out for a few seconds at erratic intervals simply because Bittorrent was running on one of the systems on the network, possibly related to unopened ports in the firewall. If so, try killing Bittorrent and see if the problem keeps up. May or may not be the issue, but it's easy to test, at any rate.

White Haven wrote:This'll sound wierd, but are you running Bittorrent? Not even downloading anything via it, but running it? I've known some routers to conk out for a few seconds at erratic intervals simply because Bittorrent was running on one of the systems on the network, possibly related to unopened ports in the firewall. If so, try killing Bittorrent and see if the problem keeps up. May or may not be the issue, but it's easy to test, at any rate.

No. Ironically, my roommate turning bittorrent on seems to have fixed it.

Either that, or the issue unfucked itself, THEN bittorrent was started unrelatedly...

Hmm. Odd. Very odd.

Do you have MAC address cloning turned on?

Laird wrote:Do you have MAC address cloning turned on?

Turned it on for a bit; the whole net connection broke spectacularly!

It appears the random disconnects are much lower in frequency almost to normal (one dc a day) after godknowswhat; seems to have 'fixed' itself (yeah right) right before Scott started his torrent...

Do you have a Linksys WRT-54g??

From wikipedia:
"As shipped, the Linksys firmware crashes under heavy peer-to-peer network traffic, such as BitTorrent. The reason for this crash is that Linksys has programmed the router to keep track of old connections for five days. This five day limit quickly overwhelms the router when there are a high number of network connections, such as with BitTorrent, and can only be resolved by power cycling the router. For a detailed tutorial on how to permanently fix this issue on a pre-v5 router see the uTorrent FAQ."

Stile wrote:Do you have a Linksys WRT-54g??

From wikipedia:
"As shipped, the Linksys firmware crashes under heavy peer-to-peer network traffic, such as BitTorrent. The reason for this crash is that Linksys has programmed the router to keep track of old connections for five days. This five day limit quickly overwhelms the router when there are a high number of network connections, such as with BitTorrent, and can only be resolved by power cycling the router. For a detailed tutorial on how to permanently fix this issue on a pre-v5 router see the uTorrent FAQ."

BEFSR41 v4, and no, I see no reason at all to suspect it doesn't also have this issue.

Einhander Sn0m4n wrote:BEFSR41 v4, and no, I see no reason at all to suspect it doesn't also have this issue.

Hmm, try here. Linksys boards
Page 2 and on have some fixes.

Einhander Sn0m4n wrote:It appears the random disconnects are much lower in frequency almost to normal (one dc a day) after godknowswhat; seems to have 'fixed' itself (yeah right) right before Scott started his torrent...

While it is likely that in your case the router is the issue, some ISPs have a disconnect after x time policy (usualy 24 hours) in order to fuck up your assigned ip address so that you can't use your home connection for running a server (and, yes, they belive people are too stupid to use one of the dynamic DNS services).

mmar wrote:

Einhander Sn0m4n wrote:It appears the random disconnects are much lower in frequency almost to normal (one dc a day) after godknowswhat; seems to have 'fixed' itself (yeah right) right before Scott started his torrent...

While it is likely that in your case the router is the issue, some ISPs have a disconnect after x time policy (usualy 24 hours) in order to fuck up your assigned ip address so that you can't use your home connection for running a server (and, yes, they belive people are too stupid to use one of the dynamic DNS services).

Quite probably, actually.

And lo and behold, haven't had trouble of any sort at all today. I have MTU at 1492, router logging off, Mac cloning off (enabling it temporarily caused all sorts of things to belch pretty sparks and then flatline; no connection), and so far so good.

mmar wrote:

Einhander Sn0m4n wrote:It appears the random disconnects are much lower in frequency almost to normal (one dc a day) after godknowswhat; seems to have 'fixed' itself (yeah right) right before Scott started his torrent...

While it is likely that in your case the router is the issue, some ISPs have a disconnect after x time policy (usualy 24 hours) in order to fuck up your assigned ip address so that you can't use your home connection for running a server (and, yes, they belive people are too stupid to use one of the dynamic DNS services).

Hence why I love my ISP...home service with a permanent static IP. So awesome. If only I felt any need to run a web server.

Original problem (Trillian not wanting to connect without a router reset) is back, along with 'microdisconnects' every now and again under heavy load.

I'm very seriously considering just getting a new non-Linksys router. BEFSR- and WRTG- routers are just flawed.

Einhander Sn0m4n wrote:I'm very seriously considering just getting a new non-Linksys router. BEFSR- and WRTG- routers are just flawed.

BEFSR is definitely sucky, but WRTG can be good. Try a router that can run an open-source firmware like DD-WRT, maybe WRT54GL or a Buffalo WHR G54s.