[Pkg-ace-devel] Packaging Combat; ACE+TAO 6.0.3+2.0.3; and issue related to IPv6 in TAO?

[Thomas Girard]

Hello all,

I started playing with Combat[1], an ORB written with Tcl, and hence
packaged it in pkg-corba newly created git repository:

  http://anonscm.debian.org/gitweb/?p=pkg-corba/pkg-combat.git;a=summary

The package is mostly ready, remaining things are ITP to submit,
manpages to write and upstream to contact.

I also updated packages for ACE+TAO 6.0.3+2.0.3. They build fine but
are yet to be tested. The current state was pushed to Alioth:

  http://anonscm.debian.org/gitweb/?p=pkg-ace/pkg-ace.git;a=summary

Before moving forward, there's one thing I want to get solved: while
playing with idl2tcl (the program generating stubs and skeletons in
Combat) I figured out that it was not working correctly with the
current ACE+TAO configuration where IPv6 and IPv4 IPv6 migration are
turned on. idl2tcl indeed does not provide an IDL compiler, but rather
relies on external IFR (here, the one from TAO) to generate Tcl code.

What I saw here that idl2tcl was not able to contact the IFR repository
using the IOR generated when invoking IFR. While this may look like an
issue in Combat, it reminded me two things I had already observed:

 - some programs I wrote did not seem to cope well with this as well,
   e.g. tlscli[2]. In my tests I had to specify an endpoint like
   127.0.0.1.

 - omniORB was recently reported an issue with something similar:

     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626099

In short: TAO servers are listening on IPv6 only, but should also be
able to accept IPv4 connections. But this last part does not seem to
work.

Does that sound familiar for someone? I need some time to understand
what's going on, and if I don't I'll report this upstream.

Thanks,
Regards,

Thomas

[1] http://www.fpx.de/Combat/
[2] https://launchpad.net/tlscli