New answers tagged ssh-tunneling
I have drawn some sketches The machine, where the ssh tunnel command is typed is called »your host«. Introduction local: -L Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. ssh -L sourcePort:forwardToHost:onPort connectToHost means: connect with ssh to connectToHost, and ...
Assuming you have: A with ip address ip_A B with ip address ip_B C with ip address ip_C From a first terminal connect to the B and set a tunnel to C on ssh (port 10022 is used for the tunnel but it can be anything else): ssh ip_B -L10022:ip_C:22 Then from another terminal, you will be able to connect "directly" to C from A by using the tunnel you just ...
Providing you have already set up your tunnel on A to C via B, then You want #user@D: ssh -N user@A -L 9999:localhost:9999 #user@D: telnet localhost 9999
You are just creating another tunnel, it is not connecting to the existing tunnel. You probably want to connect to "localhost" on machine A instead (instead of C, which is already tunneled through B from A).
If the server you're ssh'ing into has a GUI running you forgo using the -X switch to ssh and set the $DISPLAY variable on the server prior to running the wine application like so: $ DISPLAY=:0.0 wine Artemis.exe If on the other hand you do want to see the GUI via ssh then you could try changing the compression used to hopefully speed things up via SSH ...
This is what you need. #user@A: ssh -N user@B -L 9999:C:9999 When you connect from A with telnet #user@A: telnet localhost 9999
Just another option: the auditd of Linux support system call logging. sudo auditctl -a entry,always -F arch=b64 -S connect Something better compare to strace: you can filter by multiple condition. For example: Audit/Log all failed connect system call: sudo auditctl -a entry,always -F arch=b64 -F success!=0 -S connect Audit/Log all connect system call by ...
strace -e trace=connect -f yourprogram or using a dump file strace -o yourprogram.strace -e trace=connect -f yourprogram
In search of restarting the sshd after updating AuthorizedKeysFile in /etc/ssh/sshd_config RSAAuthentication yes PubkeyAuthentication yes AuthorizedKeysFile %h/.ssh/authorized_keys I got here with exact same error Which guided me to install: sudo apt-get install openssh-server sudo initctl reload-configuration sudo service ssh start ...
If you have a low bandwidth I recommend compression of the video stream: ssh USER@REMOTEHOST ffmpeg -an -f video4linux2 -s 640x480 -i /dev/video0 -r 10 -b:v 500k -f matroska - | mplayer - -idle -demuxer matroska where -an turns of audio encoding. If you want audio, replace -an with -f alsa -ac 1 -i hw:3 (where hw:3 could also be hw:0 or hw:1, … See ...
You want to do it the other way round (reverse of your set-up). Host D -> Host C:8003 forwards to --> Host B:8002 forwards to --> Host A:8001 -> Your application You only have 1 ssh forward to establish. On hostC ssh -L 8003:hostA:8001 user@hostB then to test on hostD by accessing hostC:8003
You can run a proxy on Computer A that computer B would then connect to in order to access the internet through Computer A. Something like this +----------+ +-----------+ | |+----SSH+-->| | | A | | B | |+--------+| | | ...
Top 50 recent answers are included