[TriLUG] Choosing the right pipe

Jeff Bollinger jeff01 at email.unc.edu
Mon Oct 28 15:53:54 EST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Of course you can't ssh TO a network, but you can SSH INTO a network,
like in my original message below.  Route displays an asterisk for each
network under "Gateway", which is defined as the "default".   Is there a
change I can make to /etc/resolv.conf that will always make eth0 use a
particular gateway, and eth1 use another?

Thanks,
Jeff

Jeremy Portzer wrote:
| On Mon, 2002-10-28 at 15:41, Jeff Bollinger wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Say I've got two different NICs, each connecting to a different network.
|>~ If I want to SSH into network A (a private network) how do I tell SSH
|>to run through eth0 (or the first NIC)?
|
|
| Well, you can't ssh to a *network* -- you ssh to a host (computer).
| Based on the IP address of the destination computer, the kernel routing
| tables will pick the appropriate "pipe".  (If there's more than one
| possible route to a destination, things become much more complex.)
|
| Type "route" at a shell prompt to see where the kernel is routing things
| now.  If things appear to be configured wrong, you'll need to check the
| IP address, subnet mask, and other settings for each NIC.
|
| --Jeremy
|
| _______________________________________________
| TriLUG mailing list
|     http://www.trilug.org/mailman/listinfo/trilug
| TriLUG Organizational FAQ:
|     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html

- --
Jeff Bollinger
University of North Carolina
IT Security Analyst
105 Abernethy Hall
mailto: jeff_bollinger at unc dot edu


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9vaPivoVlxVBmgsURAjFuAJ9tpq5a0HextNL2z7vHzSQeSYfSOwCg9Ba2
C4aASrrUHX7w2I2eQBHw5dQ=
=a1SN
-----END PGP SIGNATURE-----




More information about the TriLUG mailing list