It couldn't access a share.on that client only see some of the ports that were running services. My VPN client with a 10. address is able to ping and browse network shares on a test computer 10.0.20.x plugged in by ethernet on VLAN20, result.Īs a test I wanted to see if I could port scan anything else from my VPN client so tried a port scan of a device plugged into the default_vlan 10.0.10.0 and it returned an 'alive' and a list of active ports on the device. I am perhaps going the wrong way about this and it should be with firewall rules or something, anyway. What I wanted to do was have the VPN clients access only VLAN20 which is the VLAN on my network that I would want to put some servers in which I want remote clients to access by VPN.
I have setup SSL-VPN access as a test following a couple of recipes from the Fortigate Cookbooks and searching some forums. I got help with this issue earlier in the week. When a wired client is plugged into one of the untagged ports they can only see (ping) other clients in the same VLAN.
I have VLANs working across a couple of borrowed HPE Aruba 2530 switches. I have setup a borrowed Fortigate 600D which isn't licensed yet so still on FortiOS 5.4.5 Those of you who like this forum may have seen from my other recent post I am new to firewalls and VLANs.
0 kommentar(er)
