I'm completely lost. I said it should work as much as a regular device does. I suggested the hardware always come up in software mode. And then, the driver fakes as if it is doing the inet6 stuff at the moment, whereas it is already done. So that the upper level network stack needs nothing different.
Done right, this would require *NO* driver documentation. Which people won't discover. So there's a diff, which I can't test because my specific provider here doesn't actually do inet6. Have to trust others. But driver diff either provides transparent behaviour, or it behaves as described in this manaual page chunk in which case it isn't transparent. I don't know which. Gerhard Roth <gerhard_r...@genua.de> wrote: > On 4/30/20 4:03 PM, Theo de Raadt wrote: > > Is that still the true behaviour? I think it isn't, the "before up" > > aspect is gone isn't it? > > That's right for IP configuration via MBIM and I deleted the "before > up" from the first sentence. > > But wasn't sure for the SLAAC case. Will autoconf work if I set the > flag after the interface is up? Should I delete the "before up" here, > too? > > Gerhard > > > > > > > +.Pp > > +To use IPv6, configure a link-local address. > > +If the device is able to connect to the ISP's network but doesn't > > +show an IPv6 address, setting the > > +.Sy AUTOCONF6 > > +flag on the interface before bringing it up may help. > > +.Ed > > >
