Re: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect.

"Edwin L. Culp" <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
Quoting Andrew Thompson <[email protected]>:

> On Thu, Jun 19, 2008 at 06:25:20PM -0500, Edwin L. Culp wrote:
>> Quoting "Paul B. Mahol" <[email protected]>:
>>
>>> Because it looks like you are using CURRENT, first you need to create
>>> wlanX interface:
>>>
>>> ifconfig wlan create wlandev ath0
>>>
>>> Read man page of ath (if you did installed new world) and/or entry in
>>> /usr/src/UPDATING dated 20080420.
>>
>> Sorry I missed that Paul.  Thanks for calling it to my attention.
>>
>> I have tried to follow the instructions in the ath and wlan manual pages
>> and the UPDATING file but my end result hasn't changed - "no carrier".  I'm
>> sure that I am still missing something else.
>>
>> My rc.conf has changed from:
>>>> if_ath_load="yes"
>>>> ifconfig_ath0="DHCP"
>> to
>> #  ath new config
>> wlans_ath0=wlan0
>> ifconfig_wlan0="WPA DHCP"
>>
>> My ifconfig is now:
>>
>> ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>> 	ether 00:1d:d9:27:5c:e5
>> 	media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>> 	status: no carrier
>>
>> wlan0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>                    ^^^^^
>
> For some reason your interface is not UP. The dhcp client should do this
> so make sure its being launched.

Thanks, Andrew.  I haven't used wireless on freebsd since 802.11b on  
maybe 4.? before hostap, etc. etc.  I need to get this running to  
relearn about wifi under freebsd.  Unfortunately, I bought a laptop  
with an unsupported ath card but now that Sam's latest patch brings it  
and with the help from folks on the list I'm getting closer.

You are right, Andrew, dhclient wasn't running so first I tried:
# ifconfig wlan0 up
ath0 then associated:
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
	ether 00:1d:d9:27:5c:e5
	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
	status: associated
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
	inet6 ::1 prefixlen 128
	inet 127.0.0.1 netmask 0xff000000
pfsync0: flags=0<> metric 0 mtu 1460
	syncpeer: 224.0.0.240 maxupd: 128
pflog0: flags=0<> metric 0 mtu 33160
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 00:1d:d9:27:5c:e5
	media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
	status: no carrier
	ssid "" channel 4 (2427 Mhz 11g)
	regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7
	scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
	roam:rate 5 protmode CTS wme burst bintval 0
but still no carrier on wlan0 :(

so I tried

  # dhclient wlan0
wlan0: no link .............. giving up

Trying
# ifconfig wlan0 scan
never finishes at least for the 10 minutes that I have left it.

Just in case anyone wonders, I have an AP about 3 feet from where I'm  
working and an iPhone that finds about a 1/2 dozen on accessable AP's  
so it souldn't be a signal problem although all are using wep for auth.

Anyone else have a suggestion?

Thanks,

ed
>
>> 	ether 00:1d:d9:27:5c:e5
>> 	media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>> 	status: no carrier
>> 	ssid "" channel 1 (2412 Mhz 11b)
>> 	regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7
>> 	scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
>> 	roam:rate 1 wme burst bintval 0
>>
>> Both have "no carrier" and neither will do scan
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "[email protected]"
>

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.