Because we DO NOT set the ether0 interface as the highest priority
(which I've also RFE'd).
Say a PM3 with a ether0 address of 192.168.10.1/24 has a assigned pool
from 192.168.10.32 with 48 addresses...
If a user with these parameters should connect:
Framed-Address = 255.255.255.254, (dynamic pool)
Framed-Netmask = 255.255.255.0 (24 bit mask)
say he is assigned .36
With the 'user-netmask' on, the user would connect with this route:
192.168.10.0 24 192.168.10.36 local NL 1 ptpX
This route would squash the local ether0 route and redirect all packets
that were destined to the ether0 segment out to the user on ptpX.
UGLY!
So, before anyone turns 'user-netmask' on, please be sure NONE of
your user profiles have netmasks with the same length as the ether0
IF the address they use is in the same subnet as the ether0.
Tom
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.