[omniORB] [help] [beginner] cannot run naming service examples
from python chapter 2 "The Basics"
flub at devork.be
Thu Sep 8 20:05:11 BST 2011
On 8 September 2011 16:46, Duncan Grisby <duncan at grisby.org> wrote:
> On Fri, 2011-09-02 at 09:19 +1200, Alistair Bayley wrote:
>> Sorry, here's the entire file:
>> 127.0.0.1 localhost
>> # The following lines are desirable for IPv6 capable hosts
>> ::1 localhost ip6-localhost ip6-loopback
> That is no doubt the problem. When omniORB resolves "localhost", it gets
> the ::1 IPv6 loopback instead of 127.0.0.1. The server is presumably
> only listening on IPv4 (although I'd expect it to listen on IPv6 too --
> perhaps the Ubuntu package changes the default?)
Following along on debian here (testing omniorb 4.1.5 - my fault it's
not 4.1.6 yet). On a fresh install InitRef is empty and
DefaultInitRef = corbaloc::. My /etc/hosts looks the same, with
localhost pointing to both 127.0.0.1 and ::1. omniNames is stared
normally and binds to :::2809, i.e. the tcp6 wildcard.
But as far as I understand this does accept connections from ipv4 too,
I can telnet to 127.0.0.1 2809 and netstat shows the connection as on
a tcp6 socket but using IPv4 addresses:
tcp6 0 0 127.0.0.1:2809 127.0.0.1:50726
So as I understand it the default install does produce a working
environment with omniNames accepting connections from both IPv4 and
IPv6. And the duplicate hostname in /etc/hosts (which I presume is
also default on debian/ubuntu) does not cause any harm.
Or did I miss something?
PS: I'm interested since if the default install is wrong I need to fix it!
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
More information about the omniORB-list