in reply to Stories from the front

openssl s_client -connect localhost:443 No dice -- got an error right away. Eventually, I discovered that openssl s_client -connect 10.1.1.161:443 worked instead. I'm sure someone can explain that -- I can't.

I don't know about Solaris, but on linux, localhost is defined in /etc/hosts, and is normally assigned 127.0.0.1. You might try adding a localhost entry for 10.1.1.161 to /etc/hosts, or whatever file Solaris uses.

I'm not really a human, but I play one on earth Remember How Lucky You Are

Replies are listed 'Best First'.
Re^2: Stories from the front
by atcroft (Abbot) on Jan 03, 2009 at 15:05 UTC

    My first thought in reading the OP was that maybe there might be only a VirtualHost entry using port 443 defined for the 10. address. One thing that might provide a clue would be to see if netstat (sorry, but I don't recall the appropriate options on Solaris) shows it to be listening on port 443, or only on port 443 on the 10. ip address.

    Hope that helps.

[reply]
Re^2: Stories from the front
by talexb (Chancellor) on Jan 03, 2009 at 16:08 UTC
      You might try adding a localhost entry for 10.1.1.161 to /etc/hosts, or whatever file Solaris uses.

    Solaris does use /etc/hosts -- I may have to check that file and see what it contains. I do know that from both Linux and openSolaris (I'm at home and can't try it on Solaris right now), I'm able to ssh into localhost, 127.0.0.1 and $localIP. And my openSolaris box has 

    ::1             localhost
127.0.0.1       foobar foobar.local localhost loghost

    [download]
    in its /etc/hosts file. Thanks for the feedback.

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

[reply]
[d/l]
[select]
      Another thing to mull over, is that localhost is called a loopback device. So besides having localhost linked to your 10.... address in /etc/hosts, you have have to setup the network configuration to add the extra loopback device to what it listens to. Google for "ifconfig add loopback" for how to do it. You might need to add a route to the new loopback device, like " /sbin/route add -net 10.0.0.0" (untested) or something like 
       ifconfig lo:1 10.0.0.1
 route add -host 10.0.0.1 lo:1

      [download]
      then when you do an ifconfig, you will see lo and lo:1 listed as loopback. But Solaris or the linux distro may add the route automatically at boot, or re-init'ing the network. So if in doubt, reboot after editing the /etc/hosts, unless you know how to restart the network on Solaris.

      And also, as atcroft suggested, you need to check the httpd server configuration file for the https request, to see that 10.0.0.1 is configured.

      I'm not really a human, but I play one on earth Remember How Lucky You Are
[reply]
[d/l]

In Section Meditations