public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: "Speakup@Braille. Uwo. Ca" <speakup@braille.uwo.ca>
Subject: Re: Firewall question:
Date: Fri, 8 Jun 2001 10:45:32 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0106081043450.16980-100000@ignatious> (raw)
In-Reply-To: <000001c0f02b$ecb8fc20$3b910f8e@dpsd.gov.calgary.ab.ca>

The keep alive packet for any connection is on the same port as the
connection. The difference you are seeing is that the firewall times out
the connection sooner then the keep alive packets are sent. This isn't
uncommon. In fact, often times it is done intentionally to prevent you
from breaching the firewall with "safe" looking programs that happen to
keep an open connection and then let whatever you want through.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Stephen Dawes
 ` Kirk Wood [this message]
   ` Stephen Dawes
     ` Raul A. Gallegos
       ` Stephen Dawes
     ` Kirk Wood
       ` Stephen Dawes

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=Pine.LNX.4.21.0106081043450.16980-100000@ignatious \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).