I have a raspberry pi 4B that’s been running successfully for over a month. We moved, as a result the ip schema had to be migrated, it’s plugged into our Bell Home Hub 3000.
The dietpi was configured as our DHCP as a result of Bell not allowing dns configuration, according to them it’s a security risk to allow people to modify or control their DNS.
I enabled dhcp on the pihole, and disabled it on our bell equipment.
Today the connection does not show as “connected”, or it shows as connected, however in either instance I’m unable to ping(from the pi) 192.168.2.1(the bell equipment).
From my pc I can ping 192.168.2.1
ethtool eth0 shows me that it’s connected
ip a shows adequate information and likewise is able to pull an ip from the bell equipment(when dhcp is on obv), but still unable to ping 192.168.2.1
I have attempted directly modifying /etc/network/interfaces with both static and dhcp, as well a custom up script in /etc/network/interfaces.d/ifcfg-eth0 – neither changed the behaviour.
Any help with this would be appreciated please.
our internals are set to the standard 192.168.2.0/24. The gateway is configured as 192.168.2.1
the pi has an ip of 192.168.2.100
On reboot I can get a response from the gateway, shortly afterwards it drops
I can connect to the pi from the network, eg. from my laptop with 192.168.2.250
I have attempted to remove the connection and add it back in.
DietPi version |
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
Kernel version |
Linux DietPi 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
RPi 4 Model B (aarch64)
Power supply used | (EG: 5V 1A RAVpower)
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
- Software title | (EG: Nextcloud)
- Was the software title installed freshly or updated/migrated?
- Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
- Bug report ID |
Steps to reproduce