User assumptions
To add a location assumption
Notes:
Consider this location list:
192.168.0.1 john
192.168.0.3 alf
192.168.*.* fred
192.168.0.* cilla
The problem here is that cilla will never be reached because line 3 - fred,
covers anything that is not 192.168.0.1 or 192.168.0.3. If cilla was promoted
like this:
192.168.0.1 john
192.168.0.3 alf
192.168.0.* cilla
192.168.*.* fred
Then cilla would be assumed for any connection from the 192.168.0 range of IPs
except 192.168.0.1 and 192.168.0.3, and if say 192.168.1.12 connected, it
would be associated with fred.
There is an implicit assumption of *.*.*.*
Only DHCP clients can use name based assumptions.
When you set up IP assumptions (locations) you can use the wild card * to mean
IP Assumptions are read from the top down. They will associate with the first
match.
Guest, as anyone who has not logged in, and has no assumption, is in fact a
Guest. This is logically at the bottom of the list, as it will associate with
any IP.
Assumptions can save users from logging in. If certain machines are only ever
used by one person, then give them an assumption, and they won