[asterisk-bugs] [JIRA] (ASTERISK-21065) Asterisk 11 IPv6 - FastAGI fail

[Michael L. Young (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202854#comment-202854 ] 

Michael L. Young edited comment on ASTERISK-21065 at 2/12/13 6:02 PM:
----------------------------------------------------------------------

Jeremy, the problem here, I believe, is that you are using the hostname "localhost" and "localhost" is resolving to the ipv6 address on your loopback adapter.  Since the IPv6 address is being returned first by the kernel and then a call to create a socket() and then connect() are successful on this valid loopback adapter using ipv6, everything is working properly based on this configuration.  So, removing "localhost" from ::1 is not "hiding" anything.  It is actually correcting the configuration problem.

As far as I am concerned, there is no bug in Asterisk.  The current code already handles things just as cloos outlined for determining to use IPv4 or IPv6.  This issue is not a result of adding IPv6 capabilities to AGI.  This is a configuration issue, which presented itself based on the fact that we now are able to use IPv6.

I believe that Rusty just wanted you to confirm that our conclusions were correct about the problem lying in the hosts file by having "localhost" resolving to both ipv4 and ipv6 loopback addresses, something that is not commonly found in the default hosts files on current distros as far as I am aware.
                
      was (Author: elguero):
    Jeremy, the problem here, I believe, is that you are using the hostname "localhost" and "localhost" is resolving to the ipv6 address on your loopback adapter.  Since the IPv6 address is being returned first by the kernel and then a call to create a socket() and then connect() are successful on this valid loopback adapter using ipv6, everything is working properly based on this configuration.  So, commenting out ::1 is not "hiding" anything.  It is actually correcting the configuration problem.

As far as I am concerned, there is no bug in Asterisk.  The current code already handles things just as cloos outlined for determining to use IPv4 or IPv6.  This issue is not a result of adding IPv6 capabilities to AGI.  This is a configuration issue, which presented itself based on the fact that we now are able to use IPv6.

I believe that Rusty just wanted you to confirm that our conclusions were correct about the problem lying in the hosts file by having "localhost" resolving to both ipv4 and ipv6 loopback addresses, something that is not commonly found in the default hosts files on current distros as far as I am aware.
                  
> Asterisk 11 IPv6 - FastAGI 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
>            Assignee: Rusty Newton
>         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