Thank you for your message. Eth is preferred 192.168.1.10 so ssh into DietPi (from the LAN) and
WiFi disabled via diepi-launcher > dietpi-config > network options adapters
Adapter Options
Ethernet : Available | [On] | Connected
WiFi : Not Found | [Off] | Disconnected
However, static eth setting seems to have defaulted to dhcp so I set it static again, reboot and check it again:
Ethernet Details:
Usage : Sent = 25 MiB | Received = 119 MiB
Address : IP = 192.168.1.10 | Mask = 255.255.255.0 | Gateway = 192.168.1.1 | DNS = 1.1.1.1 1.0.0.1
DHCP/STATIC IP
Change Mode : [STATIC]
Copy : Copy current address to "Static"
Static IP : [192.168.1.10]
Static Mask : [255.255.255.0]
Static Gateway : [192.168.1.1]
Static DNS : [1.1.1.1 1.0.0.1]
This time STATIC so ok.
More tests:
dietpi@DietPi:~$ sudo ip addr
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
link/ether
inet 192.168.1.10/24 brd 192.168.68.255 scope global dynamic eth0
valid_lft 4808sec preferred_lft 4808sec
dietpi@DietPi:~$
So only eth0, good
dietpi@DietPi:~$ dig 192.168.1.10 -p 53 google.com
; <<>> DiG 9.16.37-Debian <<>> 192.168.1.10 -p 53 google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39545
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;192.168.1.10. IN A
;; AUTHORITY SECTION:
. 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023052300 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue May 23 09:02:30 CEST 2023
;; MSG SIZE rcvd: 118
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15060
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 210 IN A 142.250.200.110
;; Query time: 12 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue May 23 09:02:30 CEST 2023
;; MSG SIZE rcvd: 55
dietpi@DietPi:~$ dig 127.0.0.1 -p 5335 google.com
; <<>> DiG 9.16.37-Debian <<>> 127.0.0.1 -p 5335 google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
So this dig fails as in my first post.
dietpi@DietPi:~$ cat /etc/resolv.conf
nameserver 1.1.1.1
nameserver 1.0.0.1
No changes here.
Even though port forwarding is enabled in the router external 22 to internal 22 in machine 192.168.1.10 connecting via ssh from the internet is not successful (error: connection timed out). Connecting via ssh within the LAN is successful, though.
Could you please clarify how to achieve this? I have some understanding of Linux but not a pro…
Also, if unbound can’t reach internet “but this could be because unbound can’t reach the internet (bc of the two network routes)”. I don’t know how to achieve this, but a bit of feedback and I can test extensively.
Thank you for your support indeed.