From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Two NICS with same IP and same client IP
Date: Wed, 2 Feb 2005 17:29:32 -0500 [thread overview]
Message-ID: <20050202222932.GA1803@bender.817west.com> (raw)
In-Reply-To: <186AC876521E0F46BDE77079A6567FD0F0DD97@la-ncc-ms1nsabb.losangeles.afspc.ds.af.mil>
On Wed, Feb 02, 2005 at 02:22:41PM -0800, Hudson Delbert J Contr 61 CS/SCBN wrote:
> jason,
>
> sorry, but your gonna' hear this anyway...but its not negative..
> i just wanna know why?
>
> okay...here is what i'm sure will think is a dumb question.
>
> why not make life simple for all concerned [servers, clients and routers, too...]
>
> re-numbering the subnets...or just one and --- voila! problem gone !!!!
>
> this might be too simplistic for this list (he! he! he!) but lets say...
>
> eth0@server = 192.168.100.0/24
> eth0@client = 192.168.100.1/24
>
> eth1@server = 172.16.1.0/24
> eth1@client = 162.16.1.1/24
>
> or whatever...whats the problem?
>
> i think also the statement below may be have some validity
> if this is as easy as i think it is.
>
> where's the difficiulty.
>
> complex is bad.
> simple is good.
i agree with you one hundred thousand gabillion (is that a
glavin?) percent. judging from the posts in this thread--i believe
properly configuring IP is an unacceptable solution for the OP.
-j
--
"Ah, good ol' trustworthy beer. My love for you will never die."
--The Simpsons
next prev parent reply other threads:[~2005-02-02 22:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 22:22 Two NICS with same IP and same client IP Hudson Delbert J Contr 61 CS/SCBN
2005-02-02 22:29 ` Jason Opperisano [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 16:47 Gary W. Smith
2005-02-02 16:51 ` Raphael Jacquot
[not found] ` <27594E8BA9D5CA458F5EF87D88B6B48F019948@pxtvjoexd01.pxt.primeexalia.co m>
2005-02-02 16:57 ` Hervé
2005-02-02 16:57 ` Hervé
[not found] ` <18348031.1107363459685.JavaMail.rct@kale>
2005-02-02 18:41 ` Bob Tellefson
2005-02-02 20:47 ` Hervé
2005-02-02 16:26 Hudson Delbert J Contr 61 CS/SCBN
2005-02-02 16:49 ` Tom Eastep
2005-02-02 9:35 Hervé
2005-02-02 9:48 ` Raphael Jacquot
[not found] ` <5172.57.66.65.39.1107338261.squirrel@57.66.65.39>
2005-02-02 10:28 ` Raphael Jacquot
2005-02-02 14:12 ` Jason Opperisano
2005-02-02 14:32 ` Hervé
2005-02-02 14:41 ` Jason Opperisano
2005-02-02 16:53 ` Hervé
2005-02-02 14:44 ` Raphael Jacquot
2005-02-02 16:40 ` Hervé
2005-02-02 16:22 ` Tom Eastep
2005-02-02 20:56 ` Jason Opperisano
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=20050202222932.GA1803@bender.817west.com \
--to=opie@817west.com \
--cc=netfilter@lists.netfilter.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.