similar to: [Bug 515] BindAddress and -b not working

Hi In a nutshell, the BindAddress functionality doesn't seem to work (at least on Solaris 7 when using the fake-gettaddrinfo module provided). I haven't been able to test on other OS versions or using an OS library provided getaddrinfo (such as OpenBSD), but the unless the functionality of getaddrinfo is majorly different, I think this problem would be similar everywhere. The code in

I want tinc to listen locally on loopback, so that port 655 is not exposed on any system interfaces. Can't tinc make outbound connections when listening on loopback? I can't see any reason why it should. This system will never have other tinc daemons connect to it, it will only ever connect to other tinc daemons in order to establish a VPN connection. -- Jonny Tyers On Sat, 17 Nov 2018

Hello all, I recently have a problem with multiple addresses and address families. Problem is simple, i have some hosts with IPv4 access only and some with IPv6 access. This wouldn't be big problem if I had a stable IP addresses. But sometimes I move to another network with complete different addresses. So I created patch which on option BindAddress accept list of addresses. With ip I solved

https://bugzilla.mindrot.org/show_bug.cgi?id=1685 Summary: ssh attempts v4 connection w/v6 BindAddress setting in ssh config Product: Portable OpenSSH Version: 5.3p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo:

Hi there, Thanks for tinc, firstly. It's awesome. Now, I've found that if I specify: BindAddress = 127.0.0.1 655 Then my tincd cannot make outbound connections (on attempting to connect to another tinc daemon is receives 'Invalid argument'). Removing BindAddress fixes the issue. Unless I've misunderstood the purpose of this option, is this a bug? I'm running v1.0.35 on

The only thing „localhost“ can talk to is „localhost“ - by definition & independently of tinc. What are you trying to accomplish with that choice? Clemens Von meinem iPad gesendet > Am 17.11.2018 um 21:58 schrieb Jonny Tyers <jtyers at gmail.com>: > > Hi there, > > Thanks for tinc, firstly. It's awesome. Now, I've found that if I specify: > >

Changes since OpenSSH 6.4 ========================= This is a feature-focused release. New features: * ssh(1), sshd(8): Add support for key exchange using elliptic-curve Diffie Hellman in Daniel Bernstein's Curve25519. This key exchange method is the default when both the client and server support it. * ssh(1), sshd(8): Add support for Ed25519 as a public key type. Ed25519 is a

http://bugzilla.mindrot.org/show_bug.cgi?id=441 Summary: should ssh BindAddress apply to LocalForward ports Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

diff -u -r -N openssh-2.9p1/channels.c openssh-2.9p1-ajf.1/channels.c --- openssh-2.9p1/channels.c Tue Apr 17 14:14:35 2001 +++ openssh-2.9p1-ajf.1/channels.c Wed Jun 6 23:25:36 2001 @@ -1815,13 +1815,25 @@ /* * getaddrinfo returns a loopback address if the hostname is * set to NULL and hints.ai_flags is not AI_PASSIVE + * + * Oh yeah? Setting hostname to NULL and hints.ai_flags to +

https://bugzilla.mindrot.org/show_bug.cgi?id=2636 Bug ID: 2636 Summary: Fix X11 forwarding, when ::1 is not configured Product: Portable OpenSSH Version: 7.3p1 Hardware: Sparc OS: Solaris Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at

Hi: The openssh suite of commands have an option to specify address (e.g, ListenAddress for sshd) but I do not see support for bind-to-interface. The motivating use case for me is using openssh commands (sshd, ssh, scp, sftp) with the recent VRF capability added to the Linux kernel. The VRF design relies on the bind-to-interface option to select the correct routing tables. Before I started

AI_CANONNAME is only relevant when the resulting official name is used, which is not the case in tftpd for the address to bind to. Also AI_ADDRCONFIG isn't helpful. This flag is good for sockets used to connect(2) somewhere. But for listening sockets it makes tftpd fail to start when -a 0.0.0.0:69 is passed and no network device is up yet. This addresses Debian bug

Hi, i have written a patch for openSSH 5.8p2 which allows the user to set the local source port. The patch is as follows: diff -rupN openssh-5.8p2//readconf.c openssh-5.8p2-srcport//readconf.c --- openssh-5.8p2//readconf.c 2010-11-20 04:19:38.000000000 +0000 +++ openssh-5.8p2-srcport//readconf.c 2011-07-17 20:57:52.385044096 +0100 @@ -125,7 +125,7 @@ typedef enum { oGlobalKnownHostsFile2,

http://bugzilla.mindrot.org/show_bug.cgi?id=441 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From markus at openbsd.org 2002-11-22

https://bugzilla.mindrot.org/show_bug.cgi?id=1211 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1930 --- Comment #4 from Damien Miller <djm at mindrot.org> 2011-09-06 10:34:10 EST --- Retarget unresolved

https://bugzilla.mindrot.org/show_bug.cgi?id=1211 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |2130 --- Comment #12 from Damien Miller <djm at mindrot.org> --- Retarget to openssh-6.4 -- You are

https://bugzilla.mindrot.org/show_bug.cgi?id=1211 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at zip.com.au Status|NEW |ASSIGNED Assignee|openssh-bugs at

https://bugzilla.mindrot.org/show_bug.cgi?id=1211 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Damien Miller <djm at mindrot.org> --- Close all resolved bugs after 7.3p1 release

I just found an old bug report at bugs.digium.com with exactly the same problem. It's really too bad this bug wasn't addressed: http://bugs.digium.com/view.php?id=7315 --- On Fri, 1/9/09, Vieri <rentorbuy at yahoo.com> wrote: > I'm trying to figure out how to reload iax2 (without > breaking existing calls) so it can listen on a new IP > address (like "ip addr

On Sat, Nov 17, 2018 at 11:20:47PM +0000, Jonny Tyers wrote: > I want tinc to listen locally on loopback, so that port 655 is not > exposed on any system interfaces. Can't tinc make outbound connections > when listening on loopback? I can't see any reason why it should. This > system will never have other tinc daemons connect to it, it will only > ever connect to other tinc