-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linux Pquter wrote:
>My first interface is at 192.168.10.1 255.255.255.0.
>Then I added a second nic, at 192.168.10.2
>
>I don't get it. I didn't expect to see the destination
>changed from an address to the network and the
>corresponding interface from eth0 to eth1.
I think you're running into a common misconception. First, short
answer to the above is that you can hardcode the gateway using the
route command, and fix the immediate problem. But ...
>I've added a second nic for throughput to the clients. Some will
>connect to the first address, others to the second. How do I get a
>connection to utilize only one nic? For example, for a client that
>connects to 10.1, i'd want the server response to go out from eth0,
>and for a client that connects to 10.2, the response to go out from
>eth1.
That won't work. What you want to do is load balance, I presume, but
this isn't the way to do it. To understand why, you need to study up
on how TCP/IP works. What will happen is that as long as both
interfaces have a route to all clients, your outbound traffic will
only use one interface, and you won't necessarily be able to even
predict which one that will be, as you saw above. I am not qualified
to explain how you _could_ do it, though I suspect you might be able
to fake it with some iptables trickery.
- -d
- --
David Talkington
PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp
- --
http://setiathome.ssl.berkeley.edu/pale_blue_dot.html
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQA/AwUBPGH1eb9BpdPKTBGtEQJBuACdFT0fMrAaFanxyyFBPb7MS0UzVVsAmwex
C4K6hfQCrjcVL11xws3xSaEC
=ihd/
-----END PGP SIGNATURE-----
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
