03-10-2009
do I need to add a line
route add -net 192.168.1.0 255.255.255.0 192.168.1.111
in order to use qe1 to send stuff to 192.168.1.1
or the system automatically understand this?
9 More Discussions You Might Find Interesting
1. IP Networking
hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies
2. Solaris
Hi All, :(:confused:
I have scoured the web and can't find this anywhere.
What I am trying to do is set up a static route through an available gateway on a server, and then test connectivity through TELNET.
I have done this on AIX (I already had this procedure).
On AIX I would use SMIT. ... (7 Replies)
Discussion started by: jeffpas
7 Replies
3. Solaris
Does anyone know how to delete a an ip off the routing table ? i tried route delete 10.0.0.0 and gateway but it still comes back. i have 2 zones sharing one interface. help... (4 Replies)
Discussion started by: 23patrick
4 Replies
4. IP Networking
hi all,
how do i make sure that the new routing should take effect on the os memory right away? what should i run after i add all the new "route add ....".
I have an example below:
bash-2.03# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface... (1 Reply)
Discussion started by: itik
1 Replies
5. Solaris
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies
6. IP Networking
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (1 Reply)
Discussion started by: busyboy
1 Replies
7. Solaris
ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2
inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255
ether 0:14:4f:55:82:9
ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3
inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies
8. UNIX for Advanced & Expert Users
Hello
Hope someone can help with this problem. We are running Solaris 10 with a current kernel patch of 142900-09.
We appear to be getting a serious issue with the routing table as shown below:
Output from netstat -rnv
Destination ....Mask ............Gateway ........Device... (2 Replies)
Discussion started by: gregsih
2 Replies
9. Solaris
Hello All,
Problem is that redundancy doesn't work, probably a routing issue I need to get sorted out When 172.29.11.x net is down, neither node3 nor node4 is trying 172.29.12.x network,The problem lies in network 172.29.13.x
if 172.29.11.x network is down, node3/node4 should route to... (6 Replies)
Discussion started by: nadeemahmed
6 Replies
LEARN ABOUT DEBIAN
oidentd_masq.conf
oidentd_masq.conf(5) File Formats Manual oidentd_masq.conf(5)
NAME
oidentd_masq.conf - oidentd IP masquerading/NAT configuration file.
DESCRIPTION
If you are using IP masquerading or NAT, oidentd can optionally return a username for connections from other machines. Support for this is
specified by calling oidentd with the -m (or --masq) flag and by creating an /etc/oidentd_masq.conf file.
oidentd can also forward requests for an IP masqueraded connection to the machine from which connection originates by way of the -f option.
This will only work if the host to which the connection is forwarded is running oidentd with the -P (proxy) flag, or if the host's ident
daemon will return a valid reply regardless of the input supplied by and the address of the host requesting the info (some ident daemons
for windows do this, maybe others).
FORMAT
<IP Address|Hostname>[/<Mask>] <Ident Response> <System Type>
The first field contains the IP address or the hostname of a machine that IP masquerades through the machine on which oidentd runs. The
mask parameter can be either a network mask or a mask in CIDR notation. A mask of 24 is equivalent to 255.255.255.0, a mask of 16 is
equivalent to 255.255.0.0, etc.
The second field specifies the reply that oidentd will return for lookups to the host matching the IP address specified in the first param-
eter.
The third field specifies the operating system the machine matching the first parameter is running.
EXAMPLES
<Host>[/<Mask>] <Ident Response> <System Type>
192.168.1.1 someone UNIX
192.168.1.2 noone WINDOWS
192.168.1.1/32 user1 UNIX
192.168.1.0/24 user3 UNIX
192.168.0.0/16 user4 UNIX
somehost user5 UNIX
192.168.1.0/255.255.255.0 user6 UNIX
AUTHOR
Ryan McCabe <ryan@numb.org>
http://dev.ojnk.net
SEE ALSO
oidentd(8) oidentd.conf(5)
version 2.0.8 13 Jul 2003 oidentd_masq.conf(5)