Hi all, Problem: I run into a problem where I am able to ping within the Host OS, but I am unable to do this from within the container. In the container, pinging for the wwan0 device resolves in a connect: Network is unreachable message. The same configuration is working for other devices runnin…

Hi @larsjeh , Welcome to balena forums! Could you please clarify how you configure your container? Do you deploy it with a docker-compose.yml file (as described in our docs https://www.balena.io/docs/learn/develop/multicontainer/ ) or without? If you do this with docker-compose.yml file, do you set…

Hi Roman, Thank you for your response! We deploy with a normal Dockerfile, so it is basically a single container running on the device. We don’t use a docker-compose.yml file.

Ok, got it. You mentioned that you have a working ethernet connection. Does it mean that when you do ping -I <ethernetInterface> google.com, it succeeds?

Yes, that is correct! wwan0 is our 4G connection. Inside the container ping -I eth0 google.com :white_check_mark: ping -I eth0 8.8.8.8 :white_check_mark: ping -I wwan0 google.com :x: ping -I wwan0 8.8.8.8 :white_check_mark: From the HostOS ping -I eth0 google.com :white_check_mark: ping -I e…

Ok, I see. And how do you get the DNS server name? Is it set by the DHCP server or is it a static config in system-connections? I would suggest trying to ping your DNS server via wwan0 interface. Is it possible the DNS server you get configured is unreachable from the IP you get with the modem?

The DNS server is set to DHCP (method=auto). Trying to ping the DNS server (IP from /etc/resolv.conf) ping -I wwan0 10.114.102.1 does not yield a response. I tried changing the DNS to 8.8.8.8 and service networking restart, but it looks like that does not make a difference as well. To make the prob…

@roman-mazur I tried setting the DNS server inside the docker-compose.yml to 8.8.8.8 and 8.8.4.4, but unfortunately still the same behavior :frowning_face:

Hi @larsjeh ! Just wanted to check with you if you still have this issue. I thought if the problem manifests itself only for particular addresses, maybe it was an intermittent issue on the cellular network provider side, so they could not route your packets properly?

Hi @larsjeh , Most possibly some TCP header parameters that are different in the packets sent from the host OS and the containers are causing the modem to trip. To be able to narrow down the issue a packet capture needs to be run and packets to be checked with wireshark. If you still experience the …

Cannot ping inside container, but can inside Host OS with 4G dongle

Product support

roman-mazur August 30, 2019, 10:01am 10

@larsjeh I think we should exclude the DNS server issues… If you deployed with docker-compose.yml file, you could set a DNS server to 8.8.8.8 for the container as described here:

And then check how it works.

Topic		Replies	Views
Ping to www.google.com times out in balena dashboard. Is there a way to enable this Product support	4	1141	October 8, 2019
Curl an IP address on the local network Product support network	11	2150	April 1, 2021
Raspberry Pi 3 and additional network dongle Product support	10	6432	March 4, 2017
WiFi-connect installation in Raspberry Pi Docker container Project help	62	5585	January 21, 2021
Accessing static assigned host eth0 from inside a container balenaOS	3	616	June 19, 2020

Cannot ping inside container, but can inside Host OS with 4G dongle

Related topics