09-08-2010
Oooooh..but then I'd have to have physical access to the .69 machine right? I need to be able to hop through the .69 machine to the .107 machine.
I hope that makes sense.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have tried the following:
on PC1 (win xp) I have created ssh connection with port forwarding
(local 8888 to remote 8888) to server1.
>From server1 I have created another ssh connection with port
forwarding to server2(local 8888 to remote 1521).
When I try to connect to oracle... (3 Replies)
Discussion started by: goran00
3 Replies
2. UNIX for Advanced & Expert Users
Hi all
question -
there are 2 servers A + B. server A is connected to the internet and running a squid proxy server - server B is behind a firewall. I can ssh from A to B but not from B to A. I need internet access on B to update some files. I thought I could use some sort of ssh tunnel to... (1 Reply)
Discussion started by: silvaman
1 Replies
3. Filesystems, Disks and Memory
Hello Folks,
Im trying to pass the NFS Shared data through the SSH tunnel. Following are the Steps for my Executions:
A) Commands Executed on Server (NFS Server + SSHD Server running)
i) share -F nfs -o rw=<NFS Server IP> /home
ii) Start the NFS Server Services and SSHD Services.
... (3 Replies)
Discussion started by: ImpeccableCode
3 Replies
4. Cybersecurity
Hi,
from my workplace we use a proxy to connect to the outside world, including external ssh servers.
The problem is that the server is seeing the connection coming from the proxy and knows nothing about the client behind it. The ssh connection itself works fine, but x-forwarding does not work as... (1 Reply)
Discussion started by: vampirodolce
1 Replies
5. IP Networking
Hi Linux/Unix Guru,
I am setting Linux Hopping Station to another different servers.
My current config to connect to another servers is using different port to connect.
e.g
ssh -D 1080 -p 22 username@server1.com
ssh -D 1081 -p 22 username@server2.com
Now what I would like to have... (3 Replies)
Discussion started by: regmaster
3 Replies
6. Infrastructure Monitoring
Performing UDP tunneling through an SSH connection
Found this while looking for a way to temporarily forward SNMP requests across otherwise disconnected networks. Might be useful for someone else, too. (1 Reply)
Discussion started by: pludi
1 Replies
7. IP Networking
Hello my friends , i am totally stuck in ssh port forwarding topic
i had learn iptables and other networking topic without any problem but ssh port forwarding is headache
1. local port = what is this ? is this incoming traffic or outgoing traffic
2. remote port = same as above
3. dynamic... (2 Replies)
Discussion started by: rink
2 Replies
8. IP Networking
Hi,
I'm trying to connect ftp over ssh port forwarding to a sever(UnixC) behind FireWall(F/W). here's my env and question.
UnixA(SSH Client) ----F/W ---- UnixB(SSH Svr) ---- UnixC (FTP, 21)
UnixA wants to connect ftp service of UnixC via SSH port forwarding on UnixB.
Unix A,... (3 Replies)
Discussion started by: hanyunq
3 Replies
9. IP Networking
Here's a situation:
I do all my work on a Mac. I have mysql installed on my mac.
1. There's a certain linux server 'server01' that provides access to
another linux server 'server02' via a pseudo terminal
So, to ssh into 'server02', I do this from my mac:
ssh -t server01... (1 Reply)
Discussion started by: imperialguy
1 Replies
10. UNIX for Dummies Questions & Answers
I want to perform ssh tunnelling for which I have been using PuTTy. Config is as follows:
Host IP: 172.XX.XX.111Port: 22Tunnel setting source port: 19005Destination: 172.XX.XX.40:1521After entering my user ID and password, I am able to see in my command prompt that 127.0.0.1:19005 is listening.... (1 Reply)
Discussion started by: aakashsoor
1 Replies
LEARN ABOUT OPENSOLARIS
auscope
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)