From: Nick Drage <nickd@funkyjesus.org>
To: netfilter@lists.samba.org
Subject: Re: sendto: Operation not permitted
Date: Wed, 5 Jun 2002 22:25:50 +0100 [thread overview]
Message-ID: <20020605222550.F2090@funkyjesus.org> (raw)
In-Reply-To: <NJEFLNJDIFFNMHDEBKMJGEDLDOAA.jpatterson@asgardgroup.com>; from jpatterson@asgardgroup.com on Thu, May 30, 2002 at 09:01:32PM -0400
On Thu, May 30, 2002 at 09:01:32PM -0400, Joe Patterson wrote:
> kind of the same way that a system determines what an ICMP message relates
> to. For example, the format of an ICMP unreachable message, which includes
> such messages as the fragmentation needed and all the network/host/port
> unreachables, is:
<snip>
Thank you very much for this detailed explanation, much appreciated.
> Excellent documentation on all of this is in "TCP/IP Illustrated, Volume
> 1: The Protocols" by W. Richard Stevens. If you really want to know
> everything about IP and don't care that your brain might explode, read it
> cover to cover. :)
Heh, I have two copies of this around, one at work and one at home. I've
yet to read it all the way through, but it's at the top of the "to read"
pile.
Actually I know this book has been mentioned before - I commute by train a
lot, is it a good book to read on the train, or best to read while I'm sat
online so I can watch "live" what it describes?
Thank you.
--
FunkyJesus System Administration Team
next prev parent reply other threads:[~2002-06-05 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0205301011270.31451-100000@paix.pilosoft.com>
2002-05-30 19:55 ` sendto: Operation not permitted Antony Stone
2002-05-30 23:58 ` Nick Drage
2002-05-31 1:01 ` Joe Patterson
2002-06-05 21:25 ` Nick Drage [this message]
[not found] <Pine.LNX.4.44.0205300945340.31451-100000@paix.pilosoft.com>
2002-05-30 19:13 ` Antony Stone
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=20020605222550.F2090@funkyjesus.org \
--to=nickd@funkyjesus.org \
--cc=netfilter@lists.samba.org \
/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