Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Asterisk addon package not routing traffic down ipsec tunnel…?

    Scheduled Pinned Locked Moved IPsec
    1 Posts 1 Posters 1.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      whitewidow
      last edited by

      I have a IPSEC VPN connections between 2 locations.

      Location 1 Has a pfsense router (10.0.1.254) with a dedicated Asterisk server (10.0.1.2) behind the routers LAN port.

      Location 2 is a pfSense Netgate router with Asterisk installed on the router (10.0.9.254)

      At location 2 anything behind the Netgate router LAN port (10.0.9.254) ipsec traffic travels to Location 1 (10.0.1.0/24) fine with out issues. But from inside the Netgate router (10.0.9.254) either via trying to ping in the GUI or ssh the Location 1's network (10.0.1.0/24)  no packetes travel down the VPN.

      So my issues is that I have short codes (ie *80) to dial the two locations but since Asterisk is not using the VPN tunnel on the Location 2 Netgate router (10.0.9.254) they time out.

      I need to find out how to get Asterisk from Location 2 to communicate down the VPN. Right now it simply does not even see the 10.0.1.0/24 network at location 1 from inside the router.

      Testing from Location 1's router and Asterisk Server I can ping Location 2's router. I cannot ping from inside Location 2's router or Asterisk CLI to Location 1's network (10.0.1.0/24)

      Ping output:

      
      PING 10.0.9.254 (10.0.9.254) from 10.0.1.254: 56 data bytes
      64 bytes from 10.0.9.254: icmp_seq=0 ttl=64 time=22.600 ms
      64 bytes from 10.0.9.254: icmp_seq=1 ttl=64 time=30.619 ms
      64 bytes from 10.0.9.254: icmp_seq=2 ttl=64 time=21.115 ms
      
      --- 10.0.9.254 ping statistics ---
      3 packets transmitted, 3 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 21.115/24.778/30.619/4.174 ms
      
      
      
      PING 10.0.1.254 (10.0.1.254): 56 data bytes
      
      --- 10.0.1.254 ping statistics ---
      3 packets transmitted, 0 packets received, 100.0% packet loss
      
      
      
      Pinging 10.0.1.254 from 10.0.9.13 with 32 bytes of data:
      Reply from 10.0.1.1: bytes=32 time=26ms TTL=126
      Reply from 10.0.1.1: bytes=32 time=24ms TTL=126
      Reply from 10.0.1.1: bytes=32 time=25ms TTL=126
      Reply from 10.0.1.1: bytes=32 time=23ms TTL=126
      
      Ping statistics for 10.0.1.254:
          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
          Minimum = 23ms, Maximum = 26ms, Average = 24ms
      
      
      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.