From: "Paul Smith" <sparky@btinternet.com>
To: lartc@vger.kernel.org
Subject: [LARTC] What have I missed
Date: Wed, 03 Oct 2001 13:34:21 +0000 [thread overview]
Message-ID: <marc-lartc-100211622108212@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
People,
I am trying to get to grips with simple source routing in
the advance routing how-to.
I have a Linux box with two network cards
Eth0 192.192.192.3
Eth1 10.10.10.1
With IP Forwarding switched on any machine on either network
can ping any other machine.
I can disable a user by adding a new route.
What I want to do really is enable a machine to pass though
the gateway. Do I need IP Forwarding on for this and if not what routes
should I put in place.
I guess I have missed something really simple here but I
cant see it.
Thanks
Paul
[-- Attachment #2: Type: text/html, Size: 7461 bytes --]
reply other threads:[~2001-10-03 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-100211622108212@msgid-missing \
--to=sparky@btinternet.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox