The page of user setting is very closely related to the IP filter settings. While the administrators are setting these two pages, they should notice that login authorities are not only based on the login names but also the range of IP addresses. Administrators could reject login users according to both login names and IP addresses. We setup several examples to explain the logical relations between login names and the IP policy. The users login in the name of ”admin” have the most power. System will always accept no matter how IP filter setting was set.
(User page) Login name 1= 12345, Password=12345, Access Authority=whatever (IP filter page) Default Policy=Allow, login name1 comes from 192.168.0.A to B=Allow That is, when the remote users login in the name of 12345 and come from the IP addresses 192.168.0.A to 192.168.0.B, login will be successful. If these users did not come from the IP addresses A to B, login access will be rejected.
(User page) Login name 1= 12345, Password=12345, Access Authority=whatever (IP filter page) Default Policy=Allow, login name1 comes from 192.168.0.A to B=Deny That is, when the remote users login in the name of 12345 and come from the IP addresses 192.168.0.A to 192.168.0.B, login will be denied. If these users did not come from the IP addresses A to B, login access will be successful.
(User page) Login name 1= 12345, Password=12345, Access Authority=whatever (IP filter page) Default Policy=Deny, login name1 comes from 192.168.0.A to B=Allow That is, when the remote users login in the name of 12345 and come from the IP addresses 192.168.0.A to 192.168.0.B, login will be successful. If these users did not come from the IP addresses A to B, login access will be rejected.
(User page) Login name 1= 12345, Password=12345, Access Authority=whatever (IP filter page) Default Policy=Allow, login name1 comes from 192.168.0.A to B=Allow That is, login of all the login names will be rejected except the login name “admin”.
32/80