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

    PFSense dropping on LAN with KVM

    Virtualization
    2
    4
    597
    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.
    • G
      GregUS
      last edited by GregUS

      Hello,

      I've come across a problem that has me stumped. I've created a "test" network, with pfSense running as a VM. I've run this setup before without problem on VirtualBox, but running it under KVM seems to cause a problem.

      The setup:
      WAN: 192.168.1.200/24 [Local network behind my ISP's router]
      LAN 10.0.0.1/20 - [VM's reside here]

      For some reason, when I boot a VM, no traffic is passed to the WAN. No ping, ssh, DNS, or anything else. When I've enabled logging, I can't find a rule that's dropping any traffic.

      However, if I re-assign the pfSense LAN interface and redefine it using the same settings, everything suddenly works. For the life of me, I can't figure out why.

      Can anyone guess what might be going on?

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Did you disable Hardware Checksum Offloading in System > Advanced > Networking?

        1 Reply Last reply Reply Quote 0
        • G
          GregUS
          last edited by

          viragomann, I did try that, just now. It seems like it describes the problem, but didn't seem to fix it.

          Upon rebooting a system on the LAN side, no connectivity. Once I reboot the pfsense instance or reconfigure the LAN adapter, suddenly everything passes from LAN to WAN.

          1 Reply Last reply Reply Quote 0
          • G
            GregUS
            last edited by

            It seems I might have made a mistake in my virtual network configuration. I tried ssh'ing to the gateway 10.0.0.1, and lo and behold, an ssh server running. Turns out it was my virtualization host listening on that address. A reboot of the router must have made it also on that address (is that possible?) temporarily.

            > virsh net-dumpxml lan_priv
            <network connections='2'>
              <name>lan_priv</name>
              <uuid>567ca017-512e-4211-87c7-ae0193806d20</uuid>
              <bridge name='virbr1' stp='on' delay='0'/>
              <mac address='52:54:00:2e:3d:0f'/>
              **<ip address='10.0.0.1' netmask='255.255.240.0'>**
                                ^^^^^ (oops)
              </ip>
            </network>
            
            I believe it should be **"10.0.0.0"** for the network ip address.
            
            I'll clean everything up and report the results.
            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.