Skip to contentSkip to conversation

conducting TCP sessions with non-local IPs

DISCUSSION Bryan Rittmeyer 2 participants 2 messages Mar 7, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines · Gregory Maxwell

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.

Quoted 2 lines

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

Signature · 5 lines
Bryan Rittmeyer
mailto:[email protected]
Ixia Communications
26601 W. Agoura Rd.
Calabasas, CA 91302
#1 lore raw
Quoted 4 lines

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?

hostA: ip a a 10.0.0.0/24 brd + dev lo
hostB: ip r a 10.0.0.0/24 dev eth0

hostB: telnet 10.0.0.27
<connected as normal>

hostB: ssh 10.0.0.91
<connected as normal>

'tis a little magic I like. nothing special needed anywhere. does that help?

-d