Ian wrote:
> Thanks for the help. I have a friend who has a v4 and wouldn't mind swapping
> with me. I have a couple more questions pertaining to your response, see below:
>
> prg wrote:
> >
> >> My question is: is this normal behaviour for newer routers?
> >
> > Don't know, but with less memory ...
> >
> > Also having wireless clients could affect it. They use more memory and
> > processing resources than ethernet clients.
>
> OK, but the connection is lost EXACTLY in 10 minutes, traffic or not, wireless
> or not. So it must be a new "feature" they've introduced. I'm frustrated because
> I can't find ANY information on this magic 10 min period. Linksys themselves say
> they know nothing about it. Or it might just be a coincidence.
"[C]onnection is lost EXACTLY in 10 minutes" sounds like a timer going
off, not memory cramp or overheating or router "misconfiguration".
> > OTOH, there may be some "magic" config combo that will allow the router
> > to work as you want. Have you tried simply forwarding selected ports
> > to the dmz box rather than using the router's dmz (all ports)
> > forwarding feature?
>
> I'm playing with various settings on the router, so far no difference. What I'm
> actually doing is I'm running an X server at work so I can run X applications on
> my home computer, which is behind the router. ...
OK, the apps are loaded and running on your home computer and you are
at work where the apps are displayed via the work computer's X server.
Correct?
> ... So, the computer running the X
> application doesn't even need to be a DMZ host, or have any ports forwarded,
> because it is a client and initiates the connection by talking to port 6000 on
> the server. ...
How does your home computer _initiate_ the connection to your work
computer's X server? How are the apps started? How do you connect
your work computer's X server to your home computer?
> ... So this is an `outgoing' port mapping (is this the right terminology?)
>
> Thanks again for your help!
>
> Ian
If it is a timer going off, then the router(s) should not be involved
as a problem source. It sounds to me like the computer _running_ the
(remote) apps (as opposed to the the computer displaying) is timing out
in some sense. If you know the timing of the lost connection, you
should be able to capture the packets on the wire (much easier than
wireless) and see what is being passed when the connection is lost.
May provide clues.
Just how is the computer running the remote X apps set up to allow
incoming connection requests? Are you remoting the X display directly
or using ssh to forward?
What I can't quite figure out here is just how it is you can _start_ a
remote X session, _then_ have it time out right at ten minutes. I
mean, you can set things up that way to disallow limitless access, but
you would have to go out of your way to do so. Is there anything on
the office network that might timeout or bump a connection at ten
minutes?
Anyway, I would concentrate on the end where the remote apps are
running. The _diplay_ that you are using is providing the keyboard,
mouse and monitor. The other end running the apps you can't really
"see" so it's difficult to tell what/why/if it is timing out. Sounds
suspiciously like an _inactivity_ timeout or some kind.
But that doesn't really make sense. Why would a screensaver or even a
OS or BIOS inactivity timer trigger?
Sorry, interrupted by a family member running XP Infected. Must run.
I'll check back later.
prg
> > I've not even bothered to look at what's available on the v5 routers
> > beyond the web interface settings. Don't even know if there _are_ any
> > other options/configs.
> >
> > I did manage to find a v2 router at Walmart and look for pre v5 routers
> > whenever I'm in one. Walmart is not a hotbed of Linux users. For
> > customers, I've already decided to go with the wrt54GL when I need one.
> >
> > good luck,
> > prg
> >
> > PS for anyone wondering how to tell wrt54G versions.
> > -- wrt54G:
> > http://wiki.openwrt.org/OpenWrtDocs/...6cc5845eb29751
> > -- wrt54GS:
> > http://wiki.openwrt.org/OpenWrtDocs/...9a4bb3b0fc9a48
> >