Connection issues no network no fully propgated

[axet]

Hello!

When i2pd ran on network with wan dhcp and network not ready for 5 minutes (due to dhcp initialization) i2pd will fail to connect even after wan interface fully initialized.

Could be due to security issues and how i2p works with network interfaces.

This is how 7070 port looks like:

i2pd webconsole
[Main page](http://10.10.5.1:7070/)

[Router commands](http://10.10.5.1:7070/?page=commands)
[Local Destinations](http://10.10.5.1:7070/?page=local_destinations)
[Tunnels](http://10.10.5.1:7070/?page=tunnels)
[Transit Tunnels](http://10.10.5.1:7070/?page=transit_tunnels)
[Transports](http://10.10.5.1:7070/?page=transports)
[I2P tunnels](http://10.10.5.1:7070/?page=i2p_tunnels)
Uptime: 9 hours, 34 minutes, 59 seconds
Network status: Unknown
Tunnel creation success rate: 10%
Received: 0.00 KiB (0.00 KiB/s)
Sent: 0.00 KiB (0.00 KiB/s)
Transit: 0.00 KiB (0.00 KiB/s)
Data path: /var/lib/i2pd
Hidden content. Press on text to see.
Routers: 1 Floodfills: 0 LeaseSets: 0
Client Tunnels: 2 Transit Tunnels: 0

Services HTTP Proxy	Enabled
SOCKS Proxy	Enabled
BOB	Disabled
SAM	Disabled
I2CP	Disabled
I2PControl	Disabled

with logread:

Sun Apr 19 04:38:53 2026 daemon.info i2pd[2514]: 04:38:53@830/error - Tunnels: Can't create inbound tunnel, no peers available
Sun Apr 19 04:38:53 2026 daemon.info i2pd[2514]: 04:38:53@830/info - Tunnels: Can't select first hop for a tunnel. Trying already connected
Sun Apr 19 04:38:53 2026 daemon.info i2pd[2514]: 04:38:53@830/error - Tunnels: Can't select next hop for L7pQcx~wH-5ZOFN5BbqLsH6Jw2sh2~8ivlBQXCVslfM=
Sun Apr 19 04:38:53 2026 daemon.info i2pd[2514]: 04:38:53@830/error - Tunnels: Can't create inbound tunnel, no peers available
Sun Apr 19 04:38:54 2026 daemon.info i2pd[2514]: 04:38:54@264/info - NetDbReq: Exploring new 9 routers ...
...
Sun Apr 19 04:39:23 2026 daemon.info i2pd[2514]: 04:39:23@830/warn - Tunnel: Can't find any router, skip creating tunnel
Sun Apr 19 04:39:23 2026 daemon.info i2pd[2514]: 04:39:23@830/info - Tunnels: Can't select first hop for a tunnel. Trying already connected
Sun Apr 19 04:39:23 2026 daemon.info i2pd[2514]: 04:39:23@830/error - Tunnels: Can't select next hop for L7pQcx~wH-5ZOFN5BbqLsH6Jw2sh2~8ivlBQXCVslfM=
...
Sun Apr 19 04:40:07 2026 daemon.info i2pd[2514]: 04:40:07@264/info - NetDbReq: Exploring new 9 routers ...
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@830/warn - Tunnel: Can't find any router, skip creating tunnel
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@830/info - Tunnels: Can't select first hop for a tunnel. Trying already connected
...
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@830/error - Tunnels: Can't select next hop for L7pQcx~wH-5ZOFN5BbqLsH6Jw2sh2~8ivlBQXCVslfM=
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@830/error - Tunnels: Can't create inbound tunnel, no peers available
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@379/info - Transports: Started peer test IPv4
Sun Apr 19 04:40:08 2026 daemon.info i2pd[2514]: 04:40:08@379/warn - Transports: Can't find routers for peer test IPv4

Infinite loop. Even after my 'wan' interface fully initialized:

root@OpenWrt:~# ip a s wan
3: wan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 1:1:1:1:1:1 brd ff:ff:ff:ff:ff:ff
    inet 100.100.26.159/16 brd 100.100.255.255 scope global wan
       valid_lft forever preferred_lft forever
    inet6 2a00:1:1:1:1:1:1:1/64 scope global dynamic noprefixroute 
       valid_lft 1055sec preferred_lft 1055sec
    inet6 fe80::180f:39ff:fe49:3745/64 scope link 
       valid_lft forever preferred_lft forever

Looks like i2pd, read interfaces, and didn't re read them after initialzied for security reasons.

i2pd --version
i2pd version 2.58.0 (0.9.67)
Boost version 1.89.0
OpenSSL 3.5.5 27 Jan 2026

If I restart it manually it start work properly.

[orignal]

Routers: 1

That's the reason

[axet]

Why when as soon as I restart i2pd it works properly? Or if dhcpd get IP instantly it also works just fine.

[orignal]

It reseeds again once you restart.

[axet]

Is it a bug?

[orignal]

No. How it should work properly in your opinion?

[axet]

It should automatically reannonce when interfaces has changed.

[axet]

Or auto reannonce when here is no routers for a 5 minutes.

[axet]

Imagine if I had two private networks without internet, router connected to the first one. It propogated but do not see second network. I disconnect the cable and connect to the second network - i2pd sees nothing. No new routers, no old routers. Then I connect it to the internet - it sees nothing again. I assume i2p need to reannounce eveytime i reconnect or based on lack of active connections for 5 minutes (timeout).