-
unknown mac address sharing IP address of unraid server
bump? I'm sure it's coming from unraid, most likely a docker container, I'm just not sure which configuration i've messed up...
-
unknown mac address sharing IP address of unraid server
Hi All, recently my Unifi controller has been reporting a duplicate client IP address in it's dhcp table and it's coming from a mac address of a device I don't recognise, know matches any known manufacturer when I google the first digits. I suspect it's coming from unraid only on account of according to the controller it's plugged into the same switch port as the server is... I haven't installed anything new docker/plugin/vm wise since it start appearing, so I'm confused where it came from and what it's doing. According to my Unifi controller, it's not generating any traffic either, but I don't like it. Has anyone had this happen, and any way to identify what it could be? Cheers, Matt
-
adopting a physical USG hardware firewall/router into the software docker unifi controller.
Probably a unique circumstance, but i'm hoping someone has configured a similar setup and encountered this situation and might have a work around. Originally, I setup a hosted controller on my windows server as a way to manage the unifi ap's at my parents house, now expanded to a USG and Switch and new LRs also. Fast forward today, I now also have a USG, multiple switches and APs at my own house... I migrated the unifi controller onto an unraid docker app and have two "sites" set-up one for my parents, one for my house. Annoyingly whenever I reboot my server, and/or the controller app restarts, it seems to wig out my USG only, other AP's/Switches etc will adopt when the controller is back online, but the USG goes into a adoption loop. SSH to the USG and run an "info" command, the controller FQDN e.g. http://mycontroller . net:8080/inform on the USG it at an Unknown [11] status... this address populated by the controller name/ip override setting (which works for all internal/external devices across two sites) so I adopt it using the internal IP address of the server, this brings the USG back online - but only lasts as long as everything stays online. how do you guys deal with USGs and hosted controllers on the same network? do you inform the usg to the internal IP address after every reboot, or does the FQDN hostname work fine Cheers, Matt
mattson
Members
-
Joined
-
Last visited