@goetz @claushc @nygren it's n so much a threat model as a feature request.

I want a separate network I can control. Machine B is an AP where all my things are connected; the ISP's router's WiFi works as a guest network.

One of the reasons is that, if the ISP goes down, which has happened, I can connect my phone to B, enable tethering, change some stuff, and then my whole network uses that as internet connection. It is helpful in general, but also critical for work.

Replying to @mdione@en.osm.town

@goetz @claushc @nygren OK, it gives a /64 on IPv6 too, so there's that:

```
10: enxdabcc89a8a06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether da:bc:c8:9a:8a:06 brd ff:ff:ff:ff:ff:ff
inet 192.168.61.136/24 brd 192.168.61.255 scope global dynamic noprefixroute [...]
valid_lft 3593sec preferred_lft 3593sec
inet6 fe80::93a9:f7b8:8d95:e02e/64 scope link noprefixroute
valid_lft forever preferred_lft forever
```

Replying to @mdione@en.osm.town

@mdione @goetz @claushc The fe80:: address is just Link Local so won't give you any useful connectivity -- it just exists by default for all links,

For your use-case of wanting local connectivity for when the internet is down, having ULA IPv6 can be useful. One way to do that is to configure your router to announce a ULA /64 prefix (per VLAN) via RAs and then devices should pick an address from it via SLAAC.