Is it possible to give an Android VPN Client an IP on the same subnet as the rest of my network?

[jlittle988]

I have an Orbi RBR40 router, and I have it set up for OpenVPN access. I am able to connect my desktop (Win10) to the VPN with no problem, and it is assigned an IP on the .1 subnet, the same as the rest of my network. When I connect from my Galaxy S10, it gets an IP on the .2 subnet, and is not able to talk to devices on my network. Is there some way to give it an IP on my main subnet?

[ekhalil]

VPN clients will always get IP addresses different from the LAN subnet but all subnets should be possible to reach each other as there is no rule blocking this.

In my iPhone I get the IP address 192.168.2.1 when connected as VPN client but I can reach all my LAN network devices.

[jlittle988]

Ok it seems only certain things don't work. I am able to access webpages hosted by different devices on my network over the VPN, but I can't connect to a Samba share with a client on my phone. Is there any way to make this work? Could I add a second interface to the server hosting the Samba share and assign it an IP on the .2 subnet to allow my phone to see it?

[ekhalil]

---

@jlittle988 wrote:

.......... but I can't connect to a Samba share with a client on my phone. Is there any way to make this work? ..................

---

Please check the following link: https://openvpn.net/community-resources/connecting-to-a-samba-share-over-openvpn/

I hope that this will help.

[schumaku]

---

@ekhalil wrote:

VPN clients will always get IP addresses different from the LAN subnet ...

---

That's not the full truth I'm afraid. It depends if the client is using the TUN or the TAP mode. The TAP - establishing a direct bridge connection or extension to the LAN (original subnet) so th client wold receive an IP from the remote LAN - isn't available on mobile OpenVPN clients because iOS,iPadOS, or Android (except if rooted - depreciated) does not allow to install the required Kernel module and driver. For the TUN mode, Netgear has hardcoded (!!!) the 192.168.2.0/24 subnet on the TAP interface, so the VPN tunnel does run on a routed intermediate subnet.