Concern Around Hackers Using DHCP Pool
-
@Mike-Davis said in Unifi switch - tagged traffic issues:
I think were @Dashrender is going is that if you use the Unifi guest service and it's using your production DHCP and DNS servers, and then those devices get hacked, they can take down your production DNS/DHCP servers. If they are on their own VLAN and using their own DHCP/DNS servers, yuo are mitigating some of that threat.
This exactly - and just to clarify a tiny bit - the bits getting hacked are the IOT/guest network devices, not DHCP/DNS.
-
@Dashrender said in Unifi switch - tagged traffic issues:
@Mike-Davis said in Unifi switch - tagged traffic issues:
I think were @Dashrender is going is that if you use the Unifi guest service and it's using your production DHCP and DNS servers, and then those devices get hacked, they can take down your production DNS/DHCP servers. If they are on their own VLAN and using their own DHCP/DNS servers, yuo are mitigating some of that threat.
This exactly - and just to clarify a tiny bit - the bits getting hacked are the IOT/guest network devices, not DHCP/DNS.
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
-
@scottalanmiller said in Unifi switch - tagged traffic issues:
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
Conceptually, it wouldn't take much for a whole bunch of devices to request enough DHCP leases that it would prevent legit devices from obtaining a lease. If your guest wifi DHCP server is separate from your production subnet, you mitigate that threat.
-
@scottalanmiller said in Unifi switch - tagged traffic issues:
@Dashrender said in Unifi switch - tagged traffic issues:
@Mike-Davis said in Unifi switch - tagged traffic issues:
I think were @Dashrender is going is that if you use the Unifi guest service and it's using your production DHCP and DNS servers, and then those devices get hacked, they can take down your production DNS/DHCP servers. If they are on their own VLAN and using their own DHCP/DNS servers, yuo are mitigating some of that threat.
This exactly - and just to clarify a tiny bit - the bits getting hacked are the IOT/guest network devices, not DHCP/DNS.
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
You missed the whole point of the story I posted above. It's not about them being attacked per se, they weren't being attacked in my story above either - but they were being saturated by compromised things on what was believed to be a separated network.
And I'll be happy to keep talking about this, but only if you split the thread. Thanks.
-
@Mike-Davis said in Unifi switch - tagged traffic issues:
@scottalanmiller said in Unifi switch - tagged traffic issues:
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
Conceptually, it wouldn't take much for a whole bunch of devices to request enough DHCP leases that it would prevent legit devices from obtaining a lease. If your guest wifi DHCP server is separate from your production subnet, you mitigate that threat.
That's a pretty sad thing to have to worry about. This can't be a legitimate concern. That would do nothing. A denial of service that no one would even notice.
-
@Dashrender said in Unifi switch - tagged traffic issues:
@scottalanmiller said in Unifi switch - tagged traffic issues:
@Dashrender said in Unifi switch - tagged traffic issues:
@Mike-Davis said in Unifi switch - tagged traffic issues:
I think were @Dashrender is going is that if you use the Unifi guest service and it's using your production DHCP and DNS servers, and then those devices get hacked, they can take down your production DNS/DHCP servers. If they are on their own VLAN and using their own DHCP/DNS servers, yuo are mitigating some of that threat.
This exactly - and just to clarify a tiny bit - the bits getting hacked are the IOT/guest network devices, not DHCP/DNS.
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
You missed the whole point of the story I posted above. It's not about them being attacked per se, they weren't being attacked in my story above either - but they were being saturated by compromised things on what was believed to be a separated network.
And I'll be happy to keep talking about this, but only if you split the thread. Thanks.
And.... so? What I don't get is... who cares? You are going to invest time and effort mitigating a completely non-threatening threat? Why?
-
This is a case of SMBs getting worked up over a real, but totally trivial, concern that just doesn't matter. And spending effort trying to mitigate something totally pointless, when there is so much important stuff that could be done. Is it a threat? Yeah, sure. Does it matter if someone does this to you? no, not in the least. Not in your business, not in a normal business.
Who would do this, it makes no sense.
-
@scottalanmiller said in Unifi switch - tagged traffic issues:
@Mike-Davis said in Unifi switch - tagged traffic issues:
@scottalanmiller said in Unifi switch - tagged traffic issues:
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
Conceptually, it wouldn't take much for a whole bunch of devices to request enough DHCP leases that it would prevent legit devices from obtaining a lease. If your guest wifi DHCP server is separate from your production subnet, you mitigate that threat.
That's a pretty sad thing to have to worry about. This can't be a legitimate concern. That would do nothing. A denial of service that no one would even notice.
Actually, there is real potential for someone to notice in my current setup. I only have around 200 IPs in my current pool. Plus I have about 15 people who come in and out of the office legitimately. So if some hacker comes in and steals all of my open IPs, there won't be any left when any of those traveling folks return. And because the idea is to share this range with the public who is changing near hourly, my leases would need to be very short so I don't run out - of course the short leases are helpful in this situation, but nothing stops someone from sitting on my network for a while continuously hogging IPs just to be a jerk.
-
@Dashrender said in Unifi switch - tagged traffic issues:
@scottalanmiller said in Unifi switch - tagged traffic issues:
@Mike-Davis said in Unifi switch - tagged traffic issues:
@scottalanmiller said in Unifi switch - tagged traffic issues:
You think that your guests in the office are attacking your DNS and DHCP services? And you feel that your DNS and DHCP are that fragile to be a concern to that degree?
Conceptually, it wouldn't take much for a whole bunch of devices to request enough DHCP leases that it would prevent legit devices from obtaining a lease. If your guest wifi DHCP server is separate from your production subnet, you mitigate that threat.
That's a pretty sad thing to have to worry about. This can't be a legitimate concern. That would do nothing. A denial of service that no one would even notice.
Actually, there is real potential for someone to notice in my current setup. I only have around 200 IPs in my current pool. Plus I have about 15 people who come in and out of the office legitimately. So if some hacker comes in and steals all of my open IPs, there won't be any left when any of those traveling folks return. And because the idea is to share this range with the public who is changing near hourly, my leases would need to be very short so I don't run out - of course the short leases are helpful in this situation, but nothing stops someone from sitting on my network for a while continuously hogging IPs just to be a jerk.
This is exactly what I mean. That makes zero sense. And don't call someone taking your IPs a hacker, but that highlights how silly this is. Taking your IPs does effectively nothing to you. It can only be done by someone sitting in your office, it gains them nothing, puts you at no risk and all it does it inconvenience you by needing to release the leases. Whoop-tee-do. Threat level: zero.
-
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@Dashrender said in Unifi switch - tagged traffic issues:
Unifi's guest still uses all the production network services.
What's the concern there?
Licensing could be an issue if you are running Windows DHCP/DNS.
-
@scottalanmiller said:
Threat level: zero.
Incoming Phone Call From Agitated Employee Level: 15
If some device (IOT device, malicious employee, etc) is sitting on his network grabbing every IP address they can, that eventually becomes a Denial of Service attack. While "only" an inconvenience to him and the employee(s) / devices that has to wait on a valid IP address, it still leads to phone calls and agitated users.
If the only cost is my time, I'll choose mitigation every time. Although I agree with your assessment that if you're using a known insecure IOT device on your network, get it off!
-
@brianlittlejohn said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@Dashrender said in Unifi switch - tagged traffic issues:
Unifi's guest still uses all the production network services.
What's the concern there?
Licensing could be an issue if you are running Windows DHCP/DNS.
That was covered in the other thread and makes sense. But doesn't address the "hacking" concern.
-
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@brianlittlejohn said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@Dashrender said in Unifi switch - tagged traffic issues:
Unifi's guest still uses all the production network services.
What's the concern there?
Licensing could be an issue if you are running Windows DHCP/DNS.
That was covered in the other thread and makes sense. But doesn't address the "hacking" concern.
Didn't see the other thread.
-
@dafyre said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said:
Threat level: zero.
Incoming Phone Call From Agitated Employee Level: 15
It's a small office. And no one would EVER do this. The thread level is totally non-existent.
-
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@dafyre said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said:
Threat level: zero.
Incoming Phone Call From Agitated Employee Level: 15
It's a small office. And no one would EVER do this. The thread level is totally non-existent.
So nobody would EVER call if they came into the office and their computer couldn't get on the network?
-
@dafyre said in Concern Around Hackers Using DHCP Pool:
If the only cost is my time, I'll choose mitigation every time. Although I agree with your assessment that if you're using a known insecure IOT device on your network, get it off!
So you'd like to waste your time mitigating a threat that is a million to one would ever happen and has effectively no penalty even if it does happen?
This is the "shoot yourself in the face today to avoid a headache tomorrow" problem. More effort to prevent something than if the thing actually happened - and a thing that has no real world chance of happening.
-
@dafyre said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
@dafyre said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said:
Threat level: zero.
Incoming Phone Call From Agitated Employee Level: 15
It's a small office. And no one would EVER do this. The thread level is totally non-existent.
So nobody would EVER call if they came into the office and their computer couldn't get on the network?
No one would EVER attack a network in this way. It's ridiculous to discuss as an attack vector in a small office.
-
Everyone truly believes that customers of a doctor's office will sit in the office, and knowing that they are doing something that will hurt no one and have no useful effect, take the time to try to tie up IP addresses? I'm lost, what motivation do you think people have for this? Why would someone do this? How many of you have seen people do this in the real world?
-
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
Everyone truly believes that customers of a doctor's office will sit in the office, and knowing that they are doing something that will hurt no one and have no useful effect, take the time to try to tie up IP addresses? I'm lost, what motivation do you think people have for this? Why would someone do this? How many of you have seen people do this in the real world?
Sad, but true. I had someone doing this on a network with 8k IP addresses. I also have reason to believe they were causing problems at some of my (formerly) local customers as well (but no proof on their neworks).
-
@dafyre said in Concern Around Hackers Using DHCP Pool:
@scottalanmiller said in Concern Around Hackers Using DHCP Pool:
Everyone truly believes that customers of a doctor's office will sit in the office, and knowing that they are doing something that will hurt no one and have no useful effect, take the time to try to tie up IP addresses? I'm lost, what motivation do you think people have for this? Why would someone do this? How many of you have seen people do this in the real world?
Sad, but true. I had someone doing this on a network with 8k IP addresses. I also have reason to believe they were causing problems at some of my (formerly) local customers as well (but no proof on their neworks).
And that person was a customer sitting in the office of a small business where everyone involved could see him and could have him arrested? 8K DHCP on a single lease scope seems like a lot.
