Sponsored Content
Full Discussion: Network routing
Operating Systems Solaris Network routing Post 302920396 by ghostdog74 on Thursday 9th of October 2014 08:15:54 AM
Old 10-09-2014
Network routing

hi,
not an expert in Solaris networking so would like to ask your opinions

Say i want to configure packet routing from source 10.126.120.130 (A) to destination 10.214.140.9 (B).

I configured it this way (shown in netstat -rn) on (B)

Code:
Destination        Gateway                 Interface
=======          =======                 ======
10.0.0.0           10.214.140.1
10.214.0.0        173.20.50.65
10.214.140.0     10.214.140.9           vmnet1

where vmnet1 has interface address 10.214.140.9.
May I know if I have configured it properly?
I want packets to go from (A) to (B).

thanks
 

9 More Discussions You Might Find Interesting

1. IP Networking

Routing Network Traffic With Mandrake

I am running Mandrake 8.0 (KDE ver 2.1.1) on a machine with 2 NICs. This is a college project. I am attempting to configure this machine as a firewall, and to pass packets from one network to another. Eth0 is on my external network. Eth1 is on my internal network. I set the gateway in "netconf"... (1 Reply)
Discussion started by: Deuce
1 Replies

2. UNIX for Dummies Questions & Answers

Need help to configure routing on home network

I have a Windows laptop and a Sparc desktop. I'm trying to toy around with routing. If have always on broadband from BT. My router ipaddress is: 192.168.1.1 This router uses DHCP. My Laptop Ip is as follows: Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . :... (2 Replies)
Discussion started by: Kongowea
2 Replies

3. IP Networking

ssh server is attachable from local network not from another network

hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies

4. Solaris

Network cards - Routing

Hi all I hate networking, I hate everything to do with it. Its something I do in anger in one contract, then forget. This is more of a question / than a problem. So, on a solaris 10 server, using older qfe cards, Ive got a sun truck with 4 nics (qfe0,3,4,7), and a ipmp pair (hemo0,qfe1).... (2 Replies)
Discussion started by: sbk1972
2 Replies

5. IP Networking

Routing traffic problem between 3G and Office Lan Network

Hi, I would like to ask some networking solution regarding my work LAN and 3G usb network problem. I want to route my internet traffic to the 3G network and sometimes connect to some of my work network for ssh to configure some workstation or print something. Currently my problem is i can't... (0 Replies)
Discussion started by: jao_madn
0 Replies

6. IP Networking

Test network routing algourithm

hi, I've wrote my own network routing algorithm in java, now i wanna test it and see if it works correctly, also i wanna test it's performance in comparison with other network routing algorithms like RIP. can anyone tell me how can i do this? is there any simulator or something for network routing... (0 Replies)
Discussion started by: gongotar
0 Replies

7. Solaris

No network cable But Network interface is UP and Running

I've one Netra 240 After changing main board and system configuration card reader, Network is not accessible any more, Network interfaces are always UP and Running even when there is no cable connected to Network interfaces. I tried to restart and plumb/unplumb with no luck. ifconfig -a... (7 Replies)
Discussion started by: samer.odeh
7 Replies

8. IP Networking

Test Network Routing Issues (FREEBSD and RHEL)

Hello, I'm attempting to setup a test network with a client-server based architecture using a proprietary application. The client works by communicating with the server on separate links (typically cellular connections) and then initiates a tunnel over each active link. However, in place of the... (0 Replies)
Discussion started by: shadyuk
0 Replies

9. Red Hat

Network becomes slow and return fast only after restart network

Hi, I have 2 machines in production environment: 1. redhat machine for application 2. DB machine (oracle) The application doing a lot of small read&writes from and to the DB machine. The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
XNSROUTED(8)						      System Manager's Manual						      XNSROUTED(8)

NAME
XNSrouted - NS Routing Information Protocol daemon SYNOPSIS
/sbin/XNSrouted [ -s ] [ -q ] [ -t ] [ logfile ] DESCRIPTION
XNSrouted is invoked at boot time to manage the Xerox NS routing tables. The NS routing daemon uses the Xerox NS Routing Information Pro- tocol in maintaining up to date kernel routing table entries. In normal operation XNSrouted listens for routing information packets. If the host is connected to multiple NS networks, it periodically supplies copies of its routing tables to any directly connected hosts and networks. When XNSrouted is started, it uses the SIOCGIFCONF ioctl to find those directly connected interfaces configured into the system and marked ``up'' (the software loopback interface is ignored). If multiple interfaces are present, it is assumed the host will forward packets between networks. XNSrouted then transmits a request packet on each interface (using a broadcast packet if the interface supports it) and enters a loop, listening for request and response packets from other hosts. When a request packet is received, XNSrouted formulates a reply based on the information maintained in its internal tables. The response packet generated contains a list of known routes, each marked with a ``hop count'' metric (a count of 16, or greater, is considered ``infi- nite''). The metric associated with each route returned provides a metric relative to the sender. Response packets received by XNSrouted are used to update the routing tables if one of the following conditions is satisfied:(1) No routing table entry exists for the destination network or host, and the metric indicates the destination is ``reachable'' (i.e. the hop count is not infinite). (2) The source host of the packet is the same as the router in the existing routing table entry. That is, updated information is being received from the very internetwork router through which packets for the destination are being routed.(3) The existing entry in the routing table has not been updated for some time (defined to be 90 seconds) and the route is at least as cost effective as the current route.(4) The new route describes a shorter route to the destination than the one currently stored in the routing tables; the metric of the new route is compared against the one stored in the table to decide this. When an update is applied, XNSrouted records the change in its internal tables and generates a response packet to all directly connected hosts and networks. Routed waits a short period of time (no more than 30 seconds) before modifying the kernel's routing tables to allow possible unstable situations to settle. In addition to processing incoming packets, XNSrouted also periodically checks the routing table entries. If an entry has not been updated for 3 minutes, the entry's metric is set to infinity and marked for deletion. Deletions are delayed an additional 60 seconds to insure the invalidation is propagated to other routers. Hosts acting as internetwork routers gratuitously supply their routing tables every 30 seconds to all directly connected hosts and net- works. Supplying the -s option forces XNSrouted to supply routing information whether it is acting as an internetwork router or not. The -q option is the opposite of the -s option. If the -t option is specified, all packets sent or received are printed on the standard output. In addition, XNSrouted will not divorce itself from the controlling terminal so that interrupts from the keyboard will kill the process. Any other argument supplied is interpreted as the name of file in which XNSrouted's actions should be logged. This log contains informa- tion about any changes to the routing tables and a history of recent messages sent and received which are related to the changed route. SEE ALSO
``Internet Transport Protocols'', XSIS 028112, Xerox System Integration Standard. idp(4P) 4.3 Berkeley Distribution November 1, 1996 XNSROUTED(8)
All times are GMT -4. The time now is 10:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy