> 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
Jeremy Jackson wrote:
> What the hell kind of monster are you making? There's got to be another way.
heh. As I mentioned in my other response, we're doing TCP/IP load
balance testing--so we need one linux system to act as many hosts. The
only solution, short of using bind/connect/accept/etc
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
Mike Fedyk wrote:
> > [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"?
What the hell kind of monster are you making? There's got to be another way.
-
To unsubscribe from this list:
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
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
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
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,
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,
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
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
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
Mike Fedyk wrote:
[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"?
What the hell kind of monster are you making? There's got to be another way.
-
To unsubscribe from this list: send the line
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
Jeremy Jackson wrote:
What the hell kind of monster are you making? There's got to be another way.
heh. As I mentioned in my other response, we're doing TCP/IP load
balance testing--so we need one linux system to act as many hosts. The
only solution, short of using bind/connect/accept/etc
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:
16 matches
Mail list logo
