I think, I understand, but setting ether to tun has no effect, it just reports:
: Cannot open /dev/sheep_net (No such file or directory). Ethernet will not be available.
Seems to completely ignore the "tun" flag. Setting it to "tap" reports:
: Cannot open /dev/tap (No such file or directory). Ethernet will not be available.
I realize tap is a completely different networking interface from "tun", and it's been deprecated in linux for a long time, or at least is now in the TunTap code. I can still create a Tap0 interface, but it doesn't create it in /dev/tap where the BII code expects it to be,
So it's just my luck lately, four networking options in BII, and none of them will work on my Chromebook.
slirp; crashes BII
sheep_net: hard reset of the Chromebook when BII loads
tun: broken code