search for: bindaddress

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 Arch L...

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: unassigned-bugs at...

...ltiple 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 two main problems: 1. When using "Host *" it is possible to set address from one family (IPv4 or IPv6), ofcource there can be introduced BindAddress4 and BindAddress6 options 2. I can move to another net and there no need do modify ~/.ssh/config...

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,...

...f 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: > > 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? > &gt...

...hoice? > > 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: > > > > 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,...

http://bugzilla.mindrot.org/show_bug.cgi?id=515 Summary: BindAddress and -b not working Product: Portable OpenSSH Version: 3.4p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org...

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...

I''m trying to start puppetmaster on both of my tun interfaces 10.10.10.6 and 10.10.11.6. What is the syntax to support that when I want to avoid having it listen on 0.0.0.0? I tried bindaddress=10.10.10.6, 10.10.11.6. no worky. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this gro...

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

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

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

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

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

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

...get is the error ------------ debug: Calling puppetca.getcert err: Could not call puppetca.getcert: #<Errno::EHOSTUNREACH: No route to host - connect(2)> err: Could not request certificate: Certificate retrieval failed: No route to host - connect(2) ------------ i tried the default ''bindaddress'' (0.0.0.0) and ''bindaddress = 127.0.0.1, no difference. i can successfully ping / telnet all other ports from the puppet- client to the puppet-master. only port 8140 gives this error (with both, telnet and puppetd) nestat on the server: tcp 0 0 127.0.0.1:8140 0.0.0.0...

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 add local ..."). This alias IP is added/removed by a custom process (script) for clustering purposes. The iax.conf file contains "bindaddr=0.0.0.0". I tried a "iax2 reload" (executed without errors or warnings) but I'm still not

https://bugzilla.mindrot.org/show_bug.cgi?id=2606 Bug ID: 2606 Summary: IPv6 bind address vs autoconfiguration privacy Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

...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 working on patches I wanted to get a sense of whether it >> would be accepted. > > What's wrong with the existing BindAddress option? > For my use case the problem is that it is an address, not a device. The VRF implementation with Linux expects tasks to use the SO_BINDTODEVICE option to bind to the VRF-device. That triggers the use of a route table associated with the VRF domain which can encapsulate one or more...