I can confirm this bug! Same thing here, working fine before the last DEV update.

I am seeing the same here, The icon does not appear next to the WiFi icon in the notification panel.

This is the same for me. I can also add that i am unable to manually set up a connection to the VPN. 

The workaround for https://bugs.chromium.org/p/chromium/issues/detail?id=864874 fixed this for me.

Seeing the same here. If this makes it into stable it will impact all of our corp Chrome OS devices.

Seeing the same issue on my pixelbook. This is now a high priority issue for me... I desperately need to use my VPNs on my pixelbook.

Seeing this as well on pixelbook. Please deploy a fix ASAP this impacts work for a lot of people!

I can confirm on: 

Samsung Chromebook Plus 
Chrome Os version: 69.0.3494.0 

Latest version (69.0.3497.14) on Pixelbook...still broken.

Experiencing the same issue using the Private Internet Access app.  What's even more stressing about this is that the vpn client connects and reports the new external address.  Unfortunately, no traffic is actually routed across the vpn connection.

You can solve it by powerwashing and re-setting up your Chromebook. However, there doesn't appear to be a fix yet for those who are already affected without performing a powerwash.

Hope this helps.

I can confirm this bug! Same thing here, working fine before one of the last DEV updates.

OK, UPDATED INFORMATION: After Powerwash VPN ARC works now!

Once my Android VPN connection is established everything is as expected except that the routing is table is wrong.  The priority 1 route takes everything out over the MAIN lookup table, meaning it goes out as usual via WiFi (wlan0).  The ARC route (table 1) is there with a cost of 10, but the traffic never goes there as it's listed as a lower priority.  Powerwashing fixes this for a few days, then it breaks again for no apparent reason.  Happens on multiple login profiles.  Pixelbook on 68 Beta, but it happens on 67 Stable as well.  Been like this for a while now. Makes some of my work impossible to do.

Deleted: Screenshot 2018-08-13 at 18.45.33.png 105 KB

	Screenshot 2018-08-13 at 18.45.33.png 105 KB View Download

Looking around other VPN bugs in ChromeOS, I just spotted this case: https://bugs.chromium.org/p/chromium/issues/detail?id=825641  I knew I had a few preferred Networks set (used to prefer a 5Ghz network when there are multiple valid SSIDs in range).  I removed the preferred network (Settings>Network>WiFi>Known Networks) and reestablished my VPN, and now the routes are correct.  At least I have a workaround now, but that is still unexpected behavior. 

I have same issue on the last DEV vision.
It seems only chrome doesn't use vpn forward, and the VPN label doesn't light on while using vpn

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11578.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3669.0 Safari/537.36
Platform: Platform 11578.0.0 (Official Build) dev-channel eve
Chrome Version 73.0.3669.0 (Official Build) dev (64-bit)

Steps to reproduce
1. Enable #arc-vpn via chrome://flags
2. Start Android VPN client app (tested multiple clients, with multiple protocols, all results the same)
3. Check external IP within ChromeOS browser window (results in ISP ext IP)
4. Check external IP within Android Chrome browser window (results in VPN provider ext IP)
5. Check external IP within Linux container curl request (results in ISP ext IP)

What is the expected behavior?
I expect all host/device traffic to be routed through the VPN client, validated by the verified by external IP for all being VPN providers IP.

Not sure if related issues https://crbug.com/815214 or https://crbug.com/834585 are a better place to post.

Did this work before?
Earlier versions did route ChromeOS traffic as expected. I'm about to powerwash and test on stable to confirm if the issue exists in 71.0.3578.127 (Platform version: 11151.113.0).

Confirming with fresh Platform 11151.113.1 (Official Build) stable-channel eve, ChromeOS browser traffic goes through Android VPN, but not linux container traffic.