Goodmorning,
First of all I'm not the beįgest expert here, but i have some knowledge...
I have been searching this forum for a solution, found some information, but still can not make it work the way i need...
And here's the situation:
Multiple IOT devices (via routers with SE Bridge installed) will be connected to SE VPN server and will connect to different virtual HUBS. Multiple clients will connect to those hubs for management of devices. I need to find a way to make clients only to be able to connect to their part - hubs, bridges, etc which is done and works, but forbid connection to the internet through that connection, because server is in the office, ant then there will be a lot of internet traffic, ad offices IP will be used for their connections. Doing anything at client side is not an option. Clients might connect from different networks randomly - home, office, coffee shop, gas station, mobile phone...
As i mentioned, i tried different stuff found here, in this forum...
I am using SE virtual DHCP server.
First of all tried to empty default gateway in Secure NAT configuration - client can connect to VPN, gets IP address from SE DHCP, but can't connect to VPN LAN devices.
Then i tried to use Access lists.
First made a rule that allows access to real network.
Then discard everything else:
After the last rule i was unable to get IP from SE DHCP server. VPN Client shows Connected, nothing is accessible (LAN, internet)...
Then i made this rule, just for test: to allow traffic to SE NAT DHCP - That didn't help...
Once again - VPN access to LAN only
-
- Posts: 31
- Joined: Fri Jul 05, 2024 8:37 pm
Once again - VPN access to LAN only
You do not have the required permissions to view the files attached to this post.
-
- Posts: 1545
- Joined: Sun Feb 14, 2021 10:31 am
Re: Once again - VPN access to LAN only
Remove those access rules and uncheck "Use Virtual NAT Function".mendoza_lt wrote: ↑Tue Sep 03, 2024 7:12 amI need to find a way to make clients only to be able to connect to their part - hubs, bridges, etc which is done and works, but forbid connection to the internet through that connection...
-
- Posts: 31
- Joined: Fri Jul 05, 2024 8:37 pm
Re: Once again - VPN access to LAN only
I did, now when i connect to SE VPN server i get IP from SE DHCP, client side (checked at whatismyip.com) shows client IP, but i can't access remote (server side) LAN. Tried with or without local bridge.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 1545
- Joined: Sun Feb 14, 2021 10:31 am
Re: Once again - VPN access to LAN only
I see. In SecureNAT:
- re-enable "Use Virtual NAT Function"
- ensure the default gateway is empty
- in "Edit the static routing table to push" enter the LAN's subnet
- re-enable "Use Virtual NAT Function"
- ensure the default gateway is empty
- in "Edit the static routing table to push" enter the LAN's subnet
-
- Posts: 31
- Joined: Fri Jul 05, 2024 8:37 pm
Re: Once again - VPN access to LAN only
I did, same - can't access server side LAN. The only thing that works is to put back gateway... but then i am back where i came from...
You do not have the required permissions to view the files attached to this post.
-
- Posts: 1545
- Joined: Sun Feb 14, 2021 10:31 am
Re: Once again - VPN access to LAN only
Incorrect, replace 192.168.88.1 with 192.168.39.1
-
- Posts: 31
- Joined: Fri Jul 05, 2024 8:37 pm
Re: Once again - VPN access to LAN only
Awesome :) works as it should. Thank you very much for help :)