[Ekiga-list] Ekiga 3.2.0 and STUN

[Bent <bbagger gmail com>]

As a corollary to the thread about Ekiga and the Gentoo ebuilds I have
done some investigations. This is the first report on the outcome.

The following relates to a version of ekiga 3.2.0 built with debug
enabled. When I start Ekiga it registers OK with ekiga.net, but it
appears that STUN is not in play here, although I'm behind a firewall
that does NATing. I have uploaded a file related to this to:

http://filebin.ca/vjnzmo/ekiga-bbagger.tar.bz2

The tarball contains 4 files. One is the 'd -4' output. One is a
screen dump which indicates that STUN is enabled (I can't get to the
preferences, because ekiga aborts when I click the selection in the
dropdown menu, but that is another story)

The two remaining files are traces taken with wireshark (actually
tshark) on the inside and the outside of my firewall. They are taken
simultaneously, so you should be able to pair the packets using the
timestamps.

Concerning IP addresses: 192.168.19.1 is my workstation with ekiga
3.2.0. 192.168.19.6 and 86.48.49.16 are the inside (LAN side) and
outside respectively of my firewall. 86.64.162.35 is of course
ekiga.net

The inside trace shows clearly that the SIP packets are sent with the
private address in the payload. In the outside trace this is
corrected.

My firewall is a Linux-box (Soekris net501) and I have enabled the SIP
Application Layer Gateway (ALG) on it. It is quite clear that it is
the ALG that does the conversion of the IP addrsses in the payload. Is
the NAT detection SW in Ekiga really clever enough to discover that an
ALG is in place and hence does not go about its usual work?

A continued Happy Easter to you all.

Bent