3 ms·
This assumes your paranoid network admins don't disable CDP/LLDP one day because of nebulous "security reasons" and sabotage your scripts, but this is the wrong
by gruturo 2y ago
This assumes your paranoid network admins don't disable CDP/LLDP one day because of nebulous "security reasons" and sabotage your scripts, but this is the wrong time and place to rant about that :)
Cool hack!
- 9x39 2y agoI think that's a real risk for anyone not doing their own DIY network and/or able to require the network to offer (or least not block) it. Depending on protocols nobody expects you to be depending on can be risky, particularly with all the pathologies of working with multi-team corp operations... To some degree, beyond a tiny scale, building on CDP/LLDP is probably fighting uphill. From my perspective working with audio/visual (AV) teams and corporate IT, it's maybe safer to do your location and stream management out of band in some kind of overlay (app or network protocol), and just have the network serve you multicast streams that you request. That is, a receiving device is programmed out of band (manually or by some management scripting) to subscribe to a particular IP multicast stream and the network's job is just delivery through IGMP+PIM. This is the rough model most AV technologies seem to be following, even to the point of collapsing receiver/decoder boxes into the TV itself. But, sometimes there's nothing like scratching your own itch, though.
- toomuchtodo 2y agoCDP/LLDP traffic will potentially pop up on a network penetration test as a finding (if your org either performs internal red team assessments or engages an external assessor as part of a compliance regime). Have seen it disabled for this reason.