Network is unreachable

Software SW help
1

After upgrading to 7.2.0 and rebooting after a while I suddenly lost network connection. Neither wireless nor Ethernet worked. I could not ssh into the router and had to connect via Serial.
The router had internet connectivity though. It seems the interfaces were up but no IPv4 DHCP leases were assigned.
Had to rollback to 7.1.4 snapshot from 2025-03-20 to get a working system. Firmware Version: TurrisOS 7.1.4 4e1d1b7df0ce6fa96d7462dc883917682f428046 / LuCI openwrt-22.03 branch git-24.208.65546-18f3914. schnaps list below.
Seems to be the same issue as described by @lb-2017 here: Turris OS 7.2 is out! - #17 by lb-2017

Automatic updates disabled for now. How to find the cause of this issue?

    # | Type      | Size        | Date                      | Description
------+-----------+-------------+---------------------------+------------------------------------
  282 | single    |   342.18MiB | 2021-12-03 22:10:24 +0100 | User created snapshot
  321 | rollback  |   313.26MiB | 2022-04-08 18:58:47 +0200 | Rollback to snapshot 319
  559 | pre       |    41.17MiB | 2025-01-08 20:23:04 +0100 | Automatic pre-update snapshot (TurrisOS 7.1.3 - hbs)
  560 | post      |    41.10MiB | 2025-01-08 20:23:10 +0100 | Automatic post-update snapshot (TurrisOS 7.1.3 - hbs)
  571 | pre       |    41.25MiB | 2025-03-18 14:31:25 +0100 | Automatic pre-update snapshot (TurrisOS 7.1.3 - hbs)
  572 | post      |    40.93MiB | 2025-03-18 14:31:37 +0100 | Automatic post-update snapshot (TurrisOS 7.1.3 - hbs)
  573 | pre       |    43.21MiB | 2025-03-20 13:52:16 +0100 | Automatic pre-update snapshot (TurrisOS 7.1.3 - hbs)
  574 | post      |   552.00KiB | 2025-03-20 13:52:31 +0100 | Automatic post-update snapshot (TurrisOS 7.1.4 - hbs)
  582 | time      |    47.07MiB | 2025-05-11 01:05:00 +0200 | Snapshot created by cron
  583 | time      |    47.15MiB | 2025-05-18 01:05:01 +0200 | Snapshot created by cron
  584 | time      |    47.13MiB | 2025-05-25 01:05:00 +0200 | Snapshot created by cron
  585 | time      |    47.16MiB | 2025-06-01 01:05:01 +0200 | Snapshot created by cron
  586 | pre       |    40.98MiB | 2025-06-04 15:54:36 +0200 | Automatic pre-update snapshot (TurrisOS 7.1.4 - hbs)
  587 | post      |   516.00KiB | 2025-06-04 15:54:44 +0200 | Automatic post-update snapshot (TurrisOS 7.1.4 - hbs)
  588 | pre       |   528.00KiB | 2025-06-05 13:45:50 +0200 | Automatic pre-update snapshot (TurrisOS 7.1.4 - hbs)
  589 | post      |    40.95MiB | 2025-06-05 13:47:51 +0200 | Automatic post-update snapshot (TurrisOS 7.2.0 - hbs)
  590 | time      |     6.79MiB | 2025-06-08 01:05:01 +0200 | Snapshot created by cron
  591 | rollback  |    47.26MiB | 2025-06-09 14:05:54 +0000 | Rollback to snapshot factory
  592 | rollback  |   720.00KiB | 2025-06-09 14:11:39 +0000 | Rollback to snapshot 590
  593 | rollback  |     6.84MiB | 2025-06-09 20:12:12 +0200 | Rollback to snapshot 588
  594 | rollback  |     6.80MiB | 2025-06-09 20:43:45 +0200 | Rollback to snapshot 587
  595 | rollback  |     6.78MiB | 2025-06-09 20:47:51 +0200 | Rollback to snapshot 574
2

This happened to me twice since 7.2
Never happened before.
Ipv6 was still available to reach the router, and some internet sites.
Reboot fixed.

3

Hello @milos,
What happened in my case seems identical to yours, except I had no IPv4 connection at all after the update to turris 7.2.0. Two IPv6 interfaces come up (as they do under turris 7.1.4), but the IPv4 192.168.1.x interface is lost. I’ve no idea how to get into the router via the IPv6 interfaces. I have tried ssh root@(IPv6-address), but am told ‘…port 22: Connection refused’.
Even if I could get in, I would not know what to edit or run, to raise the IPv4 interface. (I am running Debian 12 on my PC). Can anyone help?
Thanks.

4

There are 3 ways how to debug it:

  1. Serial connection to the router and watching logs
  2. Configuring log persistence and connecting a hard drive
  3. schnapps mount the post-update snapshot and manually check contents of /etc/config for weird things.
5

The same thing happened to me with my Turris v1.1, after updating to version 7.2.0, the DHCP server for IPv4 stopped working. I fixed it restarting dnsmasq service after starting of the router it and it works now.

Before update I added to /etc/rc.local this command /etc/init.d/dnsmasq restart and it is working after update.

2 Likes
6

Well why instead of restarting service just make sure its enabled beforehand?

So /etc/init.d/dnsmasq enable and /etc/init.d/dnsmasq start and there should be no need for hacks in rc.local. And if it still doesnt work then look for the actual problem in the logs.

7

I can confrim the DHCP server issue (the service is enable and it still does not start and provide IPv4 addresses, or maybe does start but does not serve the network interfaces where my clients are). As a workaround, I am using the same hack as @cUBAk (the restart in rc.local). Unfortunatelly, I did not add rc.local into git so do not know the exact date/version when it happened. I am using MOX.

8

Putting the /etc/init.d/dnsmasq restart line into /etc/rc.local worked for me too. Thank you @cUBAk ! But I notice that the IPv4 interface becomes active only 20-30 secs. after the IPv6 interfaces.