I’m not sure if this is the right community to ask, but I’m going to try anyway.

So, my Asus Router has smb file server, and vpn server feature, and I have a cctv unit connected to the router as well.

I believe have set up the vpn, port forwarding etc correctly… check the public ip is already the same. But how do I access the smb and my cctv? I’ve tried the local ip (192.168.50.xxx) with no luck, neither is the public ip (which make sense).

Any info or guidance is much appreciated.

4 points

I have a Wireguard VPN to my home network and there it works exactly like you tried it. Connect to VPN, then use the internal IP to connect to the service. Maybe there are settings in the server or client that prevent that. For example, you can set specific IP ranges to not be routed through the VPN (so you can access a local service in Network A even though you are connected to VPN B).

I’m no network expert, but maybe some additional information about your setup can help other user help you better.

permalink
report
reply
6 points

You’ve got it. it’s the setting in the server.

By default, it was on “internet only”

Thank you, and everyone for responding!

permalink
report
parent
reply
2 points

Depends on your specific VPN, but look for a feature or setting called “split tunnel.” It should create a separate non-vpn route for the local network.

Usually client-side setting, but not always if the tunnel is built on connection.

permalink
report
reply
1 point
*

If it’s working correctly, it should be as simple as accessing (internal ip) : (port) at (external ip) : (port).

There are a bunch of things that might be going wrong if it’s not working. Unfortunately, I don’t have the skills to help you diagnose the issue!

permalink
report
reply
-1 points

Tailscale. It’s all you need.

permalink
report
reply
1 point
Deleted by creator
permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.5K

    Posts

  • 75K

    Comments