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

    Parent interface of VLANs got down suddenly! | KVM pfsense

    Scheduled Pinned Locked Moved Virtualization
    14 Posts 3 Posters 1.8k 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.
    • M
      mrbankheadgmail.com
      last edited by

      Did it help?  *(disabling checksum offload)  - because it did not seem to help in my case.

      1 Reply Last reply Reply Quote 0
      • R
        Refast
        last edited by

        Thanks for the suggestion. Till now it seems that the issue has been fixed! I'm still observing the firewall and I will update this thread in case there is an update. Thank you once again for the quick and smart suggestion.

        Best wishes!

        1 Reply Last reply Reply Quote 0
        • R
          Refast
          last edited by

          Hello there! Unfortunately the issue occurred again today. But this time it took a relatively long time in comparison to the other periods I've been observing for a while. Regarding your question about the kind of VNICs I am using, I use this configuration for the interfaces

          (
              <interface type="direct"><mac address="52:54:00:12:ee:67"><source dev="em1" mode="bridge">
                <model type="rtl8139"><address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0">

          )

          and you asked for logs but I couldn't determine which logs you exactly need. Therefore, could you please be more specific regarding the logs that you need.

          Thanks in advance</address></model></mac></interface>

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

            I meant the system log. Status > System Logs > System > General
            If there are some issues related to interface drop-outs you should find log entries there.

            pfSense works better with an e1000 NICs than with the rtl, but don't know, if that helps here.

            1 Reply Last reply Reply Quote 0
            • R
              Refast
              last edited by

              I can't use "e1000" NICs as the firewall VLANs become offline after applying the changes for the new option(which is "e1000"). Any suggestion?

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

                As far as I know, the e1000 supports VLAN.  ???
                I'm using virtIO NICs with my virtualized pfSense on KVM without no issue, since I've deactivated checksum offloading. And I've also defined multiple VLANs on one NIC.

                1 Reply Last reply Reply Quote 0
                • R
                  Refast
                  last edited by

                  I am still trying to fix this problem although I'm not pretty sure whether it has been solved! Anyway, may you share with me your KVM configuration regarding the interfaces parts?

                  Thanks

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

                    Here's the interface setting of the virtual machine interface, where I'm running multiple vLANs on in pfSense:

                    
    <interface type="network"><mac address="52:54:00:e9:79:76"><source bridge="br.wifi">
      <model type="virtio"><address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x0">

The host network bridge is controlled by wickedd. No special settings in the ifcfg-br.wifi:

                    BOOTPROTO='none'
                    BRIDGE='yes'
                    BRIDGE_FORWARDDELAY='0'
                    BRIDGE_PORTS='eth2'
                    BRIDGE_STP='off'
                    BROADCAST=''
                    ETHTOOL_OPTIONS=''
                    IPADDR=''
                    MTU=''
                    NAME=''
                    NETMASK=''
                    NETWORK=''
                    REMOTE_IPADDR=''
                    STARTMODE='auto'

                    
The eth2 config:

                    BOOTPROTO='none'
                    BROADCAST=''
                    DHCLIENT_SET_DEFAULT_ROUTE='no'
                    ETHTOOL_OPTIONS=''
                    IPADDR=''
                    MTU=''
                    NAME='I211 Gigabit Network Connection'
                    NETMASK=''
                    NETWORK=''
                    REMOTE_IPADDR=''
                    STARTMODE='auto'
                    PREFIXLEN=''

                    
The interface is connected to an Engenius Wifi AP and there are 5 vLAN configured on it in pfSense, no conventional network.</address></model></mac></interface>
                    1 Reply Last reply Reply Quote 0
                    • R
                      Refast
                      last edited by

                      Thank you for sharing this with me. I will double check the settings of mine as well as of yours and update my settings accordingly. I will update this thread if there is any update.

                      Kind regards.

                      1 Reply Last reply Reply Quote 0
                      • R
                        Refast
                        last edited by

                        Hello there! Unfortunately the problem occurred again today. For those of you who are asking for "system logs" here are what I got

                        May 16 09:21:20 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD2 172.16.6.2: sendto error: 64
                        May 16 09:21:20 dpinger WB_EDU 172.16.6.21: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD3 172.16.6.3: sendto error: 64
                        May 16 09:21:20 dpinger WB_OFF 172.16.6.22: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD1 172.16.6.1: sendto error: 64
                        May 16 09:21:20 dpinger WB_OOF_BNS 172.16.6.28: sendto error: 64
                        May 16 09:21:20 dpinger WB_WAHO 172.16.6.27: sendto error: 64
                        May 16 09:21:20 dpinger LANs_Bridge 172.16.101.10: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD2 172.16.6.2: sendto error: 64
                        May 16 09:21:20 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
                        May 16 09:21:20 dpinger WB_EDU 172.16.6.21: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD3 172.16.6.3: sendto error: 64
                        May 16 09:21:20 dpinger WB_OFF 172.16.6.22: sendto error: 64
                        May 16 09:21:20 dpinger WB_RD1 172.16.6.1: sendto error: 64
                        May 16 09:21:19 dpinger WB_OOF_BNS 172.16.6.28: sendto error: 64
                        May 16 09:21:19 dpinger WB_WAHO 172.16.6.27: sendto error: 64
                        May 16 09:21:19 dpinger LANs_Bridge 172.16.101.10: sendto error: 64
                        May 16 09:21:19 dpinger WB_MAJ_BNS1 172.16.6.24: sendto error: 64
                        May 16 09:21:19 dpinger WB_RD2 172.16.6.2: sendto error: 64
                        May 16 09:21:19 dpinger WB_EDU 172.16.6.21: sendto error: 64
                        May 16 09:21:19 dpinger WB_RD3 172.16.6.3: sendto error: 64
                        May 16 09:21:19 dpinger WB_OFF 172.16.6.22: sendto error: 64

                        So is there any idea to fix this problem?

                        1 Reply Last reply Reply Quote 0
                        • R
                          Refast
                          last edited by

                          Is there any suggestion for this?

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