Are you talking tcp or udp? If we had afs running over tcp, the ten-minute
ping would keep the connection alive unless your nat was really broken.
For the current udp implementation, I recently dropped in some code that
will reduce the ping interval to one minute. We have discussed this on
opena
Russ Allbery wrote:
> Jeffrey Altman <[EMAIL PROTECTED]> writes:
>
>> I have found that with the Linksys routers that SSH sessions drop after
>> 10 or 15 minutes of being idle if the server decides it wants to send
>> data to the client. It may be that the NAT will allow the client to
>> re-use t
Jeffrey Altman <[EMAIL PROTECTED]> writes:
> I have found that with the Linksys routers that SSH sessions drop after
> 10 or 15 minutes of being idle if the server decides it wants to send
> data to the client. It may be that the NAT will allow the client to
> re-use the same external port if it
> I have found that with the Linksys routers that SSH sessions
> drop after
> 10 or 15 minutes of being idle if the server decides it wants to send
> data to the client. It may be that the NAT will allow the client to
> re-use the same external port if it sends data, but the mapping is
> certai
I have not seen the spec and I do not know how feasible it would be to
implement it as part of the application when the OS is already
supporting it directly.
I know nothing about upnp but if, for example, it's simply a matter of afsd
making a single call to the OS to register the service, th
Jim Rees wrote:
> Unfortunately, switching to tcp will not solve your NAT problems.
> NATs drop their mappings from internal addr/port to external port
> equally for both both udp and tcp.
>
> I don't believe that's true for most nats. The one I use at home has a one
> day timeout for tcp,
Unfortunately, switching to tcp will not solve your NAT problems.
NATs drop their mappings from internal addr/port to external port
equally for both both udp and tcp.
I don't believe that's true for most nats. The one I use at home has a one
day timeout for tcp, and 60 seconds for udp. Lin
>I checked out the rxtcp branch, and I'd like to give it a try, but I
>couldn't exactly find any documentation. Any pointers on how to try
>it out? I realize it's not ready for prime time yet. If I just
>compile it up and install it does it listen for both rxudp and rxtcp
>connections? How does
Unfortunately, switching to tcp will not solve your NAT problems.
NATs drop their mappings from internal addr/port to external port
equally for both both udp and tcp. If the internal peer is not
sending data often enough to the external peer, the mapping will be
dropped and the connection will be
