I can confirm this happens as well on Flatpak (Alpine Linux though not very relevant since it's Flatpak). With iwd+networkmanager Steam works fine, but when using iwd as standalone network implementation Steam refuses to launch the interface and eventually throws the error 0x3000.
iwd by itself works perfectly well and this problem only happens on Steam.
In a nutshell: networkmanager + iwd works perfectly well, but iwd as standalone network backend causes this issue
Nothing extracted yet.
Your system information
steamlogs.tar.gz
Please describe your issue in as much detail as possible:
When I try to open a store, community or profile page, this very page should open, because the connection is set up, though via iwd. But for some reason Steam gives the page http://error/, saying there is no internet connection (error 105).
But if I manage to connect to the internet via NetworkManager GUI, all the pages start loading. All other client functionality works fine in both cases
Steps for reproducing this issue:
1.Connect to internet via iwd
2.Open Steam client
3.Open Steam store