[asterisk-bugs] [JIRA] (ASTERISK-21065) Asterisk 11 TCPv6 AGI fail
cloos (JIRA)
noreply at issues.asterisk.org
Tue Feb 12 13:37:58 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202832#comment-202832 ]
cloos commented on ASTERISK-21065:
----------------------------------
Falling back to v4 when v6 cannot route will not help this case.
He has a route to ::1, it is just that nothing is listen(2)ing there.
Most dists these days have hosts(5) configures such that localhost only maps to 127.0.0.1 and ::1 maps to ipv6-localhost, for exactly this reason. Too many complaints from their users that things started breaking as soon as they enabled ipv6 in their kernels.
That said, asterisk should get a list of addresses back from the getaddrinfo(3) call. It would not be a bad idea to try each in turn until connect(2) succeeds or it runs out of addrinfo structs.
The reporter’s other solution would be to listen(2) to ::1 either in addition to 127.0.0.1 if his net.ipv6.bindv6only==1 or instead of 127.0.0.1 if net.ipv6.bindv6only==0.
> Asterisk 11 TCPv6 AGI fail
> --------------------------
>
> Key: ASTERISK-21065
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21065
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_agi
> Affects Versions: 11.2.1
> Reporter: Jeremy Kister
> Attachments: 21065-1.patch, console_debug.txt, console.txt, extensions.conf
>
>
> exten => 1,1,AGI(agi://localhost/foo) always fails with "Connect failed"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list