search

mharsch / pi_tailscale_modem

Network configuration for deploying pi systems with LTE modems and connecting via tailscale
0 stars 0 forks source link

Rome, GA system. Floodedwith tailscale boostrapDNS errors. #3

Open JacobJoachim opened 2 years ago

JacobJoachim commented 2 years ago

Rome syslog.txt image

Lost connection to Rome, had to restart it physically. Might be a separate issue?

mharsch commented 2 years ago

The bootstrapDNS errors at the beginning of the attached logfile are likely a result of the same root cause as #1 (i.e. only IPv6 is configured for the wwan0 interface).

The first workaround that comes to mind is to limit the wwan0 connection to only IPv4 configuration. When using NetworkManager, this can be done by following the steps described here.

JacobJoachim commented 2 years ago

Should I do this for all systems?

On Thu, Jun 2, 2022 at 8:48 AM Mike Harsch @.***> wrote:

The bootstrapDNS errors at the beginning of the attached logfile are likely a result of the same root cause as #1 https://github.com/mharsch/pi_tailscale_modem/issues/1 (i.e. only IPv6 is configured for the wwan0 interface).

The first workaround that comes to mind is to limit the wwan0 connection to only IPv4 configuration. When using NetworkManager, this can be done by following the steps described here https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/using-networkmanager-to-disable-ipv6-for-a-specific-connection_configuring-and-managing-networking .

— Reply to this email directly, view it on GitHub https://github.com/mharsch/pi_tailscale_modem/issues/3#issuecomment-1144954183, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZLZ5UBH4NIE43VIR7S3QFLVNDCSBANCNFSM5XSQHPFQ . You are receiving this because you authored the thread.Message ID: @.***>

--

Jacob Joachim Process Engineer | Garrison Minerals, LLC M: +1 (832) 443-3479 11901 W 48th Ave. Wheat Ridge, CO 80033

mharsch commented 2 years ago

I would first try it on your test pi to make sure it works as you expect. It seems that some cellular towers are assigning ipv6 addresses and some are not. This could be part of the 5G rollout nationwide, or it could be unrelated. The issue is when our modem gets stuck with only ipv6 address and not an ipv4 address. You can tell from the output of the 'ip address' command which is getting applied: ipv4 addresses are indicated as 'inet' and ipv6 addresses are indicated as 'inet6'. This change should only make a difference for those systems that are showing ipv6 addresses on the wwan0 interface.