Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checking network connectivity, inability to ping #3395

Closed
ivavid opened this issue Feb 25, 2020 · 4 comments
Closed

Checking network connectivity, inability to ping #3395

ivavid opened this issue Feb 25, 2020 · 4 comments
Labels
External bug 🐞 For bugs which are not caused by DietPi. Known Issue 🐛 Workaround available 🆗 Workaround is available/has been implemented, but a definite solution should be found when possible.

Comments

@ivavid
Copy link

ivavid commented Feb 25, 2020

Creating a bug report/issue

Required Information

  • DietPi version | v6.28.0 (MichaIng/master)
  • Distro version | buster (ID=5)
  • Kernel version | Linux DietPi 4.19.75-v7+ DietPi-System | Quirks noticed by v158 image update  #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux
  • SBC device | RPi 3 Model B+ (armv7l)
  • Power supply used | Laptop USB port
  • SDcard used | Kingston CANVAS Select Plus 16 GB

Additional Information (if applicable)

  • Software title | DietPi-Login
  • Fresh installation of DietPi
  • Automatic bugreport seems to fail too, 462d99eb-1378-4351-b4b0-87f9ee5f39e9

Steps to reproduce

logon to dietpi with default username and password

Expected behaviour

I'm not sure as this is the first time I try dietpi.

Actual behaviour

in the terminal:
[FAILED] DietPi-Login | Checking network connectivity: ping -c 1 -W 5 1.1.1.1

in the DietPi-Login | Error handler:
Checking network connectivity

  • Command: ping -c 1 -W 5 1.1.1.1
  • Exit code: 1
  • DietPi version: v6.28.0 (MichaIng/master) | HW_MODEL:3 | HW_ARCH:2 | DISTRO:5
  • Image creator: DietPi Core Team
  • Pre-image: Raspbian Lite

Log file content:
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.

--- 1.1.1.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

Extra details

I do not expect a connectivity error as the Internet can be reached (files downloaded), but ping seems to not work from my location.

@Joulinar
Copy link
Collaborator

@seron

many thanks for your report.

Hi, if you are not able to ping 1.1.1.1 you would have local issues as it's part of Cloudflares DNS Server. It is the globally available IP address for Cloudflares 1.1.1.1 DNS resolver:

https://www.dnswatch.info/dns/dnslookup?la=en&host=1.1.1.1&submit=Resolve

Anyway if you like to change this, you can do it as follow.

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

# 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 8.8.8.8 and google.com

It's a similar issue like this #3337

@Joulinar Joulinar added External bug 🐞 For bugs which are not caused by DietPi. Known Issue 🐛 Workaround available 🆗 Workaround is available/has been implemented, but a definite solution should be found when possible. labels Feb 25, 2020
@MichaIng
Copy link
Owner

For reference, default has been changed for new images (not applied to all ones yet): ffd9431

@ivavid
Copy link
Author

ivavid commented Feb 26, 2020

Thanks. It worked.

Will changes to /DietPi/dietpi.txt be saved permanently?

@Joulinar
Copy link
Collaborator

Yes

@ivavid ivavid closed this as completed Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
External bug 🐞 For bugs which are not caused by DietPi. Known Issue 🐛 Workaround available 🆗 Workaround is available/has been implemented, but a definite solution should be found when possible.
Projects
None yet
Development

No branches or pull requests

3 participants