provision.sh skipped network installation when executed in a private network behind organizational Proxy server

I tried "vagrant up" and "vagrant provision" in a private network of my work, which is connected to the Internet only via HTTP proxy server. I found a message "No external network available. Package installation and maintenance skipped". Reading the provision/provision.sh code told me that it tries to ping public DNS servers to check external network connectivity. In my private network with proxy, ping command can reach none of the public DNS servers, it mistakenly find No network connectivity available even though HTTP messages can come and go. I think the connectivity test should be more robust. It thing one idea could be pinging IP of the platform's default gateway. Pinging the default gateway wil save the case where the platform is behind the Proxy.
I haven't tested it yet, but this block appears to report a connection every time provisioning is run, even if both other checks failed. What's the issue with Windows CJK users?