Internet connection not working

revil · July 22, 2023, 9:38am

Creating a bug report/issue

Required Information

DietPi version | v8.19.1
Distro version | bullseye
Kernel version | aarch64
Architecture | dpkg --print-architecture
SBC model | Orange Pi 5
Power supply used | Orange Pi 5V
SD card used | NvME

Steps to reproduce

Boot

Expected behaviour

Internet connection should be established

Actual behaviour

No connection possible

Extra details

I think it has something to do with the killswitch blocking access, have purged dietpi-vpn, rebooted, reset adapter multiple times, can connect to router, but does not allow actual internet access.

I am a little bit out of my depth here

Joulinar · July 22, 2023, 9:44am

can you share following

ip a

revil · July 22, 2023, 9:59am

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 mq state UP group default qlen 1000
    link/ether 86:01:32:f4:23:3c brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.108/24 brd 192.168.178.255 scope global dynamic eth0
       valid_lft 859976sec preferred_lft 859976sec

Joulinar · July 22, 2023, 10:16am

Following is working?

ping 192.168.178.1
ping 1.1.1.1
ping 8.8.8.8

revil · July 22, 2023, 10:25am

only the first works

Joulinar · July 22, 2023, 10:29am

What is the error message one the other one? Can you share as well

ip r

revil · July 22, 2023, 10:32am

default via 192.168.178.1 dev eth0
192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.108

and it says
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
— 1.1.1.1 ping statistics —
47 packets transmitted, 0 received, 100% packet loss, time 46617ms

Joulinar · July 22, 2023, 10:39am

That looks good. You device is not blocked by accident on your router?

revil · July 22, 2023, 10:42am

double checked, everything is good there

Joulinar · July 22, 2023, 10:52am

For testing could you try to assign a different static IP within dietpi-config network settings.

revil · July 22, 2023, 10:59am

done, assignment was no problem, but results remain the same, result stays

curl: (28) Failed to connect to dietpi.com port 443: Connection timed out

connection tests fail, local LAN access works, is there anything in iptables preventing access maybe?

Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ES                         TABLISHED
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ssh
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:5252
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:1340
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:6789
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:9696
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:6767
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:7878
ACCEPT     tcp  --  fritz.box            anywhere             tcp dpt:6881
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:https
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:http
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:ms-wbt-ser                         ver
ACCEPT     all  --  d99fa6e9-6951-19bd-1e22-171c0531ee11.fritz.box  anywhere

Chain FORWARD (policy DROP)
target     prot opt source               destination

Chain OUTPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             192.168.0.0/16
ACCEPT     all  --  anywhere             172.16.0.0/12
ACCEPT     all  --  anywhere             10.0.0.0/8
ACCEPT     udp  --  anywhere             connected-by.global-layer.com  udp dpt:                         openvpn

root@DietPi:~# Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ES                         TABLISHED
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:ssh
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:5252
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:1340
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:6789
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:9696
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:6767
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:7878
ACCEPT     tcp  --  fritz.box            anywhere             tcp dpt:6881
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:https
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:http
ACCEPT     tcp  --  ron.fritz.box        anywhere             tcp dpt:ms-wbt-ser                         ver

Joulinar · July 23, 2023, 5:46pm

I’m not the iptables specialist. But did you try to setup something like a firewall? Or do you use ufw?

revil · July 24, 2023, 6:29am

Nope to both, I only fumbled with iptables and the dietpi-vpn. I swallowed the bitter pill yesterday and flashed it anew, it’s working now. Thanks for your help though, appreciate it!