10:16:08 admd Authentication of Firewall user ] from EXTERNAL_IP_2 was accepted id="1100-0004" 10:14:42 sessiond SSL VPN user from EXTERNAL_IP_1 logged in assigned virtual IP is INTERNAL_IP_1 id="3E00-0002" 10:14:42 admd Authentication of Firewall user ] from EXTERNAL_IP_1 was accepted id="1100-0004" 10:14:42 admd Authentication of Firewall user ] from EXTERNAL_IP_1 was accepted id="1100-0004"
For some reason the authentication of one of my new colleagues is performed twice: When authenticating via the VPN the Event-logs in the traffic monitor are a bit confusing. We are using case sensitive usernames (and the are entered correct). If I allow the specific IP that testaccount is connected via (say 192.168.100.10) in the firewall policy Allow SSLVPN-Users the session works as expected.Īnybody got some ideas on what to do to get further with - At the moment we do not have any log server set up, can I retrieve the logs from the unit itself? There is a to-do for setting up a - We are using the Firebox-DB for authenticating, so I can't use the System Status -> Server Connection functionality as we're not using any LDAP/AD.
All traffic from testaccount is blocked by the "Unhandled External Packet" policy.Only henriks connection shows up under "authentication list" (WebUI -> System Status -> Authentication List).Both henriks and testaccounts credentials can be used to connect to the VPN, and both are accepted and receives an internal IP.A new user is created, testaccount, also member of the group.An old user (say henrik) is member of this group.When checking the documentation online this scenario is described and referred to as issues with users not being members in the SSLVPN group or this group/policy for the group not being correctly configured. When creating new users in our M470 they are able to connect to the VPN, but they are not "authenticated", rather they get blocked by the firewall (Unhandled External Packet).
0 kommentar(er)
