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

    Routing between two networks over 1 physical interface not working anymore

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 378 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.
    • A
      astrakid
      last edited by

      hi,
      after a total outage of my server i recovered mostly everything. one step is missing, and i am sure it is the configuration on my hypervisor.

      i am running a single server system with proxmox. in a virtual machine pfsense is doing all the stuff (simple firewalling, dhcp, dns, ...).

      proxmox: 1 NIC
      pfsense: 2 virtual NICs (LAN 10.1.1.4/14 and WAN 192.168.1.2/24)

      the wan router and all devices are connected to the same switch. all requests from my LAN to WAN are forwarded to the default gateway (pfsense). pfsense forwards the to the wan-router.

      hypervisor network configuration:

      iface enp3s0 inet manual
      
      auto vmbr0
      iface vmbr0 inet static
              address 10.1.1.2/14
              gateway 10.1.1.4
              bridge-ports enp3s0
              bridge-stp off
              bridge-fd 0
              dns-nameservers 10.1.1.4 192.168.1.1
      

      pfsense has vmx0 (LAN) and vmx1 (WAN).

      it looks all fine from my perspective, but route requests to WAN are not transferred to WAN-gateway.

      is the main cnfiguration right? i compared with my backup, and i can't find a difference? i tried to get it all up and running for about 12 hours now... my children are getting angry. 😊

      regards,
      andre

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

        oh man... i guess it was a reboot that i missed after changing ipv4_forward in sysctl.conf to 1 - or just do a sysctl -p... however it works now 🤦

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