On Mon, Nov 14 2022, Kirill Miazine <[email protected]> wrote: > The most recent snapshot gives non-recoverable failure in name > resolution upon boot starting with configuration which I had not > touched: > > starting network > route: fe80::: non-recoverable failure in name resolution > route: fec0::: non-recoverable failure in name resolution > route: ::ffff:0.0.0.0: non-recoverable failure in name resolution > route: 2002:e000::: non-recoverable failure in name resolution > route: 2002:7f00::: non-recoverable failure in name resolution > route: 2002:0000::: non-recoverable failure in name resolution > route: 2002:ff00::: non-recoverable failure in name resolution > route: ff01::: non-recoverable failure in name resolution > route: ff02::: non-recoverable failure in name resolution > route: ::0.0.0.0: non-recoverable failure in name resolution > > Then it goes to my own config, where I try to set IPv6 gateway to > fe80::1%vio0 and configure some WireGuard peers reachable via IPv6: > > route: fe80::1%vio0: non-recoverable failure in name resolution > ifconfig: non-recoverable failure in name resolution > ifconfig: non-recoverable failure in name resolution > ifconfig: non-recoverable failure in name resolution > ifconfig: non-recoverable failure in name resolution > ifconfig: non-recoverable failure in name resolution > > This is on OpenBSD 7.2-current (GENERIC.MP) #833: Mon Nov 14 11:25:32 MST > 2022.
This seems to be caused by a diff in snaps. I hit similar errors to yours (no wireguard involved, just IPv6 literals) and I had to rebuild libc, ifconfig and route from source to get IPv6 working. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
