search

ciniml / WireGuard-ESP32-Arduino

WireGuard implementation for ESP32 Arduino
Other
804 stars 64 forks source link

Connect to ESPAsyncWebServer / ArduinoOTA / Services on ESP32 #37

Open itsyoshio opened 8 months ago

itsyoshio commented 8 months ago

Hi, i'm using the Example code and Outbound connections work well.

I've successfully pinged my Router (also the Wireguard Server) and used the WiFiClient to fetch a Website on my Wireguard Network over HTTP.

The ESP32 i use as the Wireguard Client also runs a ESPAsyncWebServer (port 80) and ArduinoOTA (port 32537).

I can't ping it, i can't access the Webserver and OTA Updates also don't work within the VPN, but do run over Ethernet or Wifi directly.

Any help would be appreciated.

Shinmera commented 8 months ago

I'm having the same issue using the standard esp_http_server. Outbound is OK, inbound ends up with unreachable address.

Is there some kind of routing we have to perform to make sure the packets arrive at the correct place?

MrKappa commented 7 months ago

Have you in the Peer's allowed IPs the IP or the subnet containing your interface IP address?

Shinmera commented 7 months ago

In my case yes. I'm using exactly the same configuration as for every other client in the net, and the rest work just fine.

MrKappa commented 7 months ago

In my case yes. I'm using exactly the same configuration as for every other client in the net, and the rest work just fine.

Is your device wg ip pingable? If yes, looks like the problem could be that the service isn't listening/binding to the wg created interface. Can you try to start the tunnel and then initialize/start your services? Otherwise I'd look how those services bind to the network interfaces.