----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviewboard.asterisk.org/r/4563/#review15110 -----------------------------------------------------------
Did this really apply to all operating systems and all versions of Linux? We had a discussion about it when the IPv6 support was added, but I don't remember all the details - but something with the mapping was O/S and sysctl dependent. - Olle E Johansson On March 30, 2015, 4:23 p.m., Valentin Vidić wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviewboard.asterisk.org/r/4563/ > ----------------------------------------------------------- > > (Updated March 30, 2015, 4:23 p.m.) > > > Review request for Asterisk Developers. > > > Bugs: ASTERISK-18032 > https://issues.asterisk.org/jira/browse/ASTERISK-18032 > > > Repository: Asterisk > > > Description > ------- > > When udpbindaddr=:: is set Asterisk accepts IPv4 and IPv6 clients both stored > in a struct sockaddr_in6 with AF_INET6 family type. Current NAT code for IPv4 > checks if the socket type is AF_INET6 and thus fails to handle IPv4 mapped > addresses properly. The patch adds an additional check for this case allowing > IPv4 clients to be handled by NAT even when IPv6 is enabled. > > > Diffs > ----- > > /branches/11/channels/chan_sip.c 433794 > > Diff: https://reviewboard.asterisk.org/r/4563/diff/ > > > Testing > ------- > > Patch solves the problem of failing incoming calls on a local NATed > installation with IPv6 sockets enabled. > > > Thanks, > > Valentin Vidić > >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
