[asterisk-bugs] [JIRA] (ASTERISK-18032) [patch] - IPv6 and IPv4 NAT not working

Valentin Vidić (JIRA) noreply at issues.asterisk.org
Mon Mar 30 17:52:33 CDT 2015


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

Valentin Vidić edited comment on ASTERISK-18032 at 3/30/15 5:51 PM:
--------------------------------------------------------------------

Original patch was for Debian package 1.8.13.1~dfsg1-3+deb7u3. I've upgraded to a newer version of the Debian package 11.13.1~dfsg-2 but the issue still persists unless the patch is applied.

The setup I have is an asterisk server running behind a NAT for IPv4 and on public addresses for IPv6. Here are the relevant setting from sip.conf:

udpbindaddr=::
localnet=10.0.0.0/255.255.255.0
externhost=cube.dyn.valentin-vidic.from.hr
externrefresh=60

Phones in localnet work without issues. Asterisk external address is 193.198.125.23 and after NAT it becomes 192.168.0.7. Test call is originated from Internet (address 212.15.176.39).

I am attaching a log file (asterisk.log) with the timeout error reported by asterisk and two pcap files with the same call before (ast11-nogo.pcap) and after applying the patch (ast11-go.pcap). In the first pcap file you will find one packet retransmitted several times until the call is finally dropped by asterisk. In the second pcap file internal address 192.168.0.7 is replaced in SDP with 193.198.125.23 and the call proceeds without problems.


was (Author: vvidic):
Original patch was for Debian package 1.8.13.1~dfsg1-3+deb7u3. I've upgraded to a newer version of the Debian package 11.13.1~dfsg-2 but the issue still persists unless the patch is applied.

The setup I have is an asterisk server running behind a NAT for IPv4 and on public addresses for IPv6. Here are the relevant setting from sip.conf:

udpbindaddr=::
localnet=10.0.0.0/255.255.255.0
externhost=cube.dyn.valentin-vidic.from.hr
externrefresh=60

Phones in localnet work without issues. Asterisk external address is 193.198.125.23 and after NAT it becomes 192.168.0.7. Test call is originated from Internet (address 212.15.176.39).

I am attaching a log file with the timeout error reported by asterisk and two pcap files with the same call before and after applying the patch. In the first pcap file you will find one packet retransmitted several times until the call is dropped.

> [patch] - IPv6 and IPv4 NAT not working
> ---------------------------------------
>
>                 Key: ASTERISK-18032
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18032
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/IPv6
>    Affects Versions: 1.8.3
>         Environment: AsteriskNOW 1.7.1
> CentOS 5.6
> Asterisk 1.8.3.3
> FreePBX 2.9
>            Reporter: Christoph Timm
>            Assignee: Valentin Vidić
>         Attachments: ast11-go.pcap, ast11-nogo.pcap, asterisk.log, call_from_extern_not_working.cap, call_from_intern_working.cap, full.zip, nat_with_ipv6.diff, sip_general_additional.conf
>
>
> Hi All,
> I tried to play a little bit with IPv6 to test our VoIP quality software with IPv6 RTP streams.
> I add "bindaddr=::" to the general section of the sip.conf and netstat shows that Asterisk is listing also on IPv6.
> My Asterisk server is behind a IPv4 NAT and was working absolutely perfect.
> But after my bindaddr change I got a problem with external calls.
> I spend some time to investigate this issue and found out the outbound calls are working. The externaddr is used in the SIP INVITE.
> If I received a inbound call the externaddr isn't used any more in SDP part of the answer from the Asterisk. The result is one way audio. In addition I saw the following message in the Asterisk log:
>     [May 25 19:18:18] WARNING[3674] chan_sip.c: Address remapping activated in sip.conf but we're using IPv6, which doesn't need it. Please remove "localnet" and/or "externaddr" settings.
> I think that is a bug because the externaddr is used correct during the outbound calls.



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



More information about the asterisk-bugs mailing list