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

    Route is not working until ping command

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 1.5k 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.
    • H
      HerrKlauss
      last edited by

      Hi, I have weird problem for me :)

      I am routing local network (eth0) to VPN network (eth1)

      Local network 10.25.1.0/24 - GW 10.25.1.1
      VPN network 10.11.12.0/24 - GW 10.11.12.1

      On VPN network is Cisco ASA on IP 10.11.12.2 - I have this as another GW setup in pfsense.

      Static routes are set: 192.168.1.0/24 via 10.11.12.2

      FW rules set from local network to VPN netork - everything can communicate

      Pass * * * 10.25.1.0/24 to 10.11.12.0/24 * *

      FW rules set in VPN network - everything can communicate to local network and everything can communicate via optional GW 10.11.12.2

      Pass * * * 10.11.12.0/24 to 10.25.1.0/24 * *
      Pass * * * * to * via 10.11.12.2

      Everything looks fine, but commication is working only after I run ping to 192.168.1.X machine.
      Ping is working well, and after ping is working everything, but if I will not use ping first, no communication.

      Can anyone explain me, what is causing thins and how i can fix it?

      Thanks :)

      1 Reply Last reply Reply Quote 0
      • H
        HerrKlauss
        last edited by

        I think the problem can be PROXY ARP.

        On the Cisco ASA is proxy arp enabled.

        How is possible enable or check if proxy arp is working on pfsense?

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