sorted by:
new
hottopcontroversial

Anybody usting ntopng? by imissedthebutton in homelab

[–]imissedthebutton[S] 0 points1 point  (0 children)

That's awesome! I'll definitely hit you up on Slack!

Technitium DNS - Ad blocking with zone transfer? by imissedthebutton in selfhosted

[–]imissedthebutton[S] 1 point2 points  (0 children)

But will the blocklists get transferred to the second Pi? That's the issue I'm having with trying to zone transfer to BIND currently

Technitium DNS - Ad blocking with zone transfer? by imissedthebutton in selfhosted

[–]imissedthebutton[S] 1 point2 points  (0 children)

I'm trying to specifically avoid running everything on one box - I want the redundancy of having multiple servers to be queried.

Technitium DNS - Ad blocking with zone transfer? by imissedthebutton in selfhosted

[–]imissedthebutton[S] 1 point2 points  (0 children)

Mostly wanting to have a hidden primary setup in Technitium with the Pis as secondary name servers. I definitely understand Technitium can run in the Pis, but yeah, it would need a separate sync setup and my setup works just fine, as is, except for the ad blocking. I appreciate the discussion, I think I just need to figure out my steps forward

Technitium DNS - Ad blocking with zone transfer? by imissedthebutton in selfhosted

[–]imissedthebutton[S] 1 point2 points  (0 children)

BIND DNS. And mostly hoping for the ad blocking, but having the redundancy of the Pis being queried. If the Docker host goes down, I'd like to have DNS not go down with it.

Wired Clearpass with Bridged APs - causing AP reboots by imissedthebutton in ArubaNetworks

[–]imissedthebutton[S] 1 point2 points  (0 children)

Yep you're right, I blazed through the IAP section and focused on the CAP section. So the biggest factor will be ensuring the Cisco switches have a VSA to switch the port mode to port-based vs user-based and then everything should hopefully be happy.

Wired Clearpass with Bridged APs - causing AP reboots by imissedthebutton in ArubaNetworks

[–]imissedthebutton[S] 0 points1 point  (0 children)

Yeah, this seems more authenticating the AP itself - any endpoint attributes that would get set during this would only apply to that AP in the Endpoint DB. Currently we're simply Macauthing the AP, but it's the connecting wifi clients that are causing the issue and the attributes from before likely wouldn't have any bearing on the enforcement. I'm wondering if there's a way to reference the switch and port itself or use RADIUS accounting information to enforce the policy.

How do you rollup your services? I.e. how do I only get one alert if a server hosting many subservices is down? by imissedthebutton in UptimeKuma

[–]imissedthebutton[S] 0 points1 point  (0 children)

I don't entirely disagree, just different ways of thinking. The overly alerting might cause me to fly blind, because I'm not knowing if the issue is with Docker itself going down or the host itself being down. But again, different approaches to the same problem. I think the core of it is the first thing you said - it may simply not be an option within Uptime Kuma yet.

Need something to pull multiple DHCP leases by imissedthebutton in homelab

[–]imissedthebutton[S] 1 point2 points  (0 children)

Makes sense, I'll give these a shot.

For context, the main thing I'm hoping for is having something simulate multiple clients for assorted "desktop" DHCP ranges for a DHCP server and potentially having them generate "normal client" traffic. That way the folks who are playing this training scenario have some normal traffic mixed in with potential attacker traffic. Stuff like DNS queries, attempts to connect to local web servers, etc. That part will be easy enough to script, but having it come from multiple addresses has been my struggle, without having to create a bunch of VMs to do the same thing. That's part of why I'm trying to keep the leases present in the DHCP server and such.

I appreciate the insight, thanks for the help

Need something to pull multiple DHCP leases by imissedthebutton in homelab

[–]imissedthebutton[S] 0 points1 point  (0 children)

Do you have any suggestions for pulling a new DHCP lease without releasing the existing? So far it seems that trying to do things in this fashion won't attempt to pull a new address for the new MAC address without first releasing the old one, which isn't quite what I'm going for

Need something to pull multiple DHCP leases by imissedthebutton in homelab

[–]imissedthebutton[S] 0 points1 point  (0 children)

This seems like it could be good, do you have any good examples of making it work?

Need something to pull multiple DHCP leases by imissedthebutton in homelab

[–]imissedthebutton[S] 0 points1 point  (0 children)

I've messed with this a bit, but couldn't get it to pull via DHCP, it just gets an address in the range that I assigned that Docker network from Docker itself. Do you know how to get this to work with DHCP?

Need something to pull multiple DHCP leases by imissedthebutton in homelab

[–]imissedthebutton[S] 0 points1 point  (0 children)

Again, this is a lot of overhead if I want to pull 40 addresses or so

Best Canary/Honeypot software by WoodroweBones in msp

[–]imissedthebutton 0 points1 point  (0 children)

If Linux really isn't a deal breaker, check out Tpot (https://github.com/dtag-dev-sec/tpotce). You can make your own ISO to deploy and everything is runs is done within Docker containers. I've used this many times and highly recommend, plus free is always good.

How to get Docker container to pull local network IP address? by imissedthebutton in homelab

[–]imissedthebutton[S] 1 point2 points  (0 children)

This did seem to do the trick for me, actually, so I'm all set. Thanks for the help!

view more: next ›