• 0 Posts
  • 68 Comments
Joined 2 years ago
cake
Cake day: June 19th, 2023

help-circle



  • That person is missing the point that a randomized MAC will often get a different DHCP lease, and the MAC address is used in that, so the IP address will change.

    On a trusted Wi-Fi network, disable MAC randomization on your clients, and if possible reserve an IP address for their non-random MAC address. Some devices have deterministic random per WiFi network, which could also work. In iOS this is WiFi network -> private WiFi address “fixed”. “Rotating” would cause your pihole problems.


  • I’m interviewing people right now and I feel like it’s actually the opposite. I know for a lot of folks this is true, and I’ve been through those interviews, but fuck, I would love if I could find somebody who is just on par with the interview questions and could just answer them all satisfactorily, because that’s what we actually need.












  • From my understanding, it only checks DNS when it initially connects, and so if the public IP changes the connection just stops working.

    This is pretty standard TCP network behavior for long duration connections. The client queries dns for the IP address, opens a socket, and leaves it open as long as needed.

    One thing that would help here is some kind of keepalive feature, like a client to server TCP connect or SYN, or better yet a higher level protocol signal. Check your client to see if there is some tunable keepalive. It may be set so something long like 1h.