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

    Machine is reachable within it's own network but cant be reached from other networks

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 338 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.
    • S
      soupdiver
      last edited by soupdiver

      I have a pfSense running inside Proxmox.
      I want to access the Proxmox UI through that pfSense.
      I created an extra bridge on the host, assigned it an IP and hooked up pfSense to that bridge as well.
      10.240.0.1 pfSense
      10.240.0.2 host

      Both addresses can reach other but I can not access 10.240.0.2 from another network.
      However a ping to 10.240.0.1 works fine from other networks.

      What am I missing? Maybe a route somewhere?

      Since I can reach 10.240.0.1 from other networks I think the routing in general works. But why would it fail for the last hop if it works fine from within the 10.240 network?

      Edit:
      Routes on the host:

      ip route
      default via x.x.x.x dev vmbr0 proto kernel onlink
      10.0.0.0/16 dev vmbr5 proto kernel scope link
      10.10.0.0/16 dev vmbr5 proto kernel scope link
      10.240.0.0/16 dev vmbr5 proto kernel scope link src 10.240.0.2
      

      config vmbr5

      auto vmbr5
      iface vmbr5 inet static
      	address 10.240.0.2/16
      	bridge-ports none
      	bridge-stp off
      	bridge-fd 0
      #Host
      
      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @soupdiver
        last edited by

        @soupdiver said in Machine is reachable within it's own network but cant be reached from other networks:

        Both addresses can reach other but I can not access 10.240.0.2 from another network.

        Another network behind pfSense like a VM on a different Proxmox bridge?

        Maybe Proxmox blocks access from outside of its subnet.

        1 Reply Last reply Reply Quote 0
        • S
          soupdiver
          last edited by

          Seems the issue was with my route.
          I had to specify the ip and not only the dev
          e.g. route add 10.0.0.0/16 via 10.240.0.1

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