All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@linuxpower.cx>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Bryan Rittmeyer <bryan@ixiacom.com>, linux-kernel@vger.kernel.org
Subject: Re: conducting TCP sessions with non-local IPs
Date: Tue, 6 Mar 2001 20:55:17 -0500	[thread overview]
Message-ID: <20010306205517.H3372@xi.linuxpower.cx> (raw)
In-Reply-To: <3AA54902.AFF8550@ixiacom.com> <20010306170551.D2244@xi.linuxpower.cx> <3AA592FF.5107E508@matchmail.com>
In-Reply-To: <3AA592FF.5107E508@matchmail.com>; from mfedyk@matchmail.com on Tue, Mar 06, 2001 at 05:46:39PM -0800

On Tue, Mar 06, 2001 at 05:46:39PM -0800, Mike Fedyk wrote:
> Gregory Maxwell wrote:
> > 
> > On Tue, Mar 06, 2001 at 12:30:58PM -0800, Bryan Rittmeyer wrote:
> > > Hello linux-kernel,
> > >
> > > Is there any way to conduct TCP sessions (IE have a userland process
> > > connect out, or accept connections) using non-local IPs? By "non-local"
> > > I just mean IPs that aren't assigned to an interface, but do fall into
> > > the network range of a running interface (so netmask, gateway, etc are
> > > "known").
> > >
> > > For example, I want to bring up an interface for 10.0.0.0/255.255.255.0
> > > and assign it IP 10.0.0.1 Then, I want a process to accept TCP
> > [snip]
> > 
> > /sbin/ip addr add 10.2.0.0/24 dev eth0
> > 
> > Tada
> How would you deal with the other computer responding to the host "port not
> reachable"?

I didn't pick-up on the fact that you planned on have other computers
listening with those addresses.

This won't work without support from your routing device if you actually
have hosts on the addresses, just because of ARP.

You can make this work, if, you can control and configure the router
  1. You can configure your router to direct the needed ports to your Linux
	box and not the real hosts. (Linux can do this)

If you can firewall on the victim boxes, you could block their 'not
reachable' reply, but that doesn't solve ARP. You could probably make a
trivial change to Linux and run it in promiscuous mode to achieve this. It's
more likely the first will be a better option for you.

What are you doing anyways? :)

  reply	other threads:[~2001-03-07  1:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 20:30 conducting TCP sessions with non-local IPs Bryan Rittmeyer
2001-03-06 22:05 ` Gregory Maxwell
2001-03-07  1:46   ` Mike Fedyk
2001-03-07  1:55     ` Gregory Maxwell [this message]
2001-03-07  2:15     ` Jeremy Jackson
  -- strict thread matches above, loose matches on Subject: below --
2001-03-07  3:59 Bryan Rittmeyer
2001-03-07  4:00 Bryan Rittmeyer
2001-03-07  6:50 ` David

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=20010306205517.H3372@xi.linuxpower.cx \
    --to=greg@linuxpower.cx \
    --cc=bryan@ixiacom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    /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.