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

    [soled] Site B ping site A but site A does not ping site B

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 1 Posters 629 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.
    • V
      violinipa
      last edited by

      Hi forum!
      I have 2 pfsense configured in OpenVPN site to site
      The connection is made properly but if i use the tunnel in /24 mode (10.128.0.0/24) the ping from site A to site B does not work
      If i change the tunnel in /30 mode (10.128.0.0/30) the ping work in both direction (i tried /30 only for troubleshooting, i need /24 because i have many vpn clients)

      Site A config (Server )

      Lan Subnet: 10.0.1.0/24

      Server mode: Peer to Peer
      Protocol: TCP
      Device mode: tun
      Interface: WAN
      Local port: 443
      IPv4 Tunnel Networ: 10.128.0.0/24
      IPv4 Local Network: 10.0.1.0/24

      Site B config (Client)

      Lan Subnet: 10.0.4.0/24

      Server mode: Peer to Peer
      Protocol: TCP
      Device mode: tun
      Interface: WAN
      Server host or address: site B pubblic IP
      Server port: 443

      I have 100 or more client vpn site so i substitute the config "ipV4 Remote Networ" or the "Custom Option" route 10.0.x.0 255.255.255.0  with RIP
      I enabled RIP service in all pfSense and i selected LAN and OpenVPN interfaces

      The routing tables its seems corrects but the traffic work only from client to server

      thank you for your help

      1 Reply Last reply Reply Quote 0
      • V
        violinipa
        last edited by

        I missed iroute in client overrides :)

        From official documentations:
        For a site-to-site SSL/TLS server using IPv4, the IPv4 Tunnel Network size can alter how the server behaves. If x.x.x.x/30 is entered for the IPv4 Tunnel Network then the server will use a peer-to-peer mode much like Shared Key operates: It can only have one client, does not require client-specific overrides or iroutes, but also cannot push routes or settings to clients. If an IPv4 Tunnel Network larger than that is used, such as x.x.x.x/24, the server will accept multiple clients and can push settings, but does require iroutes.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.