On Thu, 20 Jan 2005 09:54:39 -0500, Dan Williams wrote:
In the case of VPN, why do other programs _care_? What good does it do
to advertise VPN connections to other applications at all? Most
applications care about getting to the internet, which a VPN does for
you. In the case of a VPN,
On Thu, 2005-01-27 at 12:24 +0100, Tomislav Vujec wrote:
I think some applications might care, e.g. email client. My usage pattern
looks like this:
1) Connect to the Internet
2) If I am in the company LAN, go to step 4
3) connect to the VPN
4) Sync my email
Now NM removes the requirement on
David Zeuthen released
hal-0.4.7.cvs20050126-1
hal-gnome-0.4.7.cvs20050126-1
hal-devel-0.4.7.cvs20050126-1
last night which fixed for me the net.80203.link bug that I reported to
yesterday bugzilla and to this list since it affected the operation of
NM. Wow, that fix was fast! 8-)
--
Bill Moss
On Tue, 2005-01-25 at 13:53 -0500, Dan Williams wrote:
Great to hear you're interested... One thing you _could_ do is to grab
the upstream Orinoco drivers (orinoco.sf.net) and try to build it, then
use it with NetworkManager and report what seems to be broken.
I'm very happy to do that. By
On Thu, 2005-01-27 at 21:28 +0100, Stefan Zechmeister wrote:
NetworkManager: Activation (ath0) started...
NetworkManager: Activation (ath0/wireless): waiting for an access point.
NetworkManager: Activation (ath0/wireless): waiting for an access point.
NetworkManager: Activation
Dan Williams wrote:
What you need to do to debug this is the following... In a separate
window, run the command watch -n 1 iwconfig ath0 and let that run
while NM is trying to associate with the AP. Look at the MAC address
that the card reports, and if it changes to FF:FF:FF:FF:FF:FF too often
Hi,
On Thu, 27 Jan 2005 15:46:49 -0500, Dan Williams wrote:
On Thu, 2005-01-27 at 21:28 +0100, Stefan Zechmeister wrote:
NetworkManager: Activation (ath0) started... NetworkManager: Activation
(ath0/wireless): waiting for an access point. NetworkManager: Activation
(ath0/wireless): waiting
