pfSense keeps disconnecting/reconnecting in UniFi Controller
-
Yeah it has to be the same MAC address appearing in different segments.
-
@stephenw10 yeah - what a shit show from unifi.. Its only been like 15 minutes, but since I changed to only send 1 vlan (untagged) down that link no more alerts.
-
Isn't that switch port-based VLANs only?
-
@mcury - sort of.. The uplink can only be what they call the "all" profile.. So you can not limit on the switch what vlans are allowed. But I can for sure limit what vlans can be sent to the switch. And there is a native vlan (untagged) and then tagged vlans..
You can then only put ports on the mini in 1 specific vlan, or the "all" profile..
I have no devices actually connected to the thing - its just connected to the network via the 1 port set as "all" profile.
You can see from the profile that some of the vlans are tagged, shows their ID.. And there is the native untagged network.
Yup when I only sent it 1 vlan worth of traffic.. no disconnects for over an hour, as soon I allowed more vlans down the connection from my upstream cisco - it starts showing disconnecting back and forth between the untagged wlan and the lan which is tagged with ID 9.. Stupid log spam to what it amounts to it seems like.. I will have to put a client on the thing and see if it shows it disconnecting when its only in 1 vlan that is assigned to the port its connected to on the mini.
So far from the few hours play time - I couldn't recommend their switches to anyone.. Even if it works the log spam is horrible. And you can not get any sort of reliable data on uptime, etc. since that resets every time it shows that connection switching.. WTF??
-
@johnpoz Since I have a unifi controller up and running, I thought about buying one of these switches, but not sure anymore..
So, basically you have the access ports (you can have up to 4 VLANs), and one uplink with the "all" profile.. And that is it, to expand the network only unmannaged switches are allowed..
-
@mcury Yeah I wouldn't buy it from my experience so far.. So I am almost sure yesterday I saw that I could apply a port in the switch to a vlan only network I created.. But I just updated controller and that seems to be gone. There is no way it seems to put a port any any specific vlan - wtf??
Let me roll back to .51 of the controller.. I always take a snapshot before update..
-
@johnpoz Strange, this was not mentioned in the improvements section of the .52 release
-
So it was me playing with the switch profiles.. You have to create the networks as vlan only, and can not create them in the profiles section..
Updating back to .52 now... Guess if you create the profile in the switch ports its "custom" and the mini can not use them... So create a vlan only network and it auto creates the profile - which the mini can use.. Once update to .52 is done will clean everything up... And will see if that will clean up the disconnects?? I doubt it since its using the all profile..
edit: ok all fixed, just had to recreate the networks vlan only, and let it auto create the switchport vlans.. Now I can assign a port to one of those vlans.
-
I'm running "Profile - ALL" on my uplinks from pfSense.
Mybe this is wrong way, but it works. Any suggestions?
-
No that works - all profile is their trunk mode.. But on the mini you can not limit what vlans are in this uplink.
So that would have be done on the other end..
I guess on their other switches you can use custom profiles so you could use a profile for your uplink that only allows say vlans 3,5 and 7, vs all of them..
-
@johnpoz So, if I was to connect the mini into the SG-3100 LAN ports, I would have to configure the sg-3100 vlans to go to the mini uplink as tagged vlans, then configure the remaining ports in the mini as access ports for each desired vlan..
The only thing here I can see as a limitation is the fact that only one uplink is possible, and the "all" profile must be used for it, but as you said, we can always limit the vlans in the other side.dead on arrival, nowhere to be found.
-
@johnpoz
Yeah, i do have couple of switches here. And i can choose different profiles.This one is from another 8 ports unifi switch.
-
Yeah you can work around the limitation - I am not so much concerned about the all profile.. What ticks me off is the log spam of it saying xyz was disconnected when clearly it wasn't - the device just saw the same mac on a different network... Which with vlans happens all the time..
edit: The whole system becomes garbage if your going to fill up the log with mis information.. The device clearly was not disconnected.. How can I trust really any info provided if you can't get something as simple as connected or not connected correct?
-
-
@johnpoz Have you checked the system logs on your Netgate? You're having the same problem as me. Those log messages go away when you find the problem.
@CiscoX On my end, the Netgate was blocking the VLAN's from reaching Unifi and it was reporting this log output. It was blocking it for a split second but that was knocking my sensitive devices like Echo's and anything that doesn't keep a cache.
-
@dragonfire1119
Hi, I have seen those logs before, but never think about them until now :)
But everything seems to work normally, no complains from the kids ether. -
there is nothing wrong with my netgate, there is nothing wrong with my switch or my internet... The log entries are clearly spam..
Since both of those networks run over the same uplink wire... Not freaking possible for 1 to be disconnected without the other.. Not possible to be disconnected from the switch, and not be disconnected for pfsense, etc..
If the uplink was bad, then my new client just connected to the switch would also be showing disconnects.. Which is not, and its connected to work vpn, etc.
Its nothing more than log spam because of the way unifi tries to determine what is connected and what is not.. If you look on the net there are lots of complaints about it - but nothing in the way of any sort of solution..
Solution is don't buy unifi switch would be my solution ;) Which glad I never, and only spent $40 on what amounts to play toy.. If its going to spam my logs with disconnections when I try and run any vlans on it - its useless. I don't even think there is a way to just not log the event?
-
@johnpoz
hehe, my house is full of unifi devices
-
@johnpoz Well, my unifi products are working great now. I wasn't saying anything was wrong with the Netgate just was saying it might be blocking the VLANs for some reason. I know now that those messages are not spam because you helped me with that problem. Looking on Google I noticed there weren't any solutions that's why I replied here. I know you don't use NTOPNG but you're very experienced so you might have a package that's doing something else or the same thing?
@CiscoX Well guess that's all that matters :). Logs bother me because I'm a programmer and in programming when something has logs like this there's a problem and it will bother me until I fix it. I constantly monitor servers though for any anomalies that could be showing me a problem.
Servers and software are programmed to show you where the error is normally or cry out for help In logs and say something is wrong at least this is my experience :).
-
Don't get me wrong I Love the APs - I have 3 of them.. And have really had no issues with them - they work, they do what I say per the controller. I get great speeds.. They are easy to configure.
Maybe they should stick to AP vs switches ;) I never see my AP say the switch disconnected. They don't even show there is a switch upstream of them - which is fine with me..
