esp_wifi_repeater icon indicating copy to clipboard operation
esp_wifi_repeater copied to clipboard

No routing from main network to client connected to WiFi repeater

Open pfugazzi opened this issue 4 years ago • 4 comments

Hi Martin,

I've a problem to connect device from main network to a client connected via WiFi repeater.

The main network is a Raspbery Pi
network 192.168.10.0/24 The ESP as WiFi repeater is configured as static IP: STA: IP: 192.168.10.100 Netmask: 255.255.255.0 Gateway: 192.168.10.1 IP:192.168.4.0/24 [NAT] I've a ESP32CAM connected to WiFi repeater with a static IP 192.168.4.50

RaspPi (192.168.10.1) < (192.168.10.100) WiFi repeater (192.168.4.1) > (192.168.4.50) ESPCAM

On Raspberry I set a route to network behind WiFi repeater sudo ip route add 192.168.4.0/24 via 192.168.10.100

From Rasperry or a PC connected to I'm able to ping the ESPCAM but 'curl' as same as via browser I cannot reach ESPCAM and straming .

While if connect the PC directly to WiFi repeater it's working.

Seems some settings are missing on WiFi repeater to allow device from main network to access to device on WiFi repeater via TCP/UDP/HTML.

I take a look on readme and issues but I'm not able to address the topic, could you help me?

Thanks in advance Paolo

I'

pfugazzi avatar Dec 03 '20 10:12 pfugazzi

By default, the esp_wifi_repeater is a NAT router. Similar to a standard home router you will neet port-forwarding to access nodes and ports in the NATed network (behind the AP of the ESP). You can use the portmap command to do so: https://github.com/martin-ger/esp_wifi_repeater#routing

Another option might be to disable NATing ("set nat 0") and configure static routes on all nodes.

martin-ger avatar Dec 03 '20 11:12 martin-ger

Martin, thanks a lot, just a bit more could you please send me an example about how to configure the route? I'm not expert on the matter and any attempt I did failed. Thanks in advanceRegardspaolo

----Messaggio originale----

Da: [email protected]

Data: 3-dic-2020 12.11

A: "martin-ger/esp_wifi_repeater"[email protected]

Cc: "pfugazzi"[email protected], "Author"[email protected]

Ogg: Re: [martin-ger/esp_wifi_repeater] No routing from main network to client connected to WiFi repeater (#426)

By default, the esp_wifi_repeater is a NAT router. Similar to a standard home router you will neet port-forwarding to access nodes and ports in the NATed network (behind the AP of the ESP). You can use the portmap command to do so: https://github.com/martin-ger/esp_wifi_repeater#routing

Another option might be to disable NATing ("set nat 0") and configure static routes on all nodes. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

pfugazzi avatar Dec 03 '20 16:12 pfugazzi

If you go for the second option "to disable NATing ("set nat 0") and configure static routes on all nodes." you should do the following:

On the esp (after configuring the WiFi) enter:

set net 0
save

on the raspberry: sudo add route -net 192.168.4.0/24 gw 192.168.10.100 (as you already did).

Now you can connect to 192.168.4.50 from the raspberry, given that you have configured 192.168.4.1 as default gateway on the espcam.

martin-ger avatar Dec 03 '20 19:12 martin-ger

Many thanks Martin

----Messaggio originale----

Da: [email protected]

Data: 3-dic-2020 20.18

A: "martin-ger/esp_wifi_repeater"[email protected]

Cc: "pfugazzi"[email protected], "Author"[email protected]

Ogg: Re: [martin-ger/esp_wifi_repeater] No routing from main network to client connected to WiFi repeater (#426)

If you go for the second option "to disable NATing ("set nat 0") and configure static routes on all nodes." you should do the following:

On the esp (after configuring the WiFi) enter: set net 0 save

on the raspberry: sudo add route -net 192.168.4.0/24 gw 192.168.10.100 (as you already did).

Now you can connect to 192.168.4.50 from the raspberry, given that you have configured 192.168.4.1 as default gateway on the espcam. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

pfugazzi avatar Dec 03 '20 20:12 pfugazzi