bugzilla-daemon at mindrot.org
2002-Jun-27 14:32 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From cmadams at hiwaay.net 2002-06-28 00:31 ------- I'm not seeing this on Tru64 4.0G or 5.1A with OpenSSH 3.4p1. What does "rsh [server]" say? Are you using IPv6? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jun-27 15:23 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From jakari at bithose.com 2002-06-28 01:23 ------- rsh <host> works fine for the one host I can test it for. I am not using IPv6. Tru64 machine is running in Enhanced Security mode (SIA), but I don't see how that should matter here. I see this in debug output: [jakari at poptart ~] ssh -v -v frogstar OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090601f debug1: Reading configuration data /usr/local/etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 ssh: frogstar: Name does not resolv to supplied parameters; neither nodename nor servname were passed. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jun-27 15:42 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From cmadams at hiwaay.net 2002-06-28 01:42 ------- That is the error I get if I try to ssh to something that doesn't resolve: $ ssh xyzzy ssh: xyzzy: Name does not resolv to supplied parameters; neither nodename nor servname were passed. $ but ssh to hosts that resolve works fine. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jun-27 16:16 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From jakari at bithose.com 2002-06-28 02:16 ------- I get the same error either way. Looks like address reolution is broken somewhere. I still have the 2.9p2 binaries and they work fine. [jakari at poptart ~] host frogstar frogstar.bithose.com. has address 192.168.1.72 [jakari at poptart ~] ssh frogstar ssh: frogstar: Name does not resolv to supplied parameters; neither nodename nor servname were passed. [jakari at poptart ~] host foobar Host foobar. not found: 3(NXDOMAIN) [jakari at poptart ~] ssh foobar ssh: foobar: Name does not resolv to supplied parameters; neither nodename nor servname were passed. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jun-28 16:27 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 joa at maths.lth.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From joa at maths.lth.se 2002-06-29 02:27 ------- I had the same problem, but I figured out that getaddrinfo(host, strport, &hints, &aitop) (in ssh_connect) returns EAI_NONAME if hints.ai_family is AF_UNSPEC, even if both host and strport is valid. If I run configure with --with-ipv4-default then family is set to AF_INET and everything seems to work. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2002-Jul-01 13:00 UTC
[Bug 306] ssh on Tru64 returns " Name does not resolv to supplied parameters"
http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From jakari at bithose.com 2002-07-01 23:00 ------- Confirmed that ./configure --with-ipv4-default fixes the problem, thanks. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.