No internet connection
  1. Home
  2. Technical Support

Internet Not working on TinyPilot

By Steven Dinh @stevendinhdev
    2024-03-07 14:45:53.415Zassigned to
    • @cghague

    Hi,

    I'm using tinypilot remotely using tailscale and somehow internet is not working in tinypilot. I log in using ssh on tinypilot and tried to ping 8.8.8.8. but internet is not going. I can access tinypilot from local machine but not through tailscale.

    Reply
    • 7 replies
    1. C
      Charles Hague @cghague2024-03-07 17:47:25.153Z

      Hi Steven, thanks for your message. I'm sorry you're having issues connecting to the Internet.

      Your TinyPilot device can automatically obtain network settings when connecting to a compatible network. However, some networks require manual configuration. Can you ask your network administrator if this is the case for this network?

      It'd also be good to verify that other devices on the network can access the Internet to rule out filtering and firewalls. You mentioned connecting to your TinyPilot device from a local machine on the same network. Can you please confirm if that machine can access the Internet (e.g., can it ping 8.8.8.8)?

      Reply
      1. SSteven Dinh @stevendinhdev
          2024-03-07 18:01:21.005Z

          Yes, can ping 8.8.8.8 from local machine. Also it worked for a while without any issue and from this morning it doens't work

          Reply
          1. CCharles Hague @cghague2024-03-08 00:44:28.520Z

            Thanks for confirming!

            It sounds like this issue may be a transient problem. I appreciate it's a bit of a cliche, but could you please try restarting your TinyPilot device? Restarting will cause a full reload of the networking system and ensure it has an up-to-date configuration.

            If that doesn't work, could you please share the output of the following commands?

            ip route show | grep default
ip addr show eth0

            The above commands will include information about your network, so if you'd prefer to keep the details private, please send them to us by e-mail instead of replying here.

            Reply
            1. SSteven Dinh @stevendinhdev
                2024-03-27 00:41:58.523Z

                pilot@tinypilot-curo:~ $ ip route show | grep default
                default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.115 metric 202
                pilot@tinypilot-curo:~ $ ip addr show eth0
                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
                link/ether d8:3a:dd:5f:4f:91 brd ff:ff:ff:ff:ff:ff
                inet 192.168.1.115/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
                valid_lft 10789sec preferred_lft 3734sec
                inet6 fd4f:7a65:fbdb:1d4c:5b46:c1f1:b818:5ae0/64 scope global deprecated dynamic mngtmpaddr noprefixroute
                valid_lft 1575sec preferred_lft 0sec
                inet6 2603:8080:9400:54bb:12f3:fd43:df1c:f763/64 scope global dynamic mngtmpaddr noprefixroute
                valid_lft 604575sec preferred_lft 604575sec
                inet6 2603:8080:9400:54bb::111c/128 scope global dynamic noprefixroute
                valid_lft 382014sec preferred_lft 382014sec
                inet6 fe80::d4b5:69e0:c28a:5323/64 scope link
                valid_lft forever preferred_lft forever
                pilot@tinypilot-curo:~ $ ip addr show eth0
                2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
                link/ether d8:3a:dd:5f:4f:91 brd ff:ff:ff:ff:ff:ff
                inet 192.168.1.115/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
                valid_lft 10736sec preferred_lft 3681sec
                inet6 fd4f:7a65:fbdb:1d4c:5b46:c1f1:b818:5ae0/64 scope global deprecated dynamic mngtmpaddr noprefixroute
                valid_lft 1522sec preferred_lft 0sec
                inet6 2603:8080:9400:54bb:12f3:fd43:df1c:f763/64 scope global dynamic mngtmpaddr noprefixroute
                valid_lft 604522sec preferred_lft 604522sec
                inet6 2603:8080:9400:54bb::111c/128 scope global dynamic noprefixroute
                valid_lft 381962sec preferred_lft 381962sec
                inet6 fe80::d4b5:69e0:c28a:5323/64 scope link
                valid_lft forever preferred_lft forever

                Reply
                1. CCharles Hague @cghague2024-03-28 17:45:56.790Z

                  Thanks for getting back to me!

                  The output shows that your TinyPilot device has established a network connection and knows how to communicate with your router, indicating that the problem is likely not the TinyPilot but the network itself. The following commands will help narrow down where the issue lies. Could you please run them over SSH and let me know the output?

                  ping -c 4 192.168.1.1
ping -c 4 1.1.1.1
ping -c 4 tinypilotkvm.com
                  Reply
                  1. SSteven Dinh @stevendinhdev
                      2024-04-09 10:17:58.318Z

                      I'm getting 4 packets transmitted, 0 received, 100% packet loss, time 3058ms

                      Reply
                      1. CCharles Hague @cghague2024-04-11 22:25:33.554Z

                        Thanks for getting back to me! Can you please confirm if that result applies to all three of the ping tests, and if you were able to restart your TinyPilot device after my earlier message?

                        The most likely explanation is that your TinyPilot device has a network connection, but the default gateway isn't allowing it to access the Internet. As a final check, could you please try running the following command? It will force the ping test to run over the local network, ruling out Tailscale issues.

                        ping -c 4 -I eth0 tinypilotkvm.com
                        Reply
            ReplyAdd progress note