From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Multihomed Problem
Date: Tue, 11 Dec 2007 16:04:10 -0600 [thread overview]
Message-ID: <475F095A.7040003@riverviewtech.net> (raw)
In-Reply-To: <475EFFF8.1010606@nwcascades.com>
On 12/11/07 15:24, Jack Lauman wrote:
> I have a multihomed linux box set up as follows:
>
> eth0: 192.168.100.1
> eth1: 192.168.1.1
>
> I need to be able to print from a workstation at 192.168.100.2 to a
> Xerox workstation at 192.168.1.30
Ok...
> How can I make this work?
Seeing as how (I'm betting) you can not set up routing on the Xerox, you
will probably need to NAT the traffic from the 192.168.100.x network to
appear as if it is from 192.168.1.1. This way when any system on the
192.168.100.x network tries to talk to the Xerox, it will think that
192.168.1.1 is talking to it and thus be able to reply back.
Grant. . . .
next prev parent reply other threads:[~2007-12-11 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 21:24 Multihomed Problem Jack Lauman
2007-12-11 22:04 ` Grant Taylor [this message]
2007-12-11 22:30 ` Matt Zagrabelny
2007-12-11 22:55 ` Grant Taylor
2007-12-12 19:09 ` Jack Lauman
2007-12-12 19:35 ` Matt Zagrabelny
2007-12-13 0:21 ` Grant Taylor
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=475F095A.7040003@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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