Hi folks, Following an upgrade to Debian wheezy, I'm now running Asterisk 1.8.13.1. As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version can support IPv6. However, it seems that I can't get it to support both IPv4 and IPv6 at the same time. For example, if in sip.conf I set the bindaddr variable to '::' it will only listen on IPv6 and none of my IPv4-only friends and peers will be able to connect to it. On the other hand, if I set it to '0.0.0.0' then it will not listen on IPv6. Is this a bug, or is this simply a limitation of Asterisk 1.8.13.1, or is there some other way to configure it for dual-stack support? Thanks, Jaap
Asghar Mohammad
2013-Mar-21 16:57 UTC
[asterisk-users] Asterisk 1.8 and dual stack support
please see, lists.digium.com/pipermail/asterisk-users/2013-March/278130.html On Thu, Mar 21, 2013 at 5:47 PM, Jaap Winius <jwinius at umrk.nl> wrote:> Hi folks, > > Following an upgrade to Debian wheezy, I'm now running Asterisk 1.8.13.1. > As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version can > support IPv6. However, it seems that I can't get it to support both IPv4 > and IPv6 at the same time. For example, if in sip.conf I set the bindaddr > variable to '::' it will only listen on IPv6 and none of my IPv4-only > friends and peers will be able to connect to it. On the other hand, if I > set it to '0.0.0.0' then it will not listen on IPv6. > > Is this a bug, or is this simply a limitation of Asterisk 1.8.13.1, or is > there some other way to configure it for dual-stack support? > > Thanks, > > Jaap > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.digium.com/pipermail/asterisk-users/attachments/20130321/caf3e216/attachment.htm>
Michael L. Young
2013-Mar-21 19:21 UTC
[asterisk-users] Asterisk 1.8 and dual stack support
----- Original Message -----> From: "Jaap Winius" <jwinius at umrk.nl> > To: asterisk-users at lists.digium.com > Sent: Thursday, March 21, 2013 12:47:57 PM > Subject: [asterisk-users] Asterisk 1.8 and dual stack support > > Hi folks, > > Following an upgrade to Debian wheezy, I'm now running Asterisk > 1.8.13.1. > As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version > can > support IPv6. However, it seems that I can't get it to support both > IPv4 > and IPv6 at the same time. For example, if in sip.conf I set the > bindaddr > variable to '::' it will only listen on IPv6 and none of my IPv4-only > friends and peers will be able to connect to it. On the other hand, > if I > set it to '0.0.0.0' then it will not listen on IPv6.How are you determining that it is not listening on IPv4? bindaddr=:: should allow you to support dual stack. Michael
Rob van der Putten
2013-Mar-21 19:38 UTC
[asterisk-users] Asterisk 1.8 and dual stack support
Hi there Michael L. Young wrote:> How are you determining that it is not listening on IPv4? > > bindaddr=:: should allow you to support dual stack.Which is the way it works with 1:1.8.11.1-1digium1~squeeze. I even use Asterisk as a RTP audio IPv4 <-> IPv6 proxy. Regards, Rob
Jaap Winius, 21.03.2013 17:47:> support IPv6. However, it seems that I can't get it to support both IPv4 > and IPv6 at the same time. For example, if in sip.conf I set the bindaddr > variable to '::' it will only listen on IPv6 and none of my IPv4-only > friends and peers will be able to connect to it. On the other hand, if I > set it to '0.0.0.0' then it will not listen on IPv6.This is well explained here: serverfault.com/a/39561 In short: In Linux, binding to :: means bind to both ipv6 and ipv4. Setting /proc/sys/net/ipv6/bindv6only to 1 changes this behaviour, and Debian has this by default (since squeeze, AFAIK). So this is a system issue, not an Asterisk. At least unless one considers Asterisk's shortcoming of not being able to use more than one socket an issue.