All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wingtung.Leung s965817@uia.ua.ac.be
To: lartc@vger.kernel.org
Subject: [LARTC] A complicated routing scenario (for me at least)
Date: Tue, 14 Nov 2000 14:44:09 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216916@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216914@msgid-missing>

<PRE>On Mon, 13 Nov 2000, Andrew wrote:

&gt;<i> 2. if I tag a packet coming into the router/firwall above with ipchains
</I>&gt;<i> for routing purposes, will the tag persist to the reply packets? Or do I
</I>&gt;<i> have to tag the reply packets with ipchains from the responding server?
</I>
You'll have to tag them whenever they enter your gateway. The reply
packets are just packets, at ip level there is no difference between them.
Only the very first packets, which initiate the connection, carry some
extra flags.

&gt;<i> 3. In reading the various documentation, I noticed several references to
</I>&gt;<i> files in the /etc/iproute2 directory. Related to this directory:
</I>&gt;<i> 	b) I don't currently have this directory in /etc. Is it something I
</I>&gt;<i> just create, and does it's existance imply that the kernel will read
</I>&gt;<i> configureation data from it on boot?
</I>
I believe you can just create that directory and the files.

&gt;<i> Suggestions in this area are much appreciated since I have no experiance
</I>&gt;<i> in HOWTO writing. (Plenty of writing experiance, just not howtos)
</I>
There is an HOWTO about writing HOWTO's, I think. Try
<A HREF="http://www.linuxdoc.org/">http://www.linuxdoc.org/</A> for more elaborate info.

Salukes,

Tung




</PRE>

  parent reply	other threads:[~2000-11-14 14:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 22:58 [LARTC] A complicated routing scenario (for me at least) Andrew
2000-11-14 14:34 ` Arthur
2000-11-14 14:44 ` Wingtung.Leung [this message]
2000-11-14 20:15 ` Andrew
2000-11-14 21:47 ` Whit
2000-11-14 23:10 ` Wingtung.Leung
2000-11-15 10:49 ` Arthur
2000-11-15 11:27 ` Arthur
2000-11-15 14:57 ` Warren
2000-11-15 19:20 ` Andrew
2000-11-15 19:30 ` Arthur
2000-11-15 20:11 ` Andrew
2000-11-17  1:07 ` Andrew
2000-11-17 12:11 ` Mike
2000-11-17 12:24 ` Mike
2000-11-17 13:00 ` Arthur
2000-11-17 21:25 ` Mike
2000-11-18 16:28 ` Warren

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=marc-lartc-98373938216916@msgid-missing \
    --to=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.