2 bugs in 2.0.1-RELEASE
-
my system version
2.0.1-RELEASE (i386)
built on Mon Dec 12 17:53:52 EST 2011
FreeBSD 8.1-RELEASE-p6
i am using captive portal + DHCP server.
in DHCP server .. it dose not check if the MAC address was previously entered, as i can assign 1 ip Address for 2 MACs .. i reported about this in m0n0wall and they fixed it monthes ago ..
in User manager , when i choose a date to make a username expires, it dose not.
i supposed it should get disabled. but it does not happen.best regards,
Mohammed Ismail . -
I thin kthese are fixed on 2.0.x and 2.1 already
-
If I recall correctly, being able to assign one IP for two MACs was done on purpose.
For example, if you have a laptop with a wired NIC and wireless NIC, people wanted to pull the same IP from the same laptop no matter how it was connected. Obviously not everyone will need that, but if we prevent it, then it isn't possible for anyone to use it.
-
got ya.
thanks allot. -
in User manager , when i choose a date to make a username expires, it dose not.
i supposed it should get disabled. but it does not happen.best regards,
Mohammed Ismail .In latest version the automatic disable dont work.
-
If I recall correctly, being able to assign one IP for two MACs was done on purpose.
For example, if you have a laptop with a wired NIC and wireless NIC, people wanted to pull the same IP from the same laptop no matter how it was connected.
Yes that was done on purpose for that exact reason, same was done in m0n0wall, they broke that feature which a number of users use if they "fixed" that non-issue.
I've never seen account expiration not work, I've been locked out of customer systems on several occasions when the account expires and never not locked out when expired.
-
@cmb:
If I recall correctly, being able to assign one IP for two MACs was done on purpose.
For example, if you have a laptop with a wired NIC and wireless NIC, people wanted to pull the same IP from the same laptop no matter how it was connected.
Yes that was done on purpose for that exact reason, same was done in m0n0wall, they broke that feature which a number of users use if they "fixed" that non-issue.
I've never seen account expiration not work, I've been locked out of customer systems on several occasions when the account expires and never not locked out when expired.
Sorry i didnt write the post very well. I meant in user manager there are a choice disabled and in overview a column disabled.
Shouldnt the disabled set it self disabled when time is out for user where endtime is set? -
Expired is a different state than disabled. Neither state can be used. An expired account isn't set to disabled by design and isn't a bug, whether expired accounts should also be set to disabled is another question. I'm not sure. There isn't a problem with the way things are currently done, and some things log differently for expired vs. disabled which some people would consider a feature.
-
@cmb:
Expired is a different state than disabled. Neither state can be used. An expired account isn't set to disabled by design and isn't a bug, whether expired accounts should also be set to disabled is another question. I'm not sure. There isn't a problem with the way things are currently done, and some things log differently for expired vs. disabled which some people would consider a feature.
Okey, understand now. Thanks.
