Who the fuck comes to the idea of printing the local IP address on the Fucking screen?

Yes, I know that it is not remotely accessable (only when there is no port forwarding set for that ip), but think of that this way: Someone manages to get in that network. Without scanning the network, you would have your first victim. You could analyzer the traffic of that victim and find more victims. And so on

A transdev? Is that a developer with some form of lgbtq I am not aware of?

@stevenliemberg no, get those lights off!

If you're in the network finding victims is a matter of seconds

@Kimmax I don't think so. It's not everytime that case.

Doing an IP ping scan would take more than a few minutes if the ip range is /16 for example

If it wasn't on the screen, there'd probably be a sticker on it somewhere. Security by obfuscation never works so who cares if the local address is known.

That's quite common, although I would rather make it a smaller and show it on the lower corners with less contrast.

But I can tell by experience that it's a pain in the ass when the customer calls with a problem on a device and you need forever to find out which device it is and how to access it remotely because the guy
- doesn't know which device it is
- gives you wrong device information
- gives you device information that has nothing to do with what you need (like internal inventory number)
- gives you only location information ("The machine on platform 11")
- gives you only useless information ("The red one with the dent on the right side, besides the blue device")

So it's better to have the important information at hand. I would even put some timestamp there so you also know when it happened if you get a photo of the situation.

And usually those devices are tethered and are not on a public network (like this one, as you see by the 192....), so it's not really a security issue

Its not like thats the most obvious subnet ever.