10 More Discussions You Might Find Interesting
1. IP Networking
Add explicit route to 10.128.255.41/32 , gateway: 10.128.201.254
if not working, please try gateway through management port: 10.128.55.254
Just want to double confirm if this would be the correct command
#route add -net 10.128.255.41/32 10.128.201.254
And if didnt work
#route add... (1 Reply)
Discussion started by: Thilagarajan
1 Replies
2. Solaris
Hi Solaris Experts,
I am trying to add a routing table entry on our 5.1 Generic_144488-12 sun4v sparc Solaris 10 SUNW,SPARC-Enterprise-T5220 so that it is possible to ping 10.56.9.34 node
# netstat -rnv
IRE Table: IPv4
Destination Mask Gateway Device Mxfrg Rtt Ref
Flg Out In/Fwd ... (2 Replies)
Discussion started by: gjackson123
2 Replies
3. Solaris
I need to add a new route on solaris10 machine.
I want that all traffic on the 23 port (telnet) use 192.168.200.1 gateway.
How I do ?
Thank you in advance. (1 Reply)
Discussion started by: arfry
1 Replies
4. Solaris
Hi need to add 2 routes, one on each server.
I know the route add comand but I have always been given the parameters to put in.
I need a route in each of the 2 following servers to be able to ping and ssh between them. But how do i know which netmask to put in the route add command ?
In... (6 Replies)
Discussion started by: vettec3
6 Replies
5. Solaris
Hey Guys:
I am trying to add a route for assign a network interface to the traffic to/from a specific net, but allways to get the same system message : network is unreacheable
root@ColectorDMSCNT # route add net 200.44.46.0/24 161.196.84.196 1
add net 200.44.46.0/24: gateway... (2 Replies)
Discussion started by: aggadtech08
2 Replies
6. Solaris
Hi,
I am trying to add route command in Solaris 10 machine in the following fashion:
route add -host 10.8.112.10 180.144.1.250 -interface lo0:1
this command fails with an error "lo0:1: bad value"
I want to add a route to 10.8.112.10 that picks 180.144.1.250 as the gateway via the... (3 Replies)
Discussion started by: sudhir_shet
3 Replies
7. IP Networking
I have a system that i want to reach via a vpn created vi a fierwall.The fierwall in an other system.
The ip i am trying to get to is 172.16.4.48
I need to get to it via the hme1 interface.
The vpn gateway has this ip 172.30.50.1
I need to clean up the routing table and make this work; or is it... (5 Replies)
Discussion started by: waterboy
5 Replies
8. HP-UX
Hi,
My H-UX box has the GW pointing to 10.10.10.1 and I need add it a new route pointing to 192.168.80.x with the GW 10.10.10.13
I tried with:
#route add 192.168.80.2 255.255.255.255 10.10.10.13
but I get: add net 192.168.80.0: gateway 255.255.255.0: Network is unreachable
I tried with... (4 Replies)
Discussion started by: efrenba
4 Replies
9. IP Networking
I have two networks connected by cisco routers. My first subnet is 192.168.0.0 and my second is 192.168.1.0.
My SCO unix machine is on the 192.168.1.0 subnet with an IP of 192.168.1.231. It can see the entire .1.0 subnet but nothing on the other network.
My cicso router(gateway) to the other... (6 Replies)
Discussion started by: agoodrich
6 Replies
10. AIX
Hello ,
We have 3 rs/6000 server's running aix on our local network, so each time I try to ping one of these servers we get a "network is down" error , I've been instructed to use to route add command which is ...
#route add server.ip router.ip
after this the ping command works fine ,... (6 Replies)
Discussion started by: cubicle^dweller
6 Replies
AUSCOPE(1) General Commands Manual AUSCOPE(1)
NAME
auscope - Network Audio System Protocol Filter
SYNOPSIS
auscope [ option ] ...
DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio
server.
auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not
installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or,
you can invoke auscope as
perl auscope [ option ] ...
assuming the Perl executable is in your path.
To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio
server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati-
cally biased by 8000. The output port defaults to 0 and the input port defaults to 1.
ARGUMENTS
-i<input-port>
Specify the port that auscope will use to take requests from clients.
-o<output-port>
Determines the port that auscope will use to connect to the audio server.
-h<audio server name>
Determines the desktop machine name that auscope will use to find the audio server.
-v<print-level>
Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater
output detail.
EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network
host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect
to the audio server on port 8000.
Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the
audio server via the TCP/IP network host tcphost and port 8001:
auscope -i1 -o0 -hmcxterm
auplay -audio tcp/tcphost:8001 dial.snd
In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the
network host tcphost, while displaying its graphical interface on another server labmcx:
auscope -i1 -o0 -hmcxterm -v1
autool -audio tcp/tcphost:8001 -display labmcx:0.0
SEE ALSO
nas(1), perl(1)
COPYRIGHT
Copyright 1994 Network Computing Devices, Inc.
AUTHOR
Greg Renda, Network Computing Devices, Inc.
1.9.3 AUSCOPE(1)
