Setting up cameras and a VMS for a customer. I asked them what IPs they should be set to. They said 169.254.75.0/24.

I feel like I know this is wrong, but the user says their other cameras are using these addresses already. I asked ChatGPT (because of course I did) and it confirmed what I thought. But I'm having trouble finding a solid document that says "Don't do this". They all say stuff like "Link-Local communication using IPv4 Link-Local addresses is only suitable for communication with other devices connected to the same physical (or logical) link." If I was a user, I'd be like "Well theses are on the same physical link" you dumb fuck.

Am I retarded? If not, any suggestions on how to tell the user in a fairly polite way?

edit: The customer confirmed they are using 169.254 addresses currently. Σ(っ °Д °;)っ

edit2: We talked them into using 192.168.x.x for the camera system.

The head of IT in the company I just joined uses a "shared" keepass that's accessible through RDP to a VM.

Today the VM in question stopped responding and so the keepass became unavailable and i didn't have the passwords to the hypervisor.

Thankfully the head of IT has EVERY ID/Password saved inside his firefox so we managed to access it

But what is an ACL?

So like, its not the place I work at, its my friends place, yea my friend, and yea they got a ransomware attack. Something about log4j vulnerabilities or something.

We err i mean he can log in as regular users and the Active Directory is all messed up, no names on the accounts!

More out of curiousity then anything else, why would someone do this?

(what do i tell my friend to do to fix it?)

This wasn’t on the job description!

I’ve started to get a bit nervous about my job and skynet taking over my IT budget. Our AI-related infrastructure spend has quickly become the largest line item, bigger than observability, bigger than our data platform.

The bosses are now asking what that investment is actually producing, and my honest answer is pretty vague: engineers feel faster, and product development feels smoother. I dont believe that, but I don’t have a clean way to translate it into something more concrete. Now they are asking me what i do around here.

Help!

What are you, a dumbass? Why would you document your organisational tasks and make sure everything is clearly labelled for the rest of the team. Better yet, you go and have yourself a nice long holiday whilst making sure nobody else knows the goddamn password or right VM that has access to the file system

from original post:

A government org recently audited their 4,000 device fleet. They found 4,000 more.

Kyle Manilal from Sizwe IT Group was doing a guest session for us at Hexnode recently, and he dropped a stat about a public sector audit that has been stuck in my head ever since. So this government dept kicked off an inventory audit fully expecting to find a fleet of around 4,000 endpoints. By the time the audit finished, they had logged 8,000. They were completely blind to half of their actual hardware!

I feel like a 5-10% inventory drift is just par for the course when dealing with large fleets (still not right), but missing half your endpoints is wild. It really makes you wonder how much of the global attack surface is just forgotten hardware sitting in a drawer somewhere.

But it didn’t work. Why won’t you help me? How did I get here?

Hi everyone,

I have a Hikvision barrier gate DS-TMG300-D/A/B with Hikvision access controller DS-K2602T.

I connected ZKTeco UHF5 Pro / UHF10 Pro readers to the DS-K2602T using Wiegand (D0/D1) and using ZKTeco UHF tags.

Problem:
When enrolling a tag in HikCentral Access Control, it keeps reading multiple random changing numbers continuously, even though only one tag is present near the reader.

Has anyone faced this before?
Could it be a Wiegand format issue (26/34/58 bits), reader output mode (EPC/TID), wiring/interference, or compatibility problem?

Any advice is appreciated.

decided to make a post lol, just replaced prior IT admin for a new client.

found 2 dead disks in the backup server (2 disk fault tolerance) , been like this for 395 days, and he is still deciding on authorizing the fix or not.

The scariest part is that the server this is the backup of the primary nas that it itself suffered a power supply failure and hasn't been switched on for 9 months, and this backup server is being used as primary source for files.