Can't connect HA to the internet but works fine locally

Installation
1

Hello!

I have been using home assistant for a long time, (2018 ish). I have ran it on a dell optiplex as haos always. It runs fine and everything until now. My network in my house is flat as it can be, 1 desktop switch plugged into a verizon fios g3100 router.

I can ping from the console on HAOS to the router, and the public IP.
I can nslookup google.com. Which means the DNS is running.
I looked at the default route which is a 192.168.1.1 and it routes it there fine.
I can access HA locally via its ip & homeassistant.local
I can ssh into the HAOS fine with dropbear, and access it locally.

I am unable to get it to route traffic from it to the world, even though I am able to access the web from the same port, and router
When I run nmcli con edit "Home Assistant OS default" It returns nothing, which I suspect causes issues.

https://github.com/home-assistant/operating-system/blob/5eb7ccb7611a06a00013d4292b5e8bd75147195d/Documentation/network.md

I work with some network engineers, and they looked at all the tables, and said they were fine.

I am just stumped. Is there a no internet setting on the home assistant that I am missing?

Thanks for your help!

docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: false
interfaces:
- connected: true
  enabled: true
  interface: eno1
  ipv4:
    address:
    - 192.168.1.217/24
    gateway: 192.168.1.1
    method: auto
    nameservers:
    - 192.168.1.1
    ready: true
  ipv6:
    address:
    - [retacted]
    - [retacted]
    gateway: null
    method: auto
    nameservers: []
    ready: true
  mac: [retacted]
  primary: true
  type: ethernet
  vlan: null
  wifi: null
supervisor_internet: false

ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2050ms

# nmcli g status
STATE                  CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
connected (site only)  limited       missing  enabled  missing  enabled 


    Core 2024.9.3
    Supervisor 2024.10.3
    Operating System 13.1
    Frontend 20240909.1

ping 192.168.1.1
192.168.1.1 is alive!
ping 8.8.8.8
^C
ping REDACTED.duckdns.org
REDACTED.duckdns.org is alive!

# cat NetworkManager.conf 
[main]
dns=default
plugins=keyfile
autoconnect-retries-default=0
rc-manager=file

[keyfile]
unmanaged-devices=type:bridge;type:tun;driver:veth

[logging]
backend=journal

[connection]
connection.mdns=2
connection.llmnr=2

[connectivity]
uri=http://checkonline.home-assistant.io/online.txt
interval=600

[device]
wifi.scan-rand-mac-address=no

# cat netconfig 
#
# The network configuration file. This file is currently only used in
# conjunction with the TI-RPC code in the libtirpc library.
#
# Entries consist of:
#
#       <network_id> <semantics> <flags> <protofamily> <protoname> \
#               <device> <nametoaddr_libs>
#
# The <device> and <nametoaddr_libs> fields are always empty in this
# implementation.
#
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -
unix       tpi_cots_ord  -     loopback  -      -       -
2

did you tryed to use Dataplicity integration?

3

Did you restart the HA host? Not just the core!

4

I have not used Dataplicity. I don’t need it as most of my stuff I can do from home. I use duckdns.

5

I physically restarted a bunch of time physically many times. Even just moving the machine directly into the router itself.

6

Check subnet mask of router and HA.

7

I checked that, the router is at 192.168.1.1, it assigns that from the 192.168.1.0/24, and the HA is getting 192.168.1.217, and it knows the router is 192.168.1.1. I can get it locally, but is not going anywhere but the router, and no internet.

8

Not the IP addresses, but the subnet masks.

9

The subnet for the router is 255.255.255.0 at 192.168.1.0 /24.

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 98:90:96:d4:05:b7 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.1.217/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1

# ip route
default via 192.168.1.1 dev eno1 proto dhcp src 192.168.1.217 metric 20100 
172.30.32.0/23 dev hassio proto kernel scope link src 172.30.32.1 
172.30.232.0/23 dev docker0 proto kernel scope link src 172.30.232.1 
192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.217 metric 100
10 
traceroute 8.8.8.8
11

Hey nick!
In homeassistant os, traceroute isn’t a thing

# traceroute 8.8.8.8
-sh: traceroute: not found
12

Silly question…
Have you added the port forwarding for port 8123 to your home assistant machines ip in your router?

13

It is here, using advanced Ssh & web terminal addon

14

However I am a little confused about your problem. Are you saying your HA machine can’t contact the internet. So updates, the default weather integration, your map dashboard etc are not working?

15

Yes the port is forwarded. I have checked this multiple times, and am able to telnet the port that I forwarded to. (443)

16

Correct, I am unable to connect to the Internet. But locally it works perfectly fine. Something about the connection with the Internet isn’t working. Anything that needs the Internet, weather, updates, etc doesn’t work at all.

17

I have not tried that. I will try that in a few hours and report back the trace route.

18

This is irrelevant to outgoing connections.

19

Are you using trusted networks in your configuration.yaml?

20

I tried to install the Advanced SSH & Web Terminal:

image
image1062×686 59.8 KB

There is no trusted networks in my configuration.