Wireless died after working since september



  • The wireless has been rock solid since the day I got it working.  The other day the router went down at random and when I restarted it
    the wireless SSID wouldn't show up.  I logged into the webgui to check settings, everything seems fine.  The status screen for the interface
    lists the status as "no carrier" which i believe was no there before… beyond that I am lost.

    I am running pfsense 1.2.3 on this hardware:
    board: ALIX.2D13
    wireless card: DCMA-82 Atheros 6G: 802.11a/b/g High Power mPCI Card

    Here is the out put on the interfaces status screen:

    Here are the settings of the wireless interface:

    Here is the output of ifconfig -a:

    $ ifconfig -a
    vr0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
    options=2808 <vlan_mtu,wol_ucast,wol_magic>ether xx:xx:xx:xx:xx:xx
    inet x.x.x.1 netmask 0xffffff00 broadcast x.x.x.255
    inet6 fe80::20d:b9ff:fe1e:4f90%vr0 prefixlen 64 scopeid 0x1
    media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active
    vr1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether xx:xx:xx:xx:xx:xx
    inet6 fe80::20d:b9ff:fe1e:4f91%vr1 prefixlen 64 scopeid 0x2
    inet y.y.y.102 netmask 0xffffff00 broadcast 255.255.255.255
    media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active
    vr2: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
    options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether xx:xx:xx:xx:xx:xx
    media: Ethernet autoselect (none)
    status: no carrier
    ath0: flags=8903 <up,broadcast,promisc,simplex,multicast>metric 0 mtu 1500
    ether xx:xx:xx:xx:xx:xx
    inet6 fe80::20b:6bff:fe2f:f105%ath0 prefixlen 64 scopeid 0x4
    media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>(autoselect <hostap,turbo>)
    status: no carrier
    ssid mySSID channel 6 (2437 Mhz 11g Turbo)
    authmode OPEN privacy OFF txpower 31.5 scanvalid 60 bgscan
    bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 pureg
    protmode OFF wme burst -apbridge dtimperiod 1
    enc0: flags=0<> metric 0 mtu 1536
    lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
    inet 127.0.0.1 netmask 0xff000000
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
    pfsync0: flags=41 <up,running>metric 0 mtu 1460
    pfsync: syncdev: lo0 syncpeer: 224.0.0.240 maxupd: 128
    pflog0: flags=100 <promisc>metric 0 mtu 33204
    bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
    ether xx:xx:xx:xx:xx:xx
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: vr0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 1 priority 128 path cost 200000
    member: ath0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 4 priority 128 path cost 370370

    If you need any other info let me know.</learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></promisc></up,running></up,loopback,running,multicast></hostap,turbo></hostap></up,broadcast,promisc,simplex,multicast></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></broadcast,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,promisc,simplex,multicast>



  • What happens if you specify a channel instead of using auto?



  • Wow… that actually worked I didn't even think to mess with that.

    It has been on auto since I originally configured it.

    Thanks!


Locked