Skip to contentSkip to conversation

How to detect the IP CAM on LAN from WG tunnel ?

DISCUSSION Nohk Two 3 participants 4 messages Jun 20, 2024 – Jun 21, 2024

lore
Share & tools
lore

Nohk Two

author
#0 lore raw

Hi,

This seems a common question but I don't know how do you solve this problem.

My machine has an ethernet interface: eth0
It's network is 192.168.100.1/24

I created a wireguard interface thru eth0: wg0
It's network is 192.168.128.1/24

I have an IP CAM on the LAN: cam1
It's network is 192.168.100.21/24
This is physically on the same LAN as my machine's eth0.

My machine has a MASQUERADE iptable entry in the nat table:
iptables -t nat -A POSTROUTING -s 192.168.128.0/24 -o eth0 -j MASQUERADE

My phone uses the wireguard connect to my machine's wg0.
This wireguard configuration allow 192.168.100.0/24. My phone's wireguard VPN IP address 192.168.128.10/24.

So my phone should be able to connect to my IP CAM without problem.
192.168.128.10(phone) source NAT as 192.168.100.1(eth0) then connect to 192.168.100.21(cam1) 192.168.100.21(cam1) reply to 192.168.100.1(eth0) then NAT rewrite to 192.168.128.10(phone)

However, the IP CAM's mobile App on my phone never remember the IP CAM's IP address and will always scan the network to find out the IP CAM. Then Failed if my phone uses the wireguard VPN.

Maybe the problem is that my phone and the IP CAM have different network, 192.168.128.0/24 vs 192.168.100.0/24.

How do you solve this problem ?

#1 lore raw
Quoted 1 line

How do you solve this problem ?

Iterative fact checking, from the lowest levels of the network stack to the highest.

- Are the devices actually connected where you think they are?
- With the tunnel disconnected, does your phone connect to the camera?
- Is your Wireguard tunnel set up properly?
- Can your phone ping the wg0 address with the tunnel active?
- Can your phone ping other .100 devices with the tunnel active?
- Does your eth0/wg0 machine have IP forwarding enabled?
- sysctl net.ipv4.ip_forward=1
- What does packet tracing show?
- I.e. ngrep -d wg0 .\* icmp or the tcpdump equivalent, also against eth0 for the wireguard UDP port.
- Does the mobile App actually support remote (routed) cameras or just on the local network?

Signature · 1 line
Mark Lawrence
author
#2 lore raw
Quoted 6 lines · Mark Lawrence
Quoted 1 line

How do you solve this problem ?

Iterative fact checking, from the lowest levels of the network stack to the highest.

    - Are the devices actually connected where you think they are?
        - With the tunnel disconnected, does your phone connect to the           camera?

I use wireguard VPN while my phone is using mobile data (4G LTE). With the tunnel disconnected my phone can't connect to the camera since it scanned and cannot find the camera.

Quoted 3 lines

    - Is your Wireguard tunnel set up properly?
        - Can your phone ping the wg0 address with the tunnel active?
        - Can your phone ping other .100 devices with the tunnel           active?

I don't know how to ping from my phone. But the phone, with the wireguard tunnel connected, can visit my LAN website which is in the network 192.168.100.0/24.

Quoted 2 lines

    - Does your eth0/wg0 machine have IP forwarding enabled?
        - sysctl net.ipv4.ip_forward=1

Yes.

$ sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
Quoted 2 lines

    - What does packet tracing show?
        - I.e. ngrep -d wg0 .\* icmp or the tcpdump equivalent, also           against eth0 for the wireguard UDP port.

I use ngrep -d wg0 .\* icmp, but nothing dump. However while I open my phone's browser to visit my LAN site, it did dump something.

Quoted 2 lines

    - Does the mobile App actually support remote (routed) cameras or       just on the local network?

This is the point I said in my original mail that I think my phone and the camera are in different networks. I believe this App is for LAN network.

For this scenario, are there solutions ?

#3 lore raw

In case the camera app uses something below IP, eg ARP to discover you don’t have a chance, since it will never cross the wireguard tunnel.
You should try to capture somehow what the app is doing, and then work from that. Either they do not accept the Wireguard routes or they are using non-IP discovery that does not get routed through wg.

Good luck!
Domi

Quoted 28 lines

21.06.2024 dátummal, 12:42 időpontban Nohk Two <[email protected]> írta:

Quoted 4 lines · Mark Lawrence
Quoted 1 line

How do you solve this problem ?

Iterative fact checking, from the lowest levels of the network stack to the highest.
- Are the devices actually connected where you think they are?
- With the tunnel disconnected, does your phone connect to the camera?

I use wireguard VPN while my phone is using mobile data (4G LTE). With the tunnel disconnected my phone can't connect to the camera since it scanned and cannot find the camera.

Quoted 3 lines

- Is your Wireguard tunnel set up properly?
- Can your phone ping the wg0 address with the tunnel active?
- Can your phone ping other .100 devices with the tunnel active?

I don't know how to ping from my phone. But the phone, with the wireguard tunnel connected, can visit my LAN website which is in the network 192.168.100.0/24.

Quoted 2 lines

- Does your eth0/wg0 machine have IP forwarding enabled?
- sysctl net.ipv4.ip_forward=1

Yes.

$ sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
Quoted 2 lines

- What does packet tracing show?
- I.e. ngrep -d wg0 .\* icmp or the tcpdump equivalent, also against eth0 for the wireguard UDP port.

I use ngrep -d wg0 .\* icmp, but nothing dump. However while I open my phone's browser to visit my LAN site, it did dump something.

Quoted 1 line

- Does the mobile App actually support remote (routed) cameras or just on the local network?

This is the point I said in my original mail that I think my phone and the camera are in different networks. I believe this App is for LAN network.

For this scenario, are there solutions ?