a User with one device get many IP addresses, why?
-
Since you hid the MAC (?) we cannot lookup what type of device it might be. Look up the MAC to see something about the device or if you know what kind of device is it?
-
@viragomann Thanks for answering,
I recently installed pfSense 2.7.1 from scratch on this machine, it was not like now.
As you see in the attached table all of the MAC addresses are same. I know about this example. We have one guest in our hotel with this ID number and he has just one device. I researched about it. -
@AndyRH
This is a random MAC address that is generated by an Android phone. Like all smartphones. -
@vahidmoghadam said in a User with one device get many IP addresses, why?:
pfSense 2.7.1
Where did you get 2.7.1 ?
The official download page shows 2.7.2 for weeks now ....
Why would you prefer to settle for an older version ?About the "same MAC, but different IP" : go to the Status > System Logs > DHCP page.
Can you see that the same device known with MAC a2:1x:xx:xx:xx:37:fa asked over and over for an IP, and the DHCP server answers every time with another IP ?There are no other DHCP servers in the portal network, right ?
Your network settings ?
I see you use 10.20.12. and 10.20.13, so close to 254*254 devices ( really ?? ) -
@Gertjan
When I wanted to install it, 2.7.1 was available.
I'm using 10.20.12.1/23 so I have 510 address capacity in this pool.
I'm using this network for the Hotel's guest. -
Hello again...
I changed network settings and rolled back to using ISC DHCP instead of KEA DHCP and my problem was solved.
I no longer conflict with IPs and MAC addresses in the Captive Portal. Every user after connecting and using the network remains connected for several days and an IP is assigned to him/her in the system.
Does anyone have an idea how to apply some settings to use the KEA DHCP without having this problem? thanks
-
@viragomann @AndyRH @Gertjan
Does anyone have any idea? Please read my last reply -
@vahidmoghadam said in a User with one device get many IP addresses, why?:
apply some settings to use the KEA DHCP without having this problem?
I have not played with kea much as of yet, its not really ready for prime time IMHO.. Unless your a very basic user of dhcp and just want stuff to get an IP.. Sure it will hand out an IP, etc. so from basic point of view - hey it works as a dhcp server. But many features that is more than capable of doing have not yet been implemented in pfsense.
isc dhcp is not going away anytime soon. Since there are many features that are not yet working in pfsense.. I would suggest you just continue to use isc dhcp at this time.. Maybe next release they will have more features implemented that allow you do do whatever the specifics are you want to do, etc.
I use options, I use reservations and registration of these reservations, etc. So while I switched too it and hey my box got an IP from dhcp.. It is currently missing feature I want to use, so I just moved back to isc.. Again its not being removed any time soon that is for sure.. I doubt they will have full feature parity with isc even by the next release of pfsense - but maybe.. I think going forward they will have features in kea that are not even possible with isc, etc.
And isc has stated that they will really not be doing any future development for isc, so yeah at some point need to move away from it.. But personally that day is not here yet.
I also noticed the logging of kea dhcp is way different than with isc dhcp, and looks its including debug info, etc. I am hoping they address that in future release. Because looking over the kea docs it has a lot of ways to filter/adjust what is logged, and what is not, etc.
-
@johnpoz
Thanks for replying...
So, according to your reply, This is a bug and not my fault in the settings.
My concern arose when I saw this text in the pfSense network settings:ISC DHCP has reached end-of-life and will be removed from a future version of pfSense. Kea DHCP is the newer, modern DHCP distribution from ISC that includes the most-requested features.As a result, I should not update the version of my pfSense until I am sure of fixing this bug.
-
@vahidmoghadam said in a User with one device get many IP addresses, why?:
This is a bug
No I wouldn't say that - its related to feature(s) that has yet to be enabled in the "PREVIEW" version of their kea implementation.
I am not a huge fan of the wording they used to notify users of the future removal of isc dhcp.. But if users would of spent some time reading over the release notes before blindly clicking over to using the new kea which they did clearly label as "preview" in the release notes.. And went over what features are not yet enabled, etc.
Better wording might of headed off some of the posts we are seeing with users trying to use kea that is not fully implemented yet with all its features and bells and whistles.
And also a "preview" version is prob more likely to have some kinks or bugs to work out..
Also with anything "preview" even if didn't read the release notes, when switching to it - would be a great idea to actually validate it is working for all the things you need before sticking with it.
I read the release notes, and knew right away it wasn't going to be viable for my use at this time. But I did switch to it, and yup client gets an IP from dhcp.. So it is functional as a dhcp server.. But again per the release notes its missing things in its current implementation that I am currently using in my setup. So for now I stick with ics dhcp..
Maybe with the note they popped up could of included a warning that all features are not fully mature or enabled - please validate it it will work for you before switch - link to release notes, etc.
Its hard to say what the best course of action is - warning the users of removal of isc dhcp at some future time is a good thing.. But maybe it might of been been better to just hold off on the warning, and put in the release notes (which seem to go unread by many) that there is a preview version of kea available if you want to play with it.. etc. It is currently missing xyz features, etc. So be warned.
