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

    Clients on bridged VPN can't see each other

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 2.6k 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
      kextyn
      last edited by

      I have a working bridged VPN setup but when I tried to connect two remote PCs I found that they couldn't talk to each other.  It also appears that a client on the local LAN can only ping one of the remote PCs at a time.  If only one is connected they talk fine.  If I connect a second one the two remote PCs can ping the local PC but the local PC can only ping one of the remotes.  But no matter what the two remotes can not ping each other.

      My configuration pretty much looks like http://stuff.kextyn.com/pfsense-bridged13.jpg except there is no "local network" specified.  Of course my IPs and certificates/keys are different as well.  I've also added these lines to the config.xml: http://stuff.kextyn.com/pfsense-bridged14.jpg  I have rules on WAN and LAN to pass everything (I recreated it in a virtual environment for testing.)

      Am I doing something wrong or am I missing a custom command?

      1 Reply Last reply Reply Quote 0
      • A
        afvadmin
        last edited by

        push your dns name and settings if applicable and also include the local network, do an ipconfig on each computer to see what ip addresses they are getting from the set up in the picture they should be getting 192.168.1.40 and 41 and try disabling the client to client option since the connection is bridged dont think you need extra routing to route packets from one remote to another

        1 Reply Last reply Reply Quote 0
        • K
          kextyn
          last edited by

          I have tried with Client-to-client enabled and disabled.  The PCs are getting the proper IPs and related settings.

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