As a workaround, since the connectivity check feature is already available, just not activated by default, you may wish to activate it with what will likely be the additional configuration we will ship. To do this, you can add the following lines to /etc/NetworkManager/NetworkManager.conf
This changes the behavior of NM to use a different "connected" state when the checks fail, so the exact behavior of applications may change (and will need to be tested). At least, this currently appears to work properly on my computer; pending further testing once my portal session expires.
As a workaround, since the connectivity check feature is already available, just not activated by default, you may wish to activate it with what will likely be the additional configuration we will ship. To do this, you can add the following lines to /etc/NetworkMan ager/NetworkMan ager.conf
[connectivity] start.ubuntu. com/connectivit y-check. html
uri=http://
interval=300
response=<!DOCTYPE HTML PUBLIC
This changes the behavior of NM to use a different "connected" state when the checks fail, so the exact behavior of applications may change (and will need to be tested). At least, this currently appears to work properly on my computer; pending further testing once my portal session expires.