Description of problem:
It happened to me multiple times that different IM clients or Evolution begin to
connect to their respective network server (IRC server, or IMAP) which is hidden
inside of VPN upon connection to the public Internet with NetworkManager.
However, in that moment VPN connection is not available (and it is not started
on by default, which is another problem), so the programs failed. Especially
wonderful with programs, which have hard time to connect to the network once
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. resume the computer from suspend with some network clients running (IM
program or the email one) which are sensitive to the NetworkManager
2. wait until the NM connection is created
observe failure of the network apps to connect through VPN
no failure, apps still patiently wait until ALL connections are established.
I am quite sure, that this is duplicate of some other bug, but even when I went
manually through all 269 NM bugs, but I haven't found the appropriate bug.
There's really only one NM bug here, which is that NM should restart the
previously active VPN connection on resume.
The other issue is that apps like pidgin and Evolution only listen for network
changes, not for VPN changes. This is actually hard to fix. You could tie a
VPN connection to an email account in Evolution, for example, but then if you're
on a wired connection which has direct access to the mail server and you don't
need VPN, Evo would still say you're disconnected because the VPN wasn't up.
You could say "if I can ping this server then I can get to email" but that
doesn't help for captive portals at coffee shops that intercept and redirect
DNS. So you are left basically with "can I start an IMAP session to this
server", at which point you're already trying to connect...
Even if I fixed the NM issue above, you'll still have the same problem if the
VPN fails to actually connect on resume.
(In reply to comment #1)
> Even if I fixed the NM issue above, you'll still have the same problem if the
> VPN fails to actually connect on resume.
Couldn't NM just try to connect to VPN and if it fails, to say by setting some
bits somewhere "OK, I have a network connection, but it is a dirty one, I
haven't managed to get all connections on"?
(In reply to comment #1)
> The other issue is that apps like pidgin and Evolution only listen for network
> changes, not for VPN changes. This is actually hard to fix. You could tie a
> VPN connection to an email account in Evolution, for example, but then if
> you're on a wired connection which has direct access to the mail server and
> you don't need VPN, Evo would still say you're disconnected because the VPN
> wasn't up.
> You could say "if I can ping this server then I can get to email" but that
> doesn't help for captive portals at coffee shops that intercept and redirect
> DNS. So you are left basically with "can I start an IMAP session to this
> server", at which point you're already trying to connect...
a) ping? Any progress here?
b) doesn't NetworkManager know which connection is used for the particular server? So, it should be able to say to Evolution -- "Connection to server foo is down" when trying to get to the VPN-shielded IMAP server and "Connection is OK" when trying to get to gmail?
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.