GNOME Bugzilla – Bug 331041
IPv6 not supported
Last modified: 2020-06-06 16:30:47 UTC
as Damien just correctly stated in #330999: -(snip)- There will be 2 problems remaining: - Add correct DNS SRV support (probably not before 2.2), see #328340. - Add IPv6 support (probably not before a few years), no bug report opened for this. -(snip)- So for the latter here's the bugreport demanding for it to be fixed publically. Just imagine your setup being IPv6-only and someone would tell you that Ekiga is supporting IPv4 just fine. It's no use, so this is indeed something important. The lack of not having IPv6 for testing can be addressed, just drop me a private email and I shall get you a tunnel.
That bug report should be in the OPAL/PWLIB bugtracker. I'll leave it here for further reference and change the priority to low and the severity to enhancement (nobody has IPv6 and not IPv4).
SNIP 330999 We have opened another bug report (#331041) to get real IPv6 support, but at least now it works on IPv4 on machines having IPv6 support, which is not so bad! SNIP My host has IPv6 and IPv4 address, but ekiga only listen on IPv4-Addr:5060. is it right?
The answer to your question is in the text you quoted...
"(nobody has IPv6 and not IPv4)" Probably true, but that doesn't mean the IPv4 address is accessible to the caller. The set up I have is for all machines on my LAN to have global scope IPv6 addresses and local scope RFC1918 IPv4 addresses. Suppose you (out on the internet) want to place a call to one of the machines on my LAN you would need to use IPv6 since the IPv4 address is out of your scope. In reality I have an Asterisk server on my internet-facing router and you would be able to proxy your call through that if you're using IPv4 but if I didn't have the Asterisk server there proxying the inbound traffic you would _need_ to use IPv6. IMHO VoIP (and similar peer-to-peer technologies) are one of the big reason why we want IPv6 and there isn't going to be a lot of adoption for that reason if we don't start actually supporting it in the software.
I agree with you. If you provide me a patch, I will be happy to proofread it and help you improving it so that we can have IPv6 in Ekiga.
Furthermore, ekiga 2.0.2 with opal 2.2.2 is publishing sip:<mypublicIPv6> and h323:<mypublicIPv6>, in addition to the ipv4 addresses, in the directory. They are not reachable because the software is not listening on them, only on private ipv4 addresses. ALso, the OLPC is supposed to put in the wild 7 million of ipv6-only machines next year, and up to 100 million in the next few years.
Well, we[ekiga developpers] don't argue about the interest of having a correct IPv6 support ; we know it's very important. Our points are : 1) we have other urging matters ; 2) we have very limited resources. If you can help us, it will come even faster!
Any update about it ?
*** Bug 552832 has been marked as a duplicate of this bug. ***
oh, sorry didn't see this bug when i searched. any ETA on possible implementation of IPv6 support?, if not. what parts of ekiga would need altering to support it?. I've got fairly good experience in C and if i can possibly kick IPv6 support in i'd be delighted to know what i would need to kick around to get it sorted.
Basically, Ekiga relies on two libraries : - OPAL (the 'protocol' library) - PTLIB (the sockets/threads/strings/ library) Having support for IPv6 addresses should require no change in Ekiga. Changes should only be made in OPAL and PTLIB. However, somebody added IPV6 support to PTLIB a few years ago, and to the H.323 part of OPAL. The only missing part to modify is the SIP part of OPAL. It is only a few files, and I don't think it is very difficult. But it is C++.
Are any of those IPv6 support fixes in the current versions of those libraries?. as in they are implemented and all. And as in such only the SIP part is what's missing?. I got some familiarity of C++. not as much as C but can't see how it would be hard to pick up on.
Damien, the "Having support for IPv6 addresses should require no change in Ekiga." isn't exactly true : I remember there are magic computations done in ekiga with ':' in uris, and those fail with IPv6.
Kristoffer, yes. Basic support is there, but not for SIP. Snark, you are right. I thought about this, but I also thought it was trivial.
I agree it's trivial to fix once the problem is spotted -- but I fear it's not that easy to spot!
re: #13, Also, it is quite probable that there are input validations that won't allow "::" or other ipv6 addresses. Another typical problem is that all uses of gethostbyname() must be typically changed to use getaddressinfo(), so that ipv6 and ipv4 addresses are handled transparently.
Continuing http://mail.gnome.org/archives/ekiga-devel-list/2010-March/msg00005.html . I'm attaching several patches that introduce experimental IPv6 support for direct pc-to-pc H.323 and SIP calls. At least, it works for me (ekiga 3.2.6, opal 3.6.6, ptlib 2.6.5) over IPv6 tunnel and does not break IPv4 connectivity within LAN. sip:[ip:v6::address]:port and h323:[ip:v6::address] URIs are supported.
Created attachment 155443 [details] [review] This match make ekiga listen on interfaces with IPv6 address for SIP
Created attachment 155444 [details] [review] Some IPv6 fixes for opal
Created attachment 155445 [details] [review] Another patch for opal Without this patch, calls to IPv4 addresses can't be made when IPv6 is present. That's because opal will try to send INVITE from IPv6 address first, fail, and terminate connection before second attempt from IPv4 address is made.
Created attachment 155446 [details] [review] Make ekiga listen on IPv6 for h.323
Created attachment 155447 [details] [review] Decrease max frame size to 1150 Decrease max video frame size from 1400 to 1150 to work properly over a tunnel with lesser MTU (MTU detection would be nice, but difficult to implement).
Sorry Arseniy for replying so late. I think the most important thing is that the patches do not break ipv4, but you already said that. As the patches are for ptlib and opal mainly, please propose those patches to ptlib/opal upstream at http://sourceforge.net/tracker/?group_id=204472&atid=989750. When they are included there, we include the changes for ekiga too. Note also that reducing the packet size for ipv4 too is not a good option, because ekiga already have problems with UDP packets with size greater than 1450, when communication does not work. Reducing to 1150 makes this problem appear very often. See http://wiki.ekiga.org/index.php/Troubleshooting#I_hear_the_ring.2C_but_the_communication_is_not_established for more information.
(In reply to comment #23) > Note also that reducing the packet size for ipv4 too is not a good option, > because ekiga already have problems with UDP packets with size greater than > 1450, when communication does not work. Reducing to 1150 makes this problem > appear very often. See > http://wiki.ekiga.org/index.php/Troubleshooting#I_hear_the_ring.2C_but_the_communication_is_not_established > for more information. Maybe I've misunderstood something, but it looks like an issue with PDU packets exceeding MTU while my patch should only decrease size of RTP packets for video session. Is it really related?
Ok, then I was wrong then.
The changes you proposed for ipv6 have been included in stable too, cf. http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=rev&revision=24330 and http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=rev&revision=24330. What does it remain to commit? is it only patches from comment #21 and comment #22? Are you sure about them? By the way, I saw that not all the patches have been committed, for ex. comment #18, is it normal?
Arsenyi, any comment about my previous comment?
Was Arseniy Lartsev the only one interesten in IPv6 in Ekiga? Now I am quite interested in this topic (I need an IPv6-capable SIP client for testing my devices), so I can continue with testing and patching. ptlib-2.8.4, opal-3.8.4 and ekiga-3.3.0 still do not support IPv6 straight away. The most important for ekiga is the patch from attachment 155446 [details] [review] – without it ptlib won't even consider IPv6 addresses for anything. For my tests, I am using a similar patch which is triggered by an 'EKIGA_IPV6' environment variables. The patch from comment 18 is indeed missing and may cause Ekiga use wrong interfaces, but I haven't got to this point yet (my Ekiga still wants to use IPv4 addresses to connect to IPv6 hosts).
I have tried to continue the Arseniy Lartsev work with adding IPv6 support to Ekiga, fixing ptlib/opal when necessary, but failed. I want to share part of my work anyway... I have posted the patch from comment 18 upstream, just for the record: https://sourceforge.net/tracker/?func=detail&aid=3295340&group_id=204472&atid=989750 I have also posted a few my patches and comments there: https://sourceforge.net/tracker/index.php?func=detail&aid=3295342&group_id=204472&atid=989750 https://sourceforge.net/tracker/?func=detail&aid=3295347&group_id=204472&atid=989750 https://sourceforge.net/tracker/?func=detail&aid=3295357&group_id=204472&atid=989748 Two of my patches for Ekiga follow. I hope it can help a bit with anyone that would like to continue. I guess I need to switch to Linphone instead, as I really need an IPv6-enabled SIP client for my work.
Created attachment 186935 [details] [review] Patch to enable IPv6 via an environment variable Probably not the way to have it in a final version, but usable for testing IPv6 support in Ekiga while patching ptlib and opal. This patch switches Ekiga to IPv6 mode when EKIGA_IPV6 environment variable is set, otherwise Ekiga works as usual, with IPv4 support only. It is a variation of the patch from attachment 155446 [details] [review].
Created attachment 186936 [details] [review] Attempt to make IPv6-enabled Ekiga listen on IPv4 too This is my failed attempt to make IPv6-enabled (attachment 186935 [details] [review] or attachment 155446 [details] [review]) Ekiga listen on IPv4 0.0.0.0 address in addition to [::]. This also relies on opal patches from https://sourceforge.net/tracker/?func=detail&aid=3295357&group_id=204472&atid=989748. This doesn't work for some reason (Opal seems to be using [::] twice instead of [::] and 0.0.0.0), but may give some idea to someone better then me.
Thank you very much, I will check your patches as soon as possible. Have you used ptlib 2.8.4, opal 3.8.4 and ekiga 3.3.0? Or have you used git (better), which uses ptlib 2.10 and opal 3.10?
I have used 2.8.4, opal 3.8.4 and ekiga 3.3.0. I am not desperate enough to try unreleased code, especially because the changelogs I have found didn't mention any IPv6 updates.
Jacek, to resume your contribution: - ptlib/opal patches have been reported and all of them have more or less been committed - what remains to be done in ekiga? I am tempted to commit attachment from comment 30; will you find a better way than the attachment from comment 31?
The patch for comment 30 shouldn't hurt and would probably make further IPv6 development easier. In the final version it should probably be made unconditional (or rather a build-time condition) or a command-line switch. Patch from comment 31 should probably be re-thought for current development branches of ptlib/opal/ekiga. It didn't quite work with the ptlib/opal/ekiga versions I was working with and I was not able to find the reason why. New ptlib/opal is said to do thing in a different way, maybe the ekiga patch would not be needed or need some changes. I'll try to take a look at the git version and most recent ptlib/ekiga if I find time.
Ok, patch from comment 30 committed, http://git.gnome.org/browse/ekiga/commit/?id=359d13db, thank you very much.
ptlib/opal v12 have good support for IPv6, and ekiga 4.4.0 will use it.
Ok what needs to be done in order to get IPv6 running. I am a person that learned, use and implemented IPv6 in different location (my home and my friends). I configured setup like 6rd, native PPPv6 and native ethernet. So IPv6 is my force and I want to help an open project. I need to improve my C++ so if I can be any help.
Thank you for your intention. This is an important bug you are tackling. Try to test on as much networks as possible, to avoid regressions with IPv4. In order to make IPv6 working, you have to: - ensure that current ekiga (4.0.x AND git) works on your network - build ptlib svn v2_12 branch, and opal svn v3_12 branch (see http://wiki.ekiga.org/index.php/Download_Ekiga_sources for how to get previous branches, you have to replace 10 by 12) - this is because IPv6 is functional in those branches, and not in currently-used-by-ekiga branches - build ekiga git master using the above ptlib/opal code, fix the simple build failures and do all IPv6 fixes there Feel free to ask here for more information.
Ekiga is not under active development anymore: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273 Ekiga saw its last release 7 years ago. The last code commits were 4 years ago. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.