Network
Settings → Network controls whether the Pod can reach the internet. Local only blocks internet traffic with firewall rules and keeps local traffic working, so the app, the iOS app, the Dial, HomeKit, MQTT, and backups on your network continue to work.

Change internet access
- Select the Internet access switch.
- The card asks Allow internet access? or Block internet access?. Select Confirm.
The row shows local only when internet access is blocked and allowed when it is not.
When the Pod needs the internet
Updates download new code, so they need internet access. If access is blocked, Updates offers to allow it temporarily and blocks it again when the update finishes.
Core is built for a trusted home network. Its local controls do not require a password. Never forward the Pod’s ports to the internet. The System dashboard shows Blocking when the firewall is on.
How the firewall works
The Pod still runs Eight Sleep’s stock firmware services next to sleepypod, and those services keep trying to reach Eight Sleep’s servers. sleepypod blocks them in three layers. Each one covers a gap the others leave.
1. Firewall rules
Local only installs firewall rules on the Pod. The Pod can send traffic only to:
- private network addresses (
10.0.0.0/8,172.16.0.0/12,192.168.0.0/16), which covers your home network - time servers (NTP, UDP port 123), so the clock stays correct
- itself (loopback)
- replies on connections that are already open
All other outbound traffic is dropped. Turning internet access off in Settings also drops inbound traffic from outside your home network. This is the main block. It is off while Internet access is allowed, and an update opens it briefly to download new code.
2. Blocked Eight Sleep domains
Whether internet access is allowed or not, the Pod treats Eight Sleep’s domain names as if they don’t exist.
On Pods that include dnsmasq, a small DNS resolver on the Pod answers every 8slp.net name, plus Eight Sleep’s log endpoint kinesis.us-east-1.amazonaws.com, with “no such domain” (NXDOMAIN). Lookups for anything else are forwarded to your router as usual. If that resolver stops, the Pod switches straight back to your router’s DNS, so a failure never leaves the Pod unable to look up names. Pods without dnsmasq, or where the resolver can’t start because another service already uses port 53, rely on the firewall alone. internet-control status (see Check the firewall on your Pod) shows which layer is active.
This layer keeps the stock firmware from uploading data while internet access is allowed.
Never point Eight Sleep names at 0.0.0.0 or another address in /etc/hosts. On Linux, 0.0.0.0
reaches the Pod itself. Some Pod firmware then connects to its own port, fails, and retries every
few milliseconds, filling the log and memory until the web interface stops responding and the red
light turns on. sleepypod 3.6.0 and 3.6.1 added such entries to /etc/hosts, and their DNS layer
answered 0.0.0.0 too; 3.6.2 and later remove both. If your Pod is affected, run sudo /home/dac/sleepypod-core/scripts/internet-control hosts-unblock and sudo /home/dac/sleepypod-core/scripts/internet-control dns-unblock, keep internet access blocked, and
update. hosts-unblock only removes sleepypod’s own entries: check grep -n 8slp /etc/hosts
afterwards and delete any line you added yourself.
3. Stock services turned off
Installs and updates turn off the stock services that sleepypod doesn’t need:
- Eight Sleep’s log shipper (
vector) and metrics agent (telegraf). Without this,vectorwould keep sending the Pod’s system logs to Eight Sleep’s servers and store up to 256 MB of unsent logs on the Pod’s flash storage. - The stock firmware updater (
swupdate) and connectivity watchdog (defibrillator,eight-kernel). A stock update can remove root access and sleepypod, and the watchdog can repeatedly reboot a Pod that can’t reach the internet. They stay off unless you allow firmware updates; see Firmware updates.
The sensor firmware that sleepypod relies on stays running.
Why your DNS server still sees Eight Sleep lookups
If you run a network-wide DNS filter such as AdGuard Home or Pi-hole, you may see the Pod look up raw-api-upload.8slp.net or kinesis.us-east-1.amazonaws.com many times. This stops once the Pod’s own resolver is blocking those names, because the Pod answers them itself. Until then, a lookup is not a connection:
- DNS requests go to a server on your home network, which the firewall allows.
- In local-only mode, the connection that would follow goes to the internet, which the firewall drops.
- The stock service then retries, so the same name appears over and over.
You can block these names in your DNS filter as well, but set it to answer NXDOMAIN or REFUSED, not 0.0.0.0 or “Null IP”, for the reason in the warning above. In AdGuard Home this is Settings → DNS settings → Blocking mode.
Check the firewall on your Pod
Connect over SSH and run:
sudo iptables -S OUTPUT; sudo iptables -S SLEEPYPOD-BLOCK 2>/dev/null # local only: OUTPUT ends in "-j DROP", or jumps to SLEEPYPOD-BLOCK, which does
curl -s -m 5 -o /dev/null -w "%{http_code}\n" https://1.1.1.1 || echo blocked # prints "blocked" when local only
nslookup foo.8slp.net 127.0.0.1 # "NXDOMAIN" when the Pod's resolver blocks Eight Sleep names
grep -c 8slp /etc/hosts # must print 0
systemctl is-enabled vector swupdate # "masked" for each, unless you allowed firmware updatesFor a summary of every layer, run sudo /home/dac/sleepypod-core/scripts/internet-control status.
Source reference: Internet card · Internet access API · Firewall and name blocking · Stock telemetry · Firewall status