Chris <chris@thisisnotanemailaddress.ca> hath wroth:
>Jeff Liebermann wrote:
>
>> Are you sure that connecting the computer is the problem and not what
>> the computer is doing? *For example, if the computer was hosting a P2P
>> file sharing program (i.e. BitTorrent), it might be crashing the
>> router due to a large number of IP sockets and buffers used.
>Now that you mention it, this does happen mostly when I'm playing an online
>FPS (Tremulous, Enemy Territory, Doom3, etc.). I have my laptop on so that
>I can browse the net while I wait to respawn (which that happens more often
>than I like to admit ;))
>
>I'm wondering now, if the high traffic caused by the online game is
>overwhelming the router?
It's possible. It's not the amount of traffic that kills cheap
routers. It's the number of simultaneous connections (streams or IP
sockets) that require huge amounts of buffer memory in the router that
just isn't there. The router has to juggle what little RAM it has to
work with, and sometimes does it badly. I don't think that's the
cause but it's worth researching and tinkering with your usage
patterns to see if there's a connection. 20 minutes sounds like about
the time it would take to thoroughly scramble some buffers and create
an over-run that clobbers some other code that eventually initiates a
crash or reboot. It might be just one game that's causing it.
However, it shouldn't be happening and does seem to point to bad code
in the router.
>I will try disabling the wireless and have both machines connected. Perhaps
>the wireless part of the router is causing the problem?
I don't think so. The wireless bridge section (i.e. access point
section) is suppose to be just an extension cord for ethernet. It has
it's own collection of horrors but crashing the router or rebooting is
not one of them.
>I tested the router with the exploit site and it passed.
Oh well. That would have been too easy.
>My laptop uses openSUSE 10.2 and my desktop is openSUSE 10.1. I had this
>same setup with my old Linksys wireless B router. That router was rock.
>I had it for 4 years (I think) and didn't have a single problem with it.
That would probably be a BEFW11S4 v1, v2, or v4. When I was running
the v4 version at home, I thought it a horrible router. It would hang
or act weird for no obvious reason. I could hang it with 2 of the
router exploit tests. I had to constantly power cycle it to keep it
alive. I'll assume you had one of the other hardware versions.
I don't think this has anything to do with running SUSE unless you've
got some manner of custom packet generator, AP simulator, MAC address
flooder, ARP flooder, or similar IP packet hacking tools running.
>Well, no problems until that router died.
I've seen a few questions no failed BEFW11S4 v2 routers drift by this
newsgroup in the last year or so. Apparently, they have some type of
lifetime problem.
>So I bought the D-Link wireless G
>thinking that I would upgrade my wireless adaptor to G.
Well, that's generally a good idea.
>I think my next move is to contact D-Link. It's been my experience though
>that companies tend not to help, so I'm not expecting much feedback from
>them.
It's worth a try. There's a real chance that they know about the
problem and have a secret project to fix it with a bios update going.
This has happened a few times with other Dlink products (i.e. DI-624).
The problem is that it was in beta for what seemed like forever, the
only site that had it was in Italy, and the final version was released
dated from before the last beta version. If you're really
adventurous, go unto:
<ftp://ftp.dlink.com>
and see what you can excavate. I couldn't find anything with WBR2310
inscribed.
Also, note that the GPL code for most of DLink's routers has been
quietly released on some models that use Linux. Sorry, your WBR2310
is not listed.
<ftp://ftp.dlink.com/GPL/>
<http://gpl-violations.org>
--
Jeff Liebermann
jeffl@comix.santa-cruz.ca.us
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
D-Link WBR 2310 rebooting 
Linear Mode
