Troubel w/ initial DietPi install (Tinker & Rasp)

[vogel]

I am a noob and am trying to install the DietPi OS on either an Asus Tinkerboard or a RaspPi SBC. I am hitting a brickwall with both attempts. I cannot get past the check for network connectivity. I have turned on (and ioff) ivp6 with no avail. And have searched the inet for other suggest - again - with no avail. Any suggestion would be greatly appreciated.

[MichaIng]

Please try to change the connection test IP and dns test domain in dietpi.txt to 9.9.9.9 and dns9.quad9.net

Some local networks/routers resolve 1.1.1.1 internally instead of to Cloudflare DNS which has this IP globally assigned.

We already changed this to be the new defaults for new images due to this found issues.

[Joulinar]

Hi,

Do nano /DietPi/dietpi.txt and search for the following 2 lines:

Code: Select all

# General connection and DNS testing
# - IP to ping when checking network connectivity. Default: 1.1.1.1 (Cloudflare DNS, should be very fast world-wide)
CONFIG_CHECK_CONNECTION_IP=1.1.1.1
# - Domain to ping when checking DNS resolver. Default: one.one.one.one (Cloudflare DNS domain, see above)
CONFIG_CHECK_DNS_DOMAIN=one.one.one.one

you can change it to 9.9.9.9 and dns9.quad9.net

[vogel]

Thanks you two for the quick response - I was called away but am back again. I changed 'dietpi.txt' as suggested but upon restart, the same error occurs - failure to verify connectivity. As a backup up test , I pinged 9.9.9.9 & dns9,quad9.net on a linux desktop machine, But that failed to return a response. I'm still at a lose.

[Joulinar]

this is strange that you are not able to connect to 1.1.1.1 or 9.9.9.9. These are global DNS servers that should be available globally. Are you sure your Internet connection is working well?

What about 8.8.8.8 ??? This would be google.com DNS server.

[vogel]

I think I'm operating above my weight class. I have reset my modem & router and still cannot ping anyone. I have attempted 1.1.1.1, 9.9.9.9, ebay.com, google.com, and others without receiving a response. Upon termination of each attempt via CTL-C, the info says 6 bundles sent, no replies received. (However, 'ping localhost' works as expected). So, I would like to thank you for you help, but I am backing away from this chat and will attempt to to learn more about firewalls and such.

[Joulinar]

pls can you past the following

Code: Select all

ip a
ip r

[vogel]

Here are the outputs for the ip cmds. Note that these are run on a linux ((Ubuntu) machine, not the DietPi Raspi. (I forgot to say previously that I can ping my router from the linux machine but no one else.)

<my user name>:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether d4:ae:52:c2:c3:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.200.98/24 brd 192.168.200.255 scope global dynamic noprefixroute enp5s0
valid_lft 79806sec preferred_lft 79806sec
inet6 fe80::6ddd:83b9:6091:f4f2/64 scope link noprefixroute
valid_lft forever preferred_lft forever
<my user name>:~$ ip r
default via 192.168.200.1 dev enp5s0 proto dhcp metric 100
169.254.0.0/16 dev enp5s0 scope link metric 1000
192.168.200.0/24 dev enp5s0 proto kernel scope link src 192.168.200.98 metric 100

Here are the outputs on the DietPi Raspi.

root@DiePit:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

root@DietPi:~# ip r
default via 192.168.200.1 dev eth0
192.168.200.0/24 dev eth0 proto kernel scope link src 192.168.200.87

[Joulinar]

hmm looking to your dietpi RPi, it seems you don't have have an IP address assigned at all. Because eth0 interface doesn't contain any valid IP. Do you have set STATIC IP or DHCP on your dietpi RPi?

[vogel]

I am not sure - here is the NETWORK stuff from dietpi.txt

##### Networking Options #####
# Enable Ethernet or WiFi adapter: 1=enable | 0=disable
# - If both Ethernet and WiFi are enabled, WiFi will take priority and Ethernet will be disabled.
# - If using WiFi, please edit dietpi-wifi.txt to pre-enter credentials.
AUTO_SETUP_NET_ETHERNET_ENABLED=1
AUTO_SETUP_NET_WIFI_ENABLED=0

# Force ethernet speeds: 0=automatic speed | 10 = 10Mbit | 100 = 100Mbit etc
# - This is mainly aimed at Pine A64 which may have an HW issue that causes unstable 1Gbit link.
AUTO_SETUP_NET_ETH_FORCE_SPEED=0

# Enter your Static Network details below, if applicable.
AUTO_SETUP_NET_USESTATIC=1
AUTO_SETUP_NET_STATIC_IP=192.168.0.100
AUTO_SETUP_NET_STATIC_MASK=255.255.255.0
AUTO_SETUP_NET_STATIC_GATEWAY=192.168.0.1
AUTO_SETUP_NET_STATIC_DNS=8.8.8.8