(not necessarily needed in the "GUI"; I would be happy if I could do it editing a text file and including that in the configuraton)
Reason: ChromeOS is using Android applications for VPN applications taht are not included in the standard ChromeOS (basically anything interesting, even Wireguard is not enabled in most Chrome-device specific kernels).
(Reasonably current) ChromeOS is turning the device into a collection of virtual machines (one of them running the Nebula app itself...) which results the system showing up with a bunch of reported addresses which are completely useless, especially if the device is inside some carrier-grade NATbehind-NAT-behind-NAT setup. It would be good to be able to suppress all of these reported addresses on the client (and keeping in mind that the client will never know about the device's real network addresses at all).
congzhangzh
commented
2 years ago
(not necessarily needed in the "GUI"; I would be happy if I could do it editing a text file and including that in the configuraton)
Reason: ChromeOS is using Android applications for VPN applications taht are not included in the standard ChromeOS (basically anything interesting, even Wireguard is not enabled in most Chrome-device specific kernels).
(Reasonably current) ChromeOS is turning the device into a collection of virtual machines (one of them running the Nebula app itself...) which results the system showing up with a bunch of reported addresses which are completely useless, especially if the device is inside some carrier-grade NATbehind-NAT-behind-NAT setup. It would be good to be able to suppress all of these reported addresses on the client (and keeping in mind that the client will never know about the device's real network addresses at all).