I've a small lan (192.168.1.0/24 - less than 15 machines), server is 192.168.1.200. I need prevent conflict IP from an user that put his machine's IP same of server, and lan goes down. I can do a subnet (something like 192.168.1.0/25) so I'll have 2 subnet.
What's the best choice?
@MikeyB It's a poorly "questioned" question. Little to no research done, no examples of what has been tried, etc. The issue is a valid one...but the whole "I have X issue...what's the best fix?" is a downvote IMO.
@MattBear I like the 2nd commenter. He's right. The employee agreed to a wage. McD's didn't come to them and demand they work there. They went searching for a job at McD's.
Happy Memory-Forensics-Thursday! I get called in to go malware hunting every once in a while. It's usually after an automatic vulnerability scanner has found something unusual about a particular computer on the network and threw up a red flag. Once a machine is suspected of being infected, someone needs to go in and validate whether what the vulnerabil…
@RyJones I assume you saw the actual bullshit collusion between Heroku and New Relic to hide the fact that Rails dynos on Heroku don't intelligently route requests anymore?
we used it before that happened, and our experience was it was pretty good for steady state usage. Like I said, it was OK, and since we were based on Heroku, it was the best we had
I've a small lan (192.168.1.0/24 - less than 15 machines), server is 192.168.1.200. I need prevent conflict IP from an user that put his machine's IP same of server, and lan goes down. I can do a subnet (something like 192.168.1.0/25) so I'll have 2 subnet.
What's the best choice?
