[asterisk-bugs] [JIRA] (ASTERISK-26430) res_hep will fail, when an IPv6 interface is enabled on the installed server

[Nir Simionovich (GreenfieldTech - Israel) (JIRA)]

Nir Simionovich (GreenfieldTech - Israel) created ASTERISK-26430:
--------------------------------------------------------------------

             Summary: res_hep will fail, when an IPv6 interface is enabled on the installed server
                 Key: ASTERISK-26430
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26430
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_hep
    Affects Versions: GIT
            Reporter: Nir Simionovich (GreenfieldTech - Israel)


When trying to utilize res_hep, while the server has an IPv6 IP address defined, the HEP report will fail, notifying the console:

[Oct  1 13:56:37] NOTICE[14719]: res_hep.c:466 hep_queue_cb: Unable to send packet: Address Family mismatch between source/destination

Additional information:

In order to investigate, I've added a couple of ast_log entries, in order to ascertain the actual discrepancy. The following is observed when the issue arises:

[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:472 ast_sockaddr_is_ipv4: My address family is: 2
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:473 ast_sockaddr_is_ipv4: My address family should be: 2
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:474 ast_sockaddr_is_ipv4: My address length is: 16
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:475 ast_sockaddr_is_ipv4: My address length should be: 16
[Oct  1 13:56:37] NOTICE[14719]: res_hep.c:467 hep_queue_cb: Sending from: 1
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:472 ast_sockaddr_is_ipv4: My address family is: 10
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:473 ast_sockaddr_is_ipv4: My address family should be: 2
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:474 ast_sockaddr_is_ipv4: My address length is: 28
[Oct  1 13:56:37] NOTICE[14719]: netsock2.c:475 ast_sockaddr_is_ipv4: My address length should be: 16
[Oct  1 13:56:37] NOTICE[14719]: res_hep.c:468 hep_queue_cb: To server: 0

The above was generated using:

int ast_sockaddr_is_ipv4(const struct ast_sockaddr *addr)
{

        ast_log(AST_LOG_NOTICE, "My address family is: %d\n", addr->ss.ss_family);
        ast_log(AST_LOG_NOTICE, "My address family should be: %d\n", AF_INET);
        ast_log(AST_LOG_NOTICE, "My address length is: %d\n", addr->len);
        ast_log(AST_LOG_NOTICE, "My address length should be: %u\n", sizeof(struct sockaddr_in));

        return addr->ss.ss_family == AF_INET &&
            addr->len == sizeof(struct sockaddr_in);
}

Now, if I disable IPv6 on the machine, using the following:

sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1

Now, the Asterisk output is as following:

[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:472 ast_sockaddr_is_ipv4: My address family is: 2
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:473 ast_sockaddr_is_ipv4: My address family should be: 2
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:474 ast_sockaddr_is_ipv4: My address length is: 16
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:475 ast_sockaddr_is_ipv4: My address length should be: 16
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:472 ast_sockaddr_is_ipv4: My address family is: 2
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:473 ast_sockaddr_is_ipv4: My address family should be: 2
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:474 ast_sockaddr_is_ipv4: My address length is: 16
[Oct  1 14:07:25] NOTICE[14975]: netsock2.c:475 ast_sockaddr_is_ipv4: My address length should be: 16

So, this is somewhat of an issue, as most cloud providers these day will enable by-default IPv6 addressing on the servers, making the module unusable till it's disabled - which is somewhat counter productive.

In order to validate potential configuration issues, I've tried changing my HEP server from IP:PORT combo, to only IP address - that caused Asterisk to go completely nuts. Recommendation, separate host ip and port to two separate configuration items, to avoid confusion.




--
This message was sent by Atlassian JIRA
(v6.2#6252)