I'll try and keep this concise because I could write a pretty detailed essay on this topic after spending the last hour+ dicking around with it. If you have a Hue lighting bridge installed, you may find this useful for the health of your network.
My Procurve switch has been throwing up non-critical errors at me for a while now, and because I'm bored I decided to finally see what it was complaining about.
I was getting a wack ton of these errors emailed to me daily, for a while now.
Now, because I'm lazy I didn't actually have a label on anything in my rack as for as what port is assigned to what device. (Tsk tsk) So, I SSH'd to my switch [http://www.chiark.gr.../download.html] , logged in, and ran the command 'show mac' to get the mac tables of all devices physically connected to the switch.
I've cropped and blurred accordingly.
With this information, we can head over to http://aruljohn.com/mac.pl and input the first characters of the MAC address to find out what exactly, this device is. Because I still have no idea at this point. To my surprise it's my Phillips Hue Bridge. Dafuq?
I swapped the cat 6 patch because I had some on hand, it's what HP suggested for troubleshooting 101 and was easy. When that was done, I watched the errors continue to roll on in. So obviously, that wasn't the issue. So I think to myself, It's probably constantly sending because I use geofencing features on my Hue, to turn on the lights <after it gets dark> and <when I'm getting close to home> and a ton of other IFTTT things. So it's not all that surprising to see a pretty constant data transmission.
So I log into my procurve GUI through IE, (Java, Java everywhere!) and turn on port monitoring for port 23, to see what exactly it's doing. Almost immediately, I'm greeted to a steady flow of these;
Again, cropped for security reasons.
Okay, that's totally not what it was complaining about before. I double check the port config and verify it's configured correctly. Which it was.
Digging a little deeper, I decided to see how many errors it was throwing up, as well as how much data it was actually sending and receiving.
3 errors?! That's what it was constantly complaining about?! I literally received about 400 auto email alerts about this particular port since I've set up my network in my new home. Also, perhaps more shocking. 254 Megabytes of traffic a month, for a smart light bridge? Get you shit together Phillips!
I ended up moving the Hue bridge to it's own VLAN and so far, it's been behaving without errors and still whoring all the bandwidth.
That's where I'll end it. If anyone is curious how to set up a VLAN with proper VLAN tagging for their Hue to interface with a Sonicwall appliance I could whip something up, but that's probably out of the scope of this...tutorial? Rant? WTF is Phillips doing essay? I'm not sure how many others run "proper" home networks with a NAS, DNS server, VPN endpoints, firewall appliances, VM's..etc etc or it I'd be wasting a great deal of time in preparing it.
So yeah, that's pretty much it. TL;DR, Hue uses a wack ton of data for what it is, and lives happiest on its own VLAN.
NextGenMember Since 04 Jan 2011
Offline Last Active Today, 03:19 AM
- Group Member
- Active Posts 12,204
- Profile Views 31,696
- Member Title KNOWhope
- Age 27 years old
- Birthday June 7, 1988
- Website URL http://steamcommunity.com/id/ngdot24