![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| DHCPD, Multiple interfaces, Single Subnet | vertigo23 | IP Networking | 0 | 10-26-2005 06:42 PM |
| Interfaces do not failover | StorageGuy | SUN Solaris | 5 | 08-06-2005 06:39 PM |
| multiple interfaces with apache? | cerberusofhnsg | UNIX for Dummies Questions & Answers | 2 | 08-09-2003 12:32 AM |
| interfaces | emsakopa | UNIX for Dummies Questions & Answers | 1 | 01-16-2003 03:44 PM |
| Multiple Interfaces and Routes | diemos | IP Networking | 3 | 06-22-2001 10:14 PM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Routes are not defined for a NIC but for a destonatin network.
Thus you can have multiple routing table entries for diffrent networks. i.,e. on my machine , I have a default route goes through my frontend network. And then a summary route for one of the Class C network which gets me to the NAS and other devices. and then some other routes for the management networks. I have 3 ethernet cards with diffrent ip address in them. Regds, Kaps |
|
||||
|
Expanding on what kapilraj already explained:
A route is basically a rule "send everything destined to network <destination> to IP-address <gateway>". This gateway can be one of your network interfaces or the address of a remote machine. In the first case you tell your own machine how to handle a (class of) network packet(s) in the latter you rely on the remote machine knowing how to further dispatch your packets. Usually this is a router whichs purpose is exactly that. A special case of a route is the "default route", which is used by your machine as a last resort - "if everything else doesn't apply follow this rule". In a machine with one NIC there are usually two routes: The first one tells the machine to send everything destined to the "own network" (the network the own IP-address is part of) to the own NIC, the other - default - route tells the machine to send everything else to the next router (which hopefully knows how to deal with it). In a machine with two (or more) interfaces you set up routes similar to the first one in the last example for every interface. At last you set up a default route to one of the routers on one of the networks connected to that way. Every traffice not addressed to the networks your machine already has a leg in will go there. Of course you can set up routes for specific networks and this way enforce that some traffic goes over a specific interface. The easiest way to get the idea is to draw a (however simple) picture with the networks and the routers and visualize your rules before implementing them. bakunin |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|