Posts:
23
Registered:
Dec 4, 2005
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 8, 2007 6:47 PM
in response to: mreckhof
|
|
|
Ok, here goes.
First, to anyone else reading the thread, the switch on the first command "./airport -I" a dash-capital-eye, not a one or an el. The forums obscure the character a bit. Lower case eye is a different switch, one and el just bring a complaint that you've entered something it doesn't understand.
I'm at home now, so I'm trying to attach to a different network, with the same problems. I don't know what the info would have shown at work-- if it thought I was attached or not. That said:
504Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -I
agrCtlRSSI: 0
agrExtRSSI: 0
agrCtlNoise: 0
agrExtNoise: 0
state: init
op mode:
lastTxRate: 0
maxRate: 0
lastAssocStatus: 65535
802.11 auth: open
link auth: unknown
BSSID: 0:0:0:0:0:0
SSID:
MCS: -1
channel: 1
505Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -z
506Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -s
SSID BSSID RSSI CHANNEL SECURITY (auth/unicast/group)
Zenyatta' Network 00:11:24:96:63:c7 -61 11 WEP
clayton 00:14:6c:d1:5d:5a -90 6 WPA(PSK/TKIP/TKIP)
coalescence 00:12:17:b9:d1:dc -88 6 NONE
2WIRE261 00:d0:9e:f4:b4:89 -90 4 WEP
2WIRE326 00:14:95:74:9e:21 -50 6 WEP
507Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -A
Network Name (SSID): Zenyatta' Network
password:
508Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -I
agrCtlRSSI: -63
agrExtRSSI: 0
agrCtlNoise: -98
agrExtNoise: 0
state: running
op mode: station
lastTxRate: 54
maxRate: 54
lastAssocStatus: 0
802.11 auth: shared
link auth: unknown
BSSID: 0:11:24:96:63:c7
SSID: Zenyatta' Network
MCS: -1
channel: 11
509Outlandos:/System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources gbest$ ./airport -I
agrCtlRSSI: -66
agrExtRSSI: 0
agrCtlNoise: -96
agrExtNoise: 0
state: running
op mode: station
lastTxRate: 54
maxRate: 54
lastAssocStatus: 0
802.11 auth: shared
link auth: unknown
BSSID: 0:11:24:96:63:c7
SSID: Zenyatta' Network
MCS: -1
channel: 11
No console messages at any time during that run. The command line thinks I'm connected, apparently, but I have no networking through the airport, the menu item still shows powered off (and gives the same console message when I attempt to power on), as does Network Preferences with this message:
12/8/07 6:44:58 PM System Preferences1279 Error: airportd MIG failed = -1 ((null)) (port = 60367)
Since the Airport is responsive from the command line, it's almost at though the hardware has fallen out of sync with the GUI and higher level services...
G4 Powerbook
Mac OS X (10.5.1)
|
|
Posts:
23
Registered:
Dec 4, 2005
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 8, 2007 6:53 PM
in response to: mreckhof
|
|
|
Any idea what "updateprefs" does in that same framework? Doesn't seem to want to give any command line help-- console says "must be root to run" and complains it's not running from launchd.
It sounds vaguely appropriate to what I need to do, but figured I'd ask before trying it.
Dual 2GHz G5
Mac OS X (10.5.1)
|
|
Posts:
692
Registered:
Nov 23, 2007
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 9, 2007 2:34 AM
in response to: AnalogKid
|
|
|
No clue... but then again, I didn't know what airport did either until I tried it.
From the looks of those results, it appears to have taken your password and joined you up to the AP.
Let's try to now bring up IP manually as well.
Err:Resources eb$ sudo ifconfig en1 up
Err:Resources eb$ sudo ifconfig en1 192.168.15.33 netmask 255.255.255.0
Err:Resources eb$ sudo route add default 192.168.15.1
Replace the IPs with whatever is valid for your environment.
Mac OS X (10.5.1)
|
|
Posts:
23
Registered:
Dec 4, 2005
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 10, 2007 1:16 AM
in response to: mreckhof
|
|
|
Well now, that's interesting:
"ifconfig: interface en1 does not exist"
'sudo ifconfig en1 create' came back with an invalid argument response. Of course the man page says nothing you do with ifconfig is permanent anyway, and to stick with Network Preferences.
FWIW, I tried redoing the 10.5.1 update but no luck...
Message was edited by: AnalogKid
G4 powerbook
Mac OS X (10.5.1)
|
|
Posts:
23
Registered:
Dec 4, 2005
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 12, 2007 9:53 PM
in response to: AnalogKid
|
|
|
mreckhof, Topher-- thanks again for walking me through this as much as you did. I learned alot in the process.
I do have it fixed now. I finally just restored the /Library/Preferences/SystemConfiguration directory from TimeMachine. Having tracked it down to the missing en1, I think NetworkInterfaces.plist was fouled up. I tried modifying it by hand once or twice, but couldn't get anything to take. Finally I just pulled the whole set of files up from backup and rebooted.
Looking back, I think what caused my problem was putting the Powerbook into target disk mode and using it to boot a downed Xserve. When I looked into that plist file and saw an en2 configured as a second ethernet port, that was kind of a clue...
So: while it's cool that you can boot an Xserve from your laptop drive, Leopard doesn't completely clean up after itself...
Also: TimeMachine is a godsend.
G4 Powerbook
Mac OS X (10.5.1)
|
|
Posts:
692
Registered:
Nov 23, 2007
|
|
|
|
Re: Airport Will Not Start
Posted:
Dec 14, 2007 9:05 PM
in response to: AnalogKid
|
|
|
Ahh! I bet the XServ uses a diff nic type (i would hope so - something high performance) so it may have added an entry for its own nic bumping everything up by 1 so it got en0.
When you rebooted, guess things didn't go back the other way, so your en1 may have been en2.
Great info - Thanks!
Mac OS X (10.5.1)
|
|
Posts:
8
Registered:
Nov 23, 2004
|
|
|
|
Re: Airport Will Not Start
Posted:
Feb 4, 2008 2:27 PM
in response to: mreckhof
|
|
|
I had the same problem, with the same errors turning up in the System Console (the ACInterfaceGetPowerPreference() invalid interface ones).
I still don't know what caused the problem, and it was very hard to find an answer. However, this thread pointed me in the right direction - the NetworkPreferences.plist and/or com.apple.airportPreferences.plist files which sit in /Library/Preferences/SystemConfiguration were borked (not due to any XServe connection, as far as I know). It looked like a bogus entry had appeared in en1, making it look like I had two Airport cards... I have no idea where that came from.
Anyway, the simplest way I solved it was to delete these two files — OS X recreates them on restart. Now my Airport has come back!
Thanks.
Mac OS X (10.5.1)
|
|
Posts:
5
Registered:
Aug 31, 2006
|
|
|
|
Re: Airport Will Not Start
Posted:
Feb 8, 2008 3:19 PM
in response to: Michael Norris
|
|
|
I'm also seen the same problem, with the same source as the original person. That is, I am booting my MacBook Pro using a different system (in my case a Mac Pro) in target mode as the source disk. It's booted, wired network works, but wireless doesn't. The Mac Pro has two Ethernet interfaces, of course.
Looks like Leopard is missing some interface sanity checking on boot.
MacBook Pro
Mac OS X (10.5.1)
|
|
Posts:
5
Registered:
Aug 31, 2006
|
|
|
|
Re: Airport Will Not Start
Posted:
Feb 8, 2008 3:46 PM
in response to: bryanwalls
|
|
|
For me, deleting the Airport entry and creating a new one did the trick. I was then able to power on the Airport card and connect to my access point.
MacBook Pro
Mac OS X (10.5.1)
|
|
Posts:
14
From:
rome
Registered:
Feb 27, 2008
|
|
|
|
Re: Airport Will Not Start
Posted:
Mar 18, 2008 3:54 PM
in response to: Mike Zwick
|
|
|
I had the same problem right now, i resolved logging in as another user and activating and deativating airport, when back to my user all was fine!
mac pro 2.8 oct (early 2008)
Mac OS X (10.5.2)
|
|
|
