From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Access through NAT
Date: Fri, 12 Aug 2011 18:55:13 +0100 [thread overview]
Message-ID: <103633f6f9a4ad1c1e97f49537a065d7@terzarima.net> (raw)
In-Reply-To: <391F0A47-638F-4793-93EF-CF6A23EC472C@orthanc.ca>
>As mentioned elsewhere, beware assinine five minute state timeouts in
>the NAT implementation.
with the new Netgear supplied by my cable company, I discovered (on a forum)
that switching off a supposed security option to do some form of packet
inspection had the pleasant effect of eliminating the only such timeout
on that box, so my cpu connections stay up for days.
prev parent reply other threads:[~2011-08-12 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 17:21 Lyndon Nerenberg
2011-08-12 17:55 ` Charles Forsyth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=103633f6f9a4ad1c1e97f49537a065d7@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).