I'm trying to setup my Raspberry Pi 3 as a USB server over Wi-Fi as an ad-hoc network using Virtual Here. I have succeeded in getting it to work over my local network, but as soon as I create an Ad-Hoc network on the Pi and connect to it with my laptop, it can no longer connect to the server on the Pi. I have allowed TCP 7575 and UPD 5353 through my firewall, and I have set a static IP on the Pi using nmtui, but so far no luck. Not sure what I'm missing, or if Windows 10/11 are the issue.
.
I think Microsoft removed ad-hoc support in windows 10. Its probably easier to just setup the pi as an Access Point(AP) and join that. Or you can do vise versa and use Microsoft Windows HotSpot and get the pi to join that.
.
I just tried doing it as an access point, and I'm having the same issue. The Virtual Here client isn't connecting to the server on the Pi.
.
It works fine so its something with your setup. Can you ping the pi from your pc?
.
The Pi for some reason isn't holding the static IP. When I run ifconfig over SSH, wlan0 doesn't show an IP address. I am able to ping the Pi with the host name, though.
.
I dont know sorry. I dont debug network issues. Just setup the pi with a basic AP. Then when thats working you can experiment with different setups eg static IP etc.