|
|||||||
| Forums | Search Forums | Register | Forum Rules | Man Pages | Albums | FAQ | Members | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
||||
|
||||
|
Just wanted to understand what is the logic being used by Solaris(kernel) to transmit data/traffic on physical interfaces. I have seen most of the time traffic is being sent to interface ce0 and sometime to ce1. I have removed ip address from below command for some reason. Code:
netstat -rn Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ------ --------- a.b.c.d x.x.x.1 U 1 537552 ce1 a.d.e.d x.x.x.2 U 1 809673 ce0 Trying to figured out the logic/algorithm used to send traffic/data. i have gone through couple of document and understand, when system transmit a packet, it must locate the "BEST" interface over which to sent it. but not so cleared about the algorithm or logic behind,since most of the time it uses ce0 and sometimes it use ce1 how? Your early response will be appreciated with detailed explanation about this logic. Thanks Nadeem
Last edited by bakunin; 10-23-2012 at 02:24 PM.. |
| Sponsored Links | ||
|
|
#2
|
|||
|
|||
|
From the routing manpage... Code:
Routing Algorithm
The routing table entries are of three types:
+ Entries for a specific host.
+ Entries for all hosts on a specific network.
+ Wildcard entries for any destination not matched by entries of
the first two types.
To select a route for forwarding an IP packet, the network facilities
select the complete set of "matching" routing table entries from the
routing table. A routing table entry is considered a match, if the
result of the bit-wise AND operation between the netmask in the
routing entry and the IP packet's destination address equals to the
destination address in the routing entry.
The network facilities then select from the set the routing entries
that have the longest netmask. The length of a netmask is defined as
the number of contiguous 1 bits starting from the leftmost bit
position in the 32-bit netmask field. In other words, the network
facilities select the routing entry that specifies the narrowest range
of IP addresses. For example, the host route entry that has a
destination/netmask pair of (147.253.56.1, 0xffffffff), is more
specific than the network route entry that has a destination/netmask
pair of (147.253.56.0, 0xfffffe00), therefore the network facilities
select the host route entry. The default route by default has a
destination/netmask pair of (0,0). Therefore the default route matches
all destinations but it is also the least specific. The default route
will be selected only if there is not a more specific route.
There may still be multiple routing entries remaining. In that case
the IP packet is routed over the first entry displayed by netstat -r.
Such multiple routes include:
+ Two or more routes to a host via different gateways.
+ Two or more routes to a network via different gateways.
+ Two default routes.
A superuser can change entries in the table by using the route command
(see route(1M), or by information received in Internet Control Message
Protocol (ICMP) redirect messages. |
| Sponsored Links | ||
|
|
#3
|
|||
|
|||
|
There are basically two possible situations: network interfaces attached to different networks and network interfaces attached to the same network.
If the network interfaces are attached to different networks, the routing table controls what is sent using which interface. The contents of the routing table may or may not be further controlled by routing protocols (RIP, OSPF, EGP, ...). This is like it is in every IP-host. If there are several interfaces pointing into one network, per default Solaris employs all the interfaces using a round-robin algorithm, if i remember correctly. It is also possible to configure several interfaces into the same network to form aggregated links: etherchannels, configured for either additional bandwidth or high-availability (or both), etc.. I hope this helps. bakunin |
| The Following User Says Thank You to bakunin For This Useful Post: | ||
nadeemahmed (11-08-2012) | ||
|
#4
|
|||
|
|||
|
Thanks for the prompt response
![]() |
| Sponsored Links | ||
|
![]() |
| Tags |
| solaris |
| Thread Tools | Search this Thread |
| Display Modes | |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Route all traffic between two ethernet interfaces | kontozebyoszuka | IP Networking | 1 | 10-27-2010 11:37 AM |
| list of physical net interfaces | busyboy | Solaris | 8 | 01-20-2010 03:06 PM |
| IPMP on 2 physical interfaces | Sunb3 | Solaris | 5 | 02-16-2009 01:52 PM |
| Configuring networking interfaces on Solaris 10 | annointed3 | UNIX for Dummies Questions & Answers | 7 | 03-02-2006 08:55 PM |
| adding interfaces in solaris 9 | BG_JrAdmin | UNIX for Dummies Questions & Answers | 2 | 03-28-2005 10:18 AM |
|
|