similar to: [Bug 1387] New: Support for tunneling FTP

I've setup a lab to test the new tunneling options in the latest openssh. Things work well... for a while... then the tunnel goes unidirectional. openssh-SNAP-20060122.tar.gz lab1 config: # uname -a FreeBSD lab1 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Fri Jan 13 13:01:17 EST 2006 root@:/usr/src/sys/i386/compile/SMP i386 # cat /etc/sysctl.conf | egrep -v '(^#|^$)'

I am in the network that is behind the Zscaler firewall. Virtually all ports except 80 and 443 are closed. ssh through any of ports 80 and 443 is disallowed based on protocol content analysis. It would be nice if OpenSSH would have some features that would allow the user to break out of such network. I suggest that OpenSSH adds the SSL tunneling feature: 1. The server would have the

Hi I've been looking at a both openssh and couple of commercial SSH implementations(F-Secure and ssh comm.). The one thing I see as missing is the "nice-to-have" feature of FTP specific port forwarding. The commercial implementations allows a syntax of "-L ftp/<someport>:..." which does some "automagical" forwarding of the data channel "under the

https://bugzilla.mindrot.org/show_bug.cgi?id=2272 Bug ID: 2272 Summary: Global "PermitTunnel Yes" required to connect to a tunnel Product: Portable OpenSSH Version: 6.6p1 Hardware: amd64 OS: Linux Status: NEW Severity: major Priority: P5 Component: sshd

Hello List, I'm not enterelly sure that I'm on the rist place to ask this question, sorry if not. The question is simple, *how to test simply a ssh tunnel ?* I just want to make sure the the tunnel i'm opening is letting information goes through it without problem, and I want to avoid any other point of failure when testing. for example let's say I run ssh -L

https://bugzilla.mindrot.org/show_bug.cgi?id=2255 Bug ID: 2255 Summary: tunneling with -W does not report non 0 exit codes on failure even with ExitOnForwardFailure=yes Product: Portable OpenSSH Version: 6.6p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority:

http://bugzilla.mindrot.org/show_bug.cgi?id=1295 Summary: [PATCH] Transparent proxy support on Linux Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org ReportedBy:

If people haven't seen it, there's a pretty nice Java SSH client called MindTerm: http://www.mindbright.se/mindterm/ One of the things they did is add some hacks to make FTP tunneling over SSH trivial. This client looks at the data being forwarded over port 21 (ftp control port), and looks for the FTP PORT and PASV commands used to establish

https://bugzilla.mindrot.org/show_bug.cgi?id=1552 Summary: Patch to log tunnel information Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jblaine at

Hi, I have setup a tunnel from server A to server B across WAN by running "ssh -l user_X -L port_A:server_B:port_B server_C -N". Server B is in a private network, so I have to establish the tunnel via server C, which is in the same LAN with B but has a public IP. The problem is, every time I start the tunnel on server B, the tunnel process will die nearly two hours later. And it

https://bugzilla.mindrot.org/show_bug.cgi?id=2265 Bug ID: 2265 Summary: ServerAlive{Interval,CountMax} ignored if using an active -R or -L tunnel Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component:

Hi, For Ethernet and others, we have a configuration file inside /etc/sysconfig/newtork-script/ like ifcfg-ethx where we specify ip address, mask, type etc... For GRE tunneling, how can I specify the parameters for tunneling device, so that I ifup-tunnel will automatically read and start the interface and I don't have to write the below scripts in my start-up file. ip tunnel add netx mode

Hi (I'm not subscribed, please, cc) I've got an ethernet level ssh tunnel to a remote system. That system is running a terminal server, so, that tunnel is the only connection, I've got. The terminal server is connected via a serial and an ethernet cable to a test board and is configured to bridge that ethernet connection to my tunnel. I can then trigger that test board to start a

Hi All. Can anyone tell what is sip tunneling ahd how its works want a make a sip tunnel between to Asterisk Server.... Please share your Kind Toughts -- Best Regards Shazi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090820/091e1ed5/attachment-0001.htm

Hi All Could a VPN be used to help with SIP Tunneling and QoS issues. State 1: Two IP Networks Connected via the Public Internet transmitting VoIP Traffic Say a VoIP User and VoIP Termination Provider. Each side can put QoS onto their part, but if QoS does NOT exist between them then call quality will be bad anyhow. State 2: Same as above except a VPN tunnel is setup between each side. Thus

On 11/12/20 7:50 AM, Jonathan Billings wrote: > On Thu, Nov 12, 2020 at 12:56:15PM +0000, Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) via CentOS wrote: >> If the point is to access a specific web site only the remote >> machine can get to, you can also do it with port forwarding: >> ssh -L 8000:ip_of_web_site_to_access_from_remote:443 remote_machine >> and

Hello I'm trying to create compatibility with an automated system that I do not have control over and cannot change. The system was built to connect to individual embedded linux machines that create reverse tunnels back to a server. These tunnels take the form: /bin/ssh -i /home/remote/.ssh/id_rsa -Nnx2TR 22000:127.0.0.1:22 robot at externalhost /bin/ssh -i /home/remote/.ssh/id_rsa -Nnx2TR

Le mercredi 18 janvier 2017 ? 8:55 +1100, Darren Tucker a ?crit : > On Tue, Jan 17, 2017 at 07:42:50AM -0800, Ron Frederick wrote: Thank you for your answers. > [...] > > One thing that makes UDP over SOCKS more complicated for SSH is that > > SOCKS normally keeps the UDP packets it forwards as UDPl, just adding > > a small header to each packet. If you want to get the

Hi, I have a problem with a Linux box which I updated from 2.5.2p2 to 2.9p2 recently. It's running a tunnel started via inittab using a script which starts ssh -2 -N -o 'ConnectionAttempts 3600' -L <tunnel> $host This has run reliable with 2.5.2 over the last months. Now, after I have upgraded to 2.9p2, the tunnel is closed right after each attempt of an application to use

I have read several HOWTO's online that indicate one should be able to access a samba share over an ssh tunnel from a windows box with the following steps: 1. Stop the File and Print sharing services on the windows box 2. Create an ssh tunnel from the windows box to the samba server (port 139) 3. Connect to the samba server as if it were on 127.0.0.1 Unfortunately, doing this on any of my