FLINT 3 Blocking Windows and Linux Devices from communicating

I use a custom setup where I use RDP to connect to Framework laptops, one running windows 11 and the other Arch Linux to each other.

If I use my Beryl AX, then the RDP and pinging connections work fine. But the Flint 3 seems to block the Linux Machine from access the windows machine.

When I try to ping the windows machine from the linux machine, though both clients show in the Router, the routing fails entirely. This also causes RDP connections to fail entirely as well.

Hi,

Could you help to check the following?

  1. Are the Linux and Windows devices connected to the Main Wi-Fi or LAN, rather than the Guest Wi-Fi? (Guest networks have built-in isolation that prevents devices from seeing each other).

  2. When switching to the Flint 3, did you select the correct Network Profile (set it to "Private" rather than "Public") on your Windows device? You might also try temporarily disabling the firewall to see if it is blocking local discovery.

  3. If you are connected to the Main Wi-Fi, please ensure that AP Isolation is not enabled under Admin Panel -> Network.

  4. If you are using MLO Wi-Fi, please try connecting to a specific, separate frequency band (e.g., 6GHz, 5GHz or 2.4GHz only) to see if local connectivity returns to normal.

Yes it does seem to be linked to MLO!

It is odd, linux devices can talk to each other, but windows and linux machines cannot communicate properly when they are on different bands of the WIFI connection.

Do you mean that:

  • Both the Linux and Windows devices are connected to the MLO SSID.
  • However, they might be using different combinations of bands (e.g., Linux is on 2.4GHz + 5GHz, while Windows is on 5GHz + 6GHz).
  • In this scenario, the Linux and Windows devices are unable to communicate with each other?

If our understanding is correct, could you please perform the following checks:

  1. ARP Table Check: Are both Linux and Windows correctly processing ARP (Address Resolution Protocol)? Please run these commands and check if the other device's IP and MAC address appear in the list:
    # On Windows CMD
    arp -a
    
    # On Linux 
    ip neighbour
    
  2. Frequency Isolation Test: If you connect both Windows and Linux to a standalone 5GHz band (instead of the MLO SSID), does the problem still occur?