similar to: DO NOT REPLY [Bug 5851] New: Name lookup failures and CIDR regression

Displaying 20 results from an estimated 200 matches similar to: "DO NOT REPLY [Bug 5851] New: Name lookup failures and CIDR regression"

2008 Oct 24
0
Name lookup failures and CIDR regression under cygwin ( patch attached )
Just updated to 3.0.4 under cygwin and I'm now getting lookup failures in the log. 2008/10/24 00:13:23 [1984] name lookup failed for X.X.X.X: Unknown server error Looking at the code it seems the call will never succeed? /* reverse lookup */ name_err = getnameinfo((struct sockaddr *) ss, ss_len, name_buf, name_buf_size, port_buf, port_buf_size,
2004 Apr 01
1
[patch] net/rsync: problems in client name lookup code
>Submitter-Id: current-users >Originator: Alex Vasylenko >Organization: >Confidential: no >Synopsis: [patch] net/rsync: problems in client name lookup code >Severity: non-critical >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 4.8-RELEASE-p16 i386 >Environment: System: FreeBSD 4.8-RELEASE-p16 >Description: rsync does reverse name
2018 Feb 23
6
RFC 8305 Happy Eyeballs in OpenSSH
Hello, I use hosts that are dual stack configured (IPv4 and IPv6) and it happens that connectivity through one or the other is broken and timeouts. In these case connection to the SSH server can take quite some time as ssh waits for the first address to timeout before trying the next. So I gave a stab at implementing RFC 8305. This patch implements part of it in sshconnect.c. * It does not do
2003 Dec 09
1
Make Fails on Cobalt Qube 2
All; I am using the cobalt Qube 2 which uses a Cobalt OS with is supposedly a RedHat Linux 4.2 variant. I can not compile the new rsync version 2.5.7 as I always fail my make with the following error: clientname.c: In function `client_addr': clientname.c:72: warning: implicit declaration of function `getnameinfo' clientname.c:73: `NI_NUMERICHOST' undeclared (first use this function)
2001 Jun 17
0
getnameinfo failed
I'm running openssh-2.3.0p1 in linux. scp -P 2222 -v user at 207.224.119.73:openssh-2.3.0p1.tar /tmp/junk gives me Executing: program /usr/local/bin/ssh host 207.224.119.73, user user, command scp -v -f openssh-2.3.0p1.tar ssh_connect: getnameinfo failed I get that 3 times and then it gives up. I've changed ssh_connect as follows: if (getnameinfo(ai->ai_addr,ai->ai_addrlen,
2002 Apr 08
1
compilation fails on Cobalt RaQ2
Configure seems to work fine with no options passed, but a make attempt fails in clientname.c: gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c clientname.c -o clientname.o clientname.c: In function `client_addr': clientname.c:55: warning: implicit declaration of function `getnameinfo' clientname.c:56: `NI_NUMERICHOST' undeclared (first use this function) clientname.c:56: (Each
2003 Jul 24
0
make fails all versions > 2.4.8 on older linux machine (clientname.o)
hi i'm trying to update an older rsync version due to some minor errors during syncing with an up to date version (2.5.6) of rsync. my problem is that the make process actually won't finish, here is the output: clientname.c: In function `client_addr': clientname.c:72: warning: implicit declaration of function `getnameinfo' clientname.c:73: `NI_NUMERICHOST' undeclared
2015 Feb 26
4
Call for testing: OpenSSH 6.8
On Thu, 26 Feb 2015, Darren Tucker wrote: > I noticed this error log spam on the tinderbox when looking at one of the > failures. It happens with Unix domain socket forwarding is requested: > > debug1: channel 1: new [forwarded-streamlocal at openssh.com] > get_socket_address: getnameinfo 1 failed: ai_family not supported > get_sock_port: getnameinfo NI_NUMERICSERV failed:
2019 Dec 04
4
Dovecot 2.3.9 fails on FreeBSD
On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot wrote: > On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot wrote: > > Hi > > > > I've just tried to build the latest Dovecot 2.3.9 on FreeBSD 11.3. > > Without success...It fails on the following commit which was introduced > > in 2.3.9: > >
2019 Dec 04
0
Dovecot 2.3.9 fails on FreeBSD
I'm working on the port as we type. I've already done this patch (will add the comments). On Wed, Dec 4, 2019 at 11:29 AM Josef 'Jeff' Sipek via dovecot < dovecot at dovecot.org> wrote: > On Wed, Dec 04, 2019 at 12:19:35 -0500, Josef 'Jeff' Sipek via dovecot > wrote: > > On Wed, Dec 04, 2019 at 18:06:58 +0100, Pascal Christen via dovecot > wrote:
2007 Nov 08
2
DO NOT REPLY [Bug 5064] New: compile error - SCO 5.0.6a
https://bugzilla.samba.org/show_bug.cgi?id=5064 Summary: compile error - SCO 5.0.6a Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: aaron.pelton@ahs.state.vt.us
2003 Apr 04
5
[Bug 533] sshd failure on Tru64 (OSF/1) 5.1a
http://bugzilla.mindrot.org/show_bug.cgi?id=533 Summary: sshd failure on Tru64 (OSF/1) 5.1a Product: Portable OpenSSH Version: 3.6p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:
2001 Jun 07
0
sshd failing to allow connections.
HI Guys, On my Slackware-current firewall I cannot ssh into it. The tail of the syslog is :- Jun 1 10:56:15 firefly sshd[22176]: fatal: get_sock_port: getnameinfo NI_NUMERICSERV failed any ideas why I get this error? Although slack-current includes openssh I've actually built this one from source ( and openssl too ) in case it was a config issue with the slackware -current release (which
2006 Oct 31
0
6249405 CIDR support does not work for logical interface
Author: kcpoon Repository: /hg/zfs-crypto/gate Revision: f244f36ccf8f500f22f5245345455c0fa68f4533 Log message: 6249405 CIDR support does not work for logical interface Files: update: usr/src/cmd/cmd-inet/usr.sbin/ifconfig/ifconfig.c
2012 Sep 07
1
[Bug 1513] CIDR address/masklen matching support for permitopen=
https://bugzilla.mindrot.org/show_bug.cgi?id=1513 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |2035 --- Comment #16 from Damien Miller <djm at mindrot.org> --- Retarget uncompleted bugs from 6.1 => 6.2
2008 Aug 22
1
CIDR address/masklen matching support for permitopen="host:port" restrictions?
Dear openssh-unix-dev list, in OpenSSH 5.1 you introduced CIDR address/masklen matching for "Match address" blocks in sshd_config as well as supporting CIDR matching in ~/.ssh/authorized_keys from="..." restrictions in sshd. I wonder whether CIDR address/masklen matching will be implemented for permitopen="host:port" restrictions in sshd as well, that would be quite
2015 Jan 08
1
[Bug 994] New: Named sets with type "ipv4_addr" do not allow adding CIDR elements
https://bugzilla.netfilter.org/show_bug.cgi?id=994 Bug ID: 994 Summary: Named sets with type "ipv4_addr" do not allow adding CIDR elements Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: enhancement Priority: P5
2016 Apr 21
0
[Bug 1009] Ability to use CIDR notation in IPV4/IPV6 named sets
https://bugzilla.netfilter.org/show_bug.cgi?id=1009 Vadim A. Misbakh-Soloviov (mva) <netfilter at mva.name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netfilter at mva.name --- Comment #1 from Vadim A. Misbakh-Soloviov (mva) <netfilter at
2016 Apr 21
0
[Bug 1009] Ability to use CIDR notation in IPV4/IPV6 named sets
https://bugzilla.netfilter.org/show_bug.cgi?id=1009 Pablo Neira Ayuso <pablo at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Pablo Neira Ayuso <pablo at netfilter.org> --- There are already kernel
2016 May 13
0
[Bug 1009] Ability to use CIDR notation in IPV4/IPV6 named sets
https://bugzilla.netfilter.org/show_bug.cgi?id=1009 Pablo Neira Ayuso <pablo at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin at rollinix.net --- Comment #3 from Pablo Neira Ayuso <pablo at netfilter.org> --- *** Bug 994