The NM failure reported earlier appears to have been caused by a
firmware crash for ipw2200 driver. This driver is still subject to
random crashes. This is an active bug. The firmware restart usually
slows NM down or makes it fail. I have been able to make several
successful wireless connection
On Thu, 27 Jan 2005, Bill Moss wrote:
> Note that the essid and key have been set but no MAC address has been
> set for the AP. This is where the problem lies.
Bill,
We don't set the MAC address of the AP on the card itself, the address you
see there comes from the card's firmware and is valid
The changes made this afternoon have made NM fail to make a wireless
connection. syslog shows an attempt to make an Open System connection,
which would normally be successful. Then an attempt is make to make a
Shared Key connection. No connection is made. After stoping NM and
NMInfo, iwconfig e
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): wai
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
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 (ath0/wirele
Hello!
i have problems using networkmanager with my atheros based wireless card
(built in wlan in ibm thinkpad t41).
the madwifi drivers seem to work, but networkmanager does not get a
connection:
iwconfig reports:
ath0 IEEE 802.11g ESSID:"ESSID" Nickname:"NICK"
Mode:Managed
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, 27 Jan 2005 16:31:56 +0100, Tomislav Vujec wrote:
> This is not a huge time server, but it is definitely something worth
^^
I obviously wanted to say time saver here :-)
Tomislav
___
NetworkManager-list mailing li
> Colin Walters and I have talked about a configurable server that you
> could "ping" (like some internal server that you can't get to from
> outside) that would identify whether or not you're on the company LAN.
> Other than that, we could do something based on DHCP reply (ie if you're
> given an
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
P
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 requirem
On Tue, 2005-01-25 at 18:24 +, D. D. Brierton wrote:
> waiting for upstream improvements in the orinoco driver. I just wanted
> to know if I could help out (no I'm not a developer so I can't help with
> programming).
Darren,
Great to hear you're interested... One thing you _could_ do is to g
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
14 matches
Mail list logo
