• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • That’s not how that works. network_mode: host shares the network namespace with the container host, so it doesn’t do any NAT, it only exists on the host’s IP. It would be akin to running a natively installed app, rather than in a container. macvlan networking is what gives a container its own IP on the logical network, without the layer of NAT that the default bridge mode networking that docker typically does.




  • StarkZarn@infosec.pubtoPrivacy@lemmy.mlAh yes, smart lights need Tor.
    link
    fedilink
    English
    arrow-up
    111
    arrow-down
    1
    ·
    1 year ago

    It’s just an NTP pool. The device is trying to update it’s time. Likely it made many other requests to other servers when this one didn’t work.

    Maintaining up to date lists of anything is a game of whack a mole, so you’re always going to get weird results.

    If you’re actually unsure, pcap the traffic on your pfsense box and see for yourself. NTP is an unencrypted protocol, so tshark or Wireshark will have no problem telling you all about it.

    That said, I’d still agree with the other poster about local integration with home assistant and just block that sucker from the Internet.