similar to: problems with -R

http://bugzilla.mindrot.org/show_bug.cgi?id=530 Summary: problems with port forwarding Product: Portable OpenSSH Version: 3.5p1 Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: gilbert at

I've attached a patch to OpenSSH 3.0.2p1 that will allow the client side of local port forwarding to be bound to a single address. For my purposes, binding to 127.0.0.1 or (via GatewayPorts) all addresses would not work. I overloaded the "-b local_host" option so that it's address will be used when "-L port:remote_host:remote_port" is also specified. Today is the first

https://bugzilla.mindrot.org/show_bug.cgi?id=2222 Bug ID: 2222 Summary: GatewayPorts=no should not rewrite localhost addresses in port-forward requests Product: Portable OpenSSH Version: 6.5p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5

No answers on secureshell at securityfocus.com I must be doing something wrong or the server seems to ignore my bind request. Port forwarding is working it just bind to all ips and ignores my bind request. I've also tried this with an rfc1918 address opposed to a loopback and had the same results. Google and the archive haven't helped. Thanks in advance for your time and consideration.

Hi all, I'm working on an implementation of VoIP en Linux. I have a Debian Suse (*.*.*.173) with an * and a X-lite client and a Red Hat 9.0 (*.*.*.172) with another softphone X-lite. Both of the softphones are registering and appear in the peers (sip show peers) with the good parameters of address and port. If I try to make a call, * receive the INVITE request and send a 404 NOT FOUND answer.

https://bugzilla.mindrot.org/show_bug.cgi?id=1804 Summary: ssh option -R 127.0.0.2:10443:<dest ip>:443 does not work Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

On Wed, Nov 19, 2014 at 11:47:11PM +0100, Nicolas Ecarnot wrote: > OK, I'm progressing : the ssh issue seems to be gone. > I changed some parameters but not sure which one are relevant. > When comparing with a fresh install, here are the diffs : > > root:/etc# diff /etc/ssh/sshd_config /tmp/sshd_config > 43a44 > > LogLevel DEBUG3 > 48c49 > < #PermitRootLogin

Hi and happy new year! My question: - two extensions: 1111 and 2222 - an active call on 1111 - incoming calls to 1111 should be forwarded to 1111 (call advice!) and 2222 I know how can I forward an incoming call to more than an extension, but I have no idea how can I get the information, that 1111 has already an active call... I think, I need something like: exten =>

https://bugzilla.mindrot.org/show_bug.cgi?id=2473 Bug ID: 2473 Summary: sshd and -R port forwardings on 127.0.0.0/8 Product: Portable OpenSSH Version: 6.6p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

Summary: the newish fourth forwarding argument does not correctly specify the interface on the remote machine for a tunnel in -R On OpenSSH_4.3p2 OpenSSL 0.9.7g 11 Apr 2005, on Kanotix 2.9 kernel 2.6.16.2 and Cygwin 1.5.19(0.150/4/2) and (old) FreeBSD 4.6-RELEASE sshd_config file: AllowTcpForwarding yes GatewayPorts yes Set up a forwarding tunnel: From a Kanotix box inside my firewall:

Dear asterisk users, We want setup TE121 digium board: Model: Digium TE121: VoiceBus technology allows the TE121 to use an industry standard bus-mastering PCI Express interface. http://www.digium.com/en/products/digital/te121.php My platform Server: HP Proliant 150 G5 OS: UBUNTU x86_64 GNU/Linux Asterisk: 1.4.21.2 zaptel: SVN-branch-1.4-r4662M When we enable zaptel driver for TE121, the

Mike, As it stands right now, we use xz for our compression, so if rsync had a similar option for xz that would probably be an improvement. However, I think being able to decompress directly to the remote system would save more; elsewise I don't see how I'm going to be able to avoid untarring and uncompressing the whole xz file on the other end. thanks much, ed On Tue, Dec 6, 2016 at

Le 19/11/2014 22:19, Richard W.M. Jones a écrit : > On Wed, Nov 19, 2014 at 10:05:53PM +0100, Nicolas Ecarnot wrote: >> Nov 19 21:54:52 serv-p2v-adm1 sshd[2727]: pam_unix(sshd:session): >> session opened for user root by (uid=0) >> Nov 19 21:54:53 serv-p2v-adm1 sshd[2725]: channel 2: open failed: >> connect failed: Connection refused >> Nov 19 21:54:53

All, A bit of background: I work on a QA API on a network that is very choppy (a lot of network interrupts), and we use ssh to do a large part of this automation. This leads to some problems: ssh connections seem to be sensitive to network state, becoming unusable if the choppiness reaches a certain threshold, and either timing out or disconnecting if this happens. Anyways, I stumbled across

I'm experiencing some problem using the transfer() application,expecially when a call in received from a queue. I'm using Asterisk 1.4.22.1 This is my scenario: ; this is the piece of code in extensions.conf that place the call in the queue when 1111 is called exten => 1111,1,Answer exten => 1111,n,Queue(2000|t) ;this is the piece of code that calls the user test when 2222 is

http://bugzilla.mindrot.org/show_bug.cgi?id=1180 Summary: Add finer-grained controls to sshd Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org ReportedBy: dtucker at

Hi, I'm very new to Asterisk and I have the following scenario. 1. Let's say I have a number of 1-222-222-2222 from my SIP service provider (VoicePulse). 2. I point my phone, Verizon wireless cellphone (1-111-111-1111), voicemail to the number provided by SIP service provider (1-222-222-2222). 3. I use another phone (1-333-333-333) to call 1-111-111-1111 and leave a voicemail message.

When forwarding local ports with -L these ports can be made accessible to the local net with the -g option. For remote ports, forwarded with -R this option does not apply. It would be nice to have a -G option which does the same on the remote machine for the remote net, depending on the remote users rights. On the server site it should be configurable, on which networks/addresses the forwarded

Hello, I added the support for netgroups to be used in the AllowUsers and DenyUsers parameters. This has some advantages: * hostnames or ip addresses need not to be written or maintained in the sshd_config file, but can be kept abstract names what also simplifies a bit largescale openssh installations * sshd_config needs not change and sshd be restarted when changing the list of allowed /

Hello, I just upgraded from 2.9p2 to 3.0.1p1 and good news. I don't have to patch channels.c to get Remote Port Forwarding to work. That is fantastic. It appears, however, that -g still doesn't work. I checked the archives and it doesn't look like anyone has mentioned it yet. What does work is if I ssh to a machine I can telnet to localhost on the forwarded port, but connecting to