The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bryan Rittmeyer <bryan@ixiacom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: conducting TCP sessions with non-local IPs
Date: Tue, 06 Mar 2001 20:00:14 -0800	[thread overview]
Message-ID: <3AA5B24E.D0ED2206@ixiacom.com> (raw)

Gregory Maxwell wrote:

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

We won't--without getting into the specifics (NDA) we are developing a
TCP/IP load balance tester that needs to act--similtaneously--as many
machines. It is certainly not designed to run on your average LAN, but
rather on a carefully prepared test network using data assigned by a
user who (presumably) has ensured the IPs we are using are not already
assigned to other machines.

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

We have hacks in place for promiscous ARPing on any of the IPs we may
want to use :)

So, if I configure the interface as suggested ("/sbin/ip addr add
10.0.0.0/24 dev eth0") can I really bind to any IP in 10.0.0.0/24 and
conduct TCP sessions (as a client or server) using that IP--assuming all
the ARP, etc, issues are worked out?

Regards,

Bryan
-- 
Bryan Rittmeyer
mailto:bryan@ixiacom.com
Ixia Communications
26601 W. Agoura Rd.
Calabasas, CA 91302

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

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

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=3AA5B24E.D0ED2206@ixiacom.com \
    --to=bryan@ixiacom.com \
    --cc=linux-kernel@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