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

    Site to site ping with VLAN?

    Scheduled Pinned Locked Moved OpenVPN
    23 Posts 4 Posters 1.1k 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.
    • K
      killmasta93
      last edited by

      the new routing table on site 2 pfsense

      default	181.57.181.xx	UGS	46042966	1500	vtnet1	
      127.0.0.1	link#4	UH	494	16384	lo0	
      181.57.181.xx/30	link#2	U	670282	1500	vtnet1	
      181.57.181.xx	link#2	UHS	0	16384	lo0	
      192.168.0.0/22	192.168.90.1	UGS	17521	1500	ovpnc1	
      192.168.15.0/24	link#1	U	46559	1500	vtnet0	
      192.168.15.254	link#1	UHS	0	16384	lo0	
      192.168.80.0/24	192.168.80.2	UGS	0	1500	ovpns2	
      192.168.80.1	link#8	UHS	0	16384	lo0	
      192.168.80.2	link#8	UH	0	1500	ovpns2	
      192.168.90.1	link#7	UH	0	1500	ovpnc1	
      192.168.90.2	link#7	UHS	0	16384	lo0
      

      Should i reboot because the ping is not working though

      Tutorials:

      https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

      1 Reply Last reply Reply Quote 0
      • M
        marvosa
        last edited by marvosa

        Correct, the issue is at site 2. It looks like you made adjustments to ovpns2, which is the first step, so now we need to get the correct route added for 192.168.60.0/24. Rebooting will work, but we can use that as the last resort cause we should be able to resolve this without a reboot. I would try bouncing the tunnel first in one of two ways:

        1. Status -> Services, then restart the service that is running the tunnel to site 1
        2. VPN -> OpenVPN -> Servers, then edit the server that is running the tunnel to site 1 and re-save it.

        After the tunnel is bounced, check the routing table on site 2... there should now be a route for 192.168.60.0/24 using 192.168.90.1 as the gateway on the ovpnc1 interface. If not, then go ahead and reboot site 2.

        Once you see the route mentioned above, you should now be able to communicate across the tunnel to VLAN 60.

        1 Reply Last reply Reply Quote 1
        • K
          killmasta93
          last edited by

          Thank you for the reply, that did the trick i rebooted and it started to work flawless
          Thank you again for all the help

          Tutorials:

          https://www.mediafire.com/folder/v329emaz1e9ih/Tutorials

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