DalekSec Posted December 11, 2018 Posted December 11, 2018 Hi All, We have this strange problem at the moment on our UniFi test bed, when connecting to the wireless it goes through and picks up an IP address on the correct vlan for the user logging in, but a lot of the time in the controller the IP address is different to what is on the machine. To add to confusion i added another machine and it picked up the IP address that it said the other device had wrongly, but the new machine had it correctly. According to the controller both devices had the same IP address. E.g. Macbook currently ip 10.13.3.32, on the controller it reads 10.13.1.98 Windows device connects, it's ip is 10.13.1.98 and is the same in the controller.... This is on a WPA Enterprise network with an assigned RADIUS profile, let me know if you need any other info. Thanks Dalek
jthompson Posted December 11, 2018 Posted December 11, 2018 Maybe see if ipconfig /flushdns on the server running UniFi Controller makes a difference? Not encountered/noticed that problem here, but that's probably what I'd try first of all. Since UniFi Controller isn't managing those IP address leases, it could just be referring to DNS to populate that info.
adamsund Posted December 11, 2018 Posted December 11, 2018 We had something similar but it was a DNS issue on the DC that was to blame, nothing to do with Unifi. That’s where I would start. Check scavenging etc
DalekSec Posted December 12, 2018 Author Posted December 12, 2018 Maybe see if ipconfig /flushdns on the server running UniFi Controller makes a difference? Not encountered/noticed that problem here, but that's probably what I'd try first of all. Since UniFi Controller isn't managing those IP address leases, it could just be referring to DNS to populate that info. I can't see it being the DNS on the server, as we've rebuilt the unifi testbed to another VM and only recently turned it on. I'll give it a go none the less! Which APs do you have? AC-Pros We had something similar but it was a DNS issue on the DC that was to blame, nothing to do with Unifi. That’s where I would start. Check scavenging etc Do you know what the issue on the DNS was? So i have somewhere to start digging
adamsund Posted December 12, 2018 Posted December 12, 2018 I can't see it being the DNS on the server, as we've rebuilt the unifi testbed to another VM and only recently turned it on. I'll give it a go none the less! AC-Pros Do you know what the issue on the DNS was? So i have somewhere to start digging For us it was one of the technicians mistaking DHCP and DNS and deleting almost all of our DNS records. While the entries were repopulating I noticed every strange entries in Unifi with wrong hostnames and duplicated IPs. It sorted itself out once it had fully repopulated.
DalekSec Posted December 12, 2018 Author Posted December 12, 2018 For us it was one of the technicians mistaking DHCP and DNS and deleting almost all of our DNS records. While the entries were repopulating I noticed every strange entries in Unifi with wrong hostnames and duplicated IPs. It sorted itself out once it had fully repopulated. Oooerrrr Glad you got it sorted! Fixed!!! We think, everything seems to be working as it should now. It was DNS, our student wifi network was missing the Reverse Lookup Zone for the network. Unsure why, guessing Ruckus doesn't require it! Inputted one and now it's seem to be ok. Thanks for all your help
DalekSec Posted December 12, 2018 Author Posted December 12, 2018 REVERSE REVERSE! Nope it's stopped working again, have 10 iPads connected all coming up as same IP address....
DalekSec Posted December 12, 2018 Author Posted December 12, 2018 More info, we've noticed when a new wifi client joins the IP address of that client is then populated across all already connected clients in the controller. So all clients are showing as the same as the most recently connected device.What makes this weirder, is this connected device is currently connected to our existing Ruckus network, and is on the other side of site so is not connecting to the Unifi testbed....
Primus Posted December 19, 2018 Posted December 19, 2018 Honestly this has to be related to your environment - I've got quite a few Unifi installations and I've never seen this or read about anyone else having this problem on their support forums.
DalekSec Posted December 19, 2018 Author Posted December 19, 2018 Honestly this has to be related to your environment - I've got quite a few Unifi installations and I've never seen this or read about anyone else having this problem on their support forums. I totally agree, but my manager thinks its UniFi and i can't seem to turn his head! I posted it on the UniFi forums and had no replies
Primus Posted December 19, 2018 Posted December 19, 2018 What is providing the DNS and DHCP for the network you're running the Unifi setup on? Does this network have any other DNS or DHCP running on it? Is it completely isolated as a test environment from your main environment?
DalekSec Posted December 19, 2018 Author Posted December 19, 2018 (edited) What is providing the DNS and DHCP for the network you're running the Unifi setup on? Does this network have any other DNS or DHCP running on it? Is it completely isolated as a test environment from your main environment? We have 3 DHCP servers, 2 of which are on the same network as UniFi and 2 DNS Servers, both on the same as UniFi. UniFi is in our main environment. Edited December 19, 2018 by DalekSec
Primus Posted December 19, 2018 Posted December 19, 2018 How is your DHCP configured? Eg. split scopes, failover? Is your DNS correctly replicating? Could you possibly (temporarily) run with just 1 DHCP and 1 DNS server in order to try to diagnose the issue further?
DalekSec Posted December 19, 2018 Author Posted December 19, 2018 (edited) How is your DHCP configured? Eg. split scopes, failover? Is your DNS correctly replicating? Could you possibly (temporarily) run with just 1 DHCP and 1 DNS server in order to try to diagnose the issue further? Both DNS and DHCP are set as mirrors so both have same settings (bar obvious stuff like its IP) with the clients spread across both so i'm guessing its Failover with split scope?. I just noticed in one of our DHCP servers it's missing the server option policy for the router while the other one has it a policy setup. Could this be a part of the problem? We could try running with 1 of each but i'd have to persuade my manager to give it a go! Edited December 19, 2018 by DalekSec
Primus Posted December 19, 2018 Posted December 19, 2018 You'd need to look at this further - failover replaces the need to use split scopes. I doubt that option policy would make a difference however the DHCP servers should all be identical - you're probably going to need to do a bit of digging in DHCP here. You could do some testing with just 1 DNS and 1 DHCP server over the holiday period - shouldn't be any major drama to simply shut the other DNS/DHCP servers down unless you've got other stuff running on them?
DalekSec Posted December 19, 2018 Author Posted December 19, 2018 You'd need to look at this further - failover replaces the need to use split scopes. I doubt that option policy would make a difference however the DHCP servers should all be identical - you're probably going to need to do a bit of digging in DHCP here. You could do some testing with just 1 DNS and 1 DHCP server over the holiday period - shouldn't be any major drama to simply shut the other DNS/DHCP servers down unless you've got other stuff running on them? Spoke to my manager about it, going to turn off the one i think might be dodgy tomorrow and see how it goes!
Primus Posted December 19, 2018 Posted December 19, 2018 Ok - post back and update the thread on how you get on.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now