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

[cloos (JIRA)]

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

cloos commented on ASTERISK-21065:
----------------------------------

I see why conenct(2) doesn’t fail right away; ast sets O_NONBLOCK.

When I tried a quick test with netcat(1) listen(2)ing on 127.0.0.1 and nc6(1) (which also uses O_NONBLOCK) trying to connect(2) to ::1, I got EINPROGRESS.

The fact that res_agi.c ignores EINPROGRESS leads to the connection miss showing up later than it otherwise would.

Giving up O_NONBLOCK is too much of a loss, so that clearly is not an option.

connect(2) suggests poll(2)ing for writeability on the socket(7) whenever EINPROGRESS is set; I do not know whether doing so will help this case.  That would need a test.

This is an interesting issue.

(And I see that deb still defaults localhost to both 127.0.0.1 and ::1 in wheezy and sid, so this will be an issue long term.  Or at least until everyone uses v6 by default. ☺)

                
> 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: Matt Jordan
>         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