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

[Jeremy Kister (JIRA)]

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

Jeremy Kister edited comment on ASTERISK-21065 at 2/12/13 5:11 PM:
-------------------------------------------------------------------

rusty, "Waiting for Feedback" for what?  i've identified the problem and we know that removing localhost from ::1 hides the issue.

it's arguable how to fix the issue, and depending on how it's fixed a blurb in UPGRADE.txt may be needed.

I'm not versed on IPv4 -> IPv6 transition semantics, so I don't know if the "proper" or "well accepted" way of fixing this is to loop through  getaddrinfo until connect succeeds or it runs out of hosts as cloos mentioned.  Reading CHANGES for r357610, it does appear an attempt was made for asterisk to have this behavior.

If we do not make asterisk connect to each host for a given RR, I would suggest adding a comment in UPGRADE.TXT.  It should mention ipv6 taking precedence over ipv4 and "localhost" is the most common thing that may need tweaking if the daemon is not ipv6 enabled.  Then, perhaps something in configure could also check for localhost in /etc/hosts to see if it is multihomed (send a well visible warning, but not an error)

                
      was (Author: jkister):
    rusty, "Waiting for Feedback" for what?  i've identified the problem and we know that removing localhost from ::1 hides the issue.

it's arguable how to fix the issue, and depending on how it's fixed a blurb in UPGRADE.txt may be needed.

I'm not versed on IPv4 -> IPv6 transition semantics, so I don't know if the "proper" or "well accepted" way of fixing this is to loop through  getaddrinfo until connect succeeds or it runs out of hosts as cloos mentioned.

I would probably suggest this /only/ be changed by adding a comment in UPGRADE.TXT.  It should mention ipv6 taking precedence over ipv4 and "localhost" is the most common thing that may need tweaking if the daemon is not ipv6 enabled.

perhaps something in configure could also check for localhost in /etc/hosts to see if it is multihomed (send a well visible warning, but not an error)

                  
> 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