This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XGFW still not support Jumbo Frame in virtualization feat. home lab.

  • Did you change the MTU of the Interface in the webadmin? 

    __________________________________________________________________________________________________________________

  • Yes.
    Initially, the MTU was changed on the web. When I rebooted XGFW, the interface started up and rebooted within 10 seconds, and this was repeated.
    The recorded video is a troubleshoot situation.

  • Which Interface driver on ESX do you use?

    __________________________________________________________________________________________________________________

  • The interface I use is VMXNET3. The VM Tools drivers used by VMXNET3 are managed by Sophos, so I can't check them.

    It is presumed that XGFW cannot properly process requests for packets larger than a certain size in the process of starting the interface immediately after booting.

    VMXNET3 is a 10G vNIC, and the physical interface is also 10G.
    It fails on both Intel and AMD.
  • There are plenty of issues with VMXNet3 Drivers.

    See: https://community.sophos.com/sophos-xg-firewall/f/discussions/113986/xg-home-edition-on-esxi-6-7-with-4-vnics---nics-order

    Did you try to use E1000 Drivers on Vmware? 

    Because there is a open issue with VMXnet3 Drivers in V18.0 and 10 mbit/s half duplex. Those could lead to reboots. 

    __________________________________________________________________________________________________________________

  • VMXNET3 was released 10 years ago and is the only 10G adapter for VMware virtualization in existence.

    If VMXNET3 is not supported, then customers using public cloud will grow and have nowhere to be deployed on the underlay network of VMware Virtual Data Center when planning hybrid cloud. The Synchrozied Security design will also be useless. The customer will look for an appliance from another vendor.

    I recommend resloving the problem before it's too late.

    Thanks for the feedback.

  • Sorry - again mix up both adapters. VMXnet3 are the correct adapters. E1000 Drivers causing certain issues in some deployments. 

    If you can reproduce this, as it looks, you could easily open a support case to get this resolved. 

    Because i cannot reproduce this as of today. 

    __________________________________________________________________________________________________________________

  • FormerMember
    0 FormerMember

    Hi, thanks for reaching out to Sophos Community.

    I tried to replicate the same scenario with jumbo-frame in my ESX environment and I am getting the same error. On my side of things, I have noticed a full CPU utilization before SFOS runs into kernel panic.

    I have dropped you a PM to get more details about your environment and get it checked here with our team.