Ath0 not detected on Alix 2D13



  • Try tomorrow snapshots please.



  • Yes, will report back tomorrow.

    Just a comment about this process now. We cannot see anything of what is happening to pfSense-tools repo. We are flying blind. Yes, that is the way it is with Microsoft products, we try things and report apparent bugs and some time later a "magic fix" (might) appear. But this is an open source project!

    I used to debug OpenVMS device drivers. I do have some skills and if I could look at what is in pfSense-tools then I could help spot what some of the issues are. Sure, Ermal can do this stuff himself behind the scenes, but IMHO it is useful to have other sets of eyes to help in the debugging process.

    And then people will quickly assume that some security agency is working with ESF to insert "bonus code" into pfSense. Actually I don't think that will be the case, but unless people can see the pfSense mods made to "pf" and other standard FreeBSD components, then they will naturally start to think these things.

    Come on ESF, sort out a way for community members to see the code.



  • This was mostly related to kernel config handling.

    The tools repo issues is being handled slowly but being handled.



  • @phil.davis:

    Just a comment about this process now. We cannot see anything of what is happening to pfSense-tools repo. We are flying blind. Yes, that is the way it is with Microsoft products, we try things and report apparent bugs and some time later a "magic fix" (might) appear. But this is an open source project!

    I used to debug OpenVMS device drivers. I do have some skills and if I could look at what is in pfSense-tools then I could help spot what some of the issues are. Sure, Ermal can do this stuff himself behind the scenes, but IMHO it is useful to have other sets of eyes to help in the debugging process.

    And then people will quickly assume that some security agency is working with ESF to insert "bonus code" into pfSense. Actually I don't think that will be the case, but unless people can see the pfSense mods made to "pf" and other standard FreeBSD components, then they will naturally start to think these things.

    Come on ESF, sort out a way for community members to see the code.

    Phil, these comments distill my concerns exactly, too bad it's buried in this thread (not that these comments make any difference apparently).

    A less nefarious concern than three letter agencies and 'bonus code' is simply documentation.  When a newbie like me say,  tries to dig into a problem using available freebsd documentation, it's very frustrating to find that pfsense contains mods that are not reflected in the docs.  Often pfsense relies on these changes, yet they are undocumented.  I'm thinking of my on-going issues with state killing in 2.1 (pfctl mods) and of course the new tracker numbers.

    I recall a post where someone said in effect ' … if we wanted to close it, we took away the wrong repo', referring to removing the pfsense-tools repo rather than pfsense repo.  Well, IMHO pfsense is effectively closed until the tools repo is available again.



  • Please send this discussion on its own thread not related to this.

    This is about ath0.



  • I will be a couple of days before being able to try this. I am away and something happened at home - the home laptop is not getting out through the setup I left behind so I can't TeamViewer in to it. And OpenVPN client is not working on that pfSense 2.2 box, so it did not make a site-to-site connection out to the intended place, so I can't get back to it over that. Bit hard for the wife to troubleshoot - she is getting internet from a WiFi ADSL device until I get back.



  • Just want to throw it out there, if anyone does get their ath0 wireless N card working, it would be handy to know any steps you did to set it up. I went to test my atheros 5416 chipset card (Dlink DWA-552) and am happy to report it no longer causes a kernel panic. (anything FreeBSD 8 and it's not happy) I set it up as the WAN interface on a test box and it automatically connected itself to an open network, got an IP and appears to have internet. I wasn't able to get it to connect to a secured network however and it didn't look like the rescan option worked as it couldn't find any networks. Haven't had time to investigate why yet.

    This was done on the April 7th snapshot..



  • 2.2-ALPHA (i386)
    built on Wed Apr 9 09:01:59 CDT 2014
    FreeBSD 10.0-STABLE

    Still no "ath0" available in Interfaces->Assign on my Alix 2D13.



  • 2.2-ALPHA (i386)
    built on Sun Apr 13 15:35:58 CDT 2014
    FreeBSD 10.0-STABLE

    ath0 is back on Alix 2D13! Very good. I have set it up in Access Point mode, enabled DHCP and added firewall rules and it is working as expected. I am posting across that now.



  • Hi good morning,

    @phil.davis, have you support to N Wireless?

    Thanks



  • I don't know about that. I think the card in my Alix 2D13 is only b/g



  • I tested an N card and it's not recognised anymore.
    It was recognised in an earlier version.

    Is still shown as:
    none2@pci0:4:0:0: class=0x028000 card=0x3123168c chip=0x0033168c rev=0x01 hdr=0x00
        class      = network



  • Can you tell me which vrsion it was recognized before?

    Its a PCI card and nothing should have changed there afaik.

    I see it even supported by ath AR9300_DEVID_AR9580_PCIE



  • The march 27 version.
    It seems these files aren't on the snapshot server anymore.



  • A March 27th image was the last time I saw if_cdce.ko; I suspect many modules have been missing since then.



  • Those are inside the kernel nowdays.

    And if_cdce iirc is for USB interfaces while this is a PCIe one.
    Judging on the other seeing the ath interface for assignment this is a bit strange happening.

    Though can you try with the next set that will come out?



  • As a test i downloaded the current amd64 memstick serial and booted from this one.
    There the card is detected correctly.

    The version on the sata was upgraded with the autoupgrade function.

    I reinstalled and the card seems to work now.



  • Waiting on feedback for N wireless now :)



  • Well the gui is severely lacking in config options.
    Shorlty what i'm missing most:
    Antenna selection. Since we are working with MIMO devices now there is no more primary/secondary antenna, but all at once.
    Some mechanism to select the active chains is required here.
    Other stuff which is missing selection option:
    HT20/HT40
    LDCP
    RXSTBC1,12,123
    TXSTBC
    short GI 20/40

    Some preliminary tests show that most of it is enabled by default.
    Will test some more tomorrow.



  • Ok did some tests.
    pfSense side:
    PC1 connected to APU with an AR9580 (3x3)
    PC2 side: AR9580 (3x3)

    on 2.4GHz
    40MHz,
    Switching between MCS22 and MCS23
    Switching between short GI on and off

    [  3] 167.0-168.0 sec  34.3 MBytes  288 Mbits/sec  0.043 ms    0/24451 (0%)
    [  3] 168.0-169.0 sec  33.5 MBytes  281 Mbits/sec  0.066 ms    0/23869 (0%)
    [  3] 169.0-170.0 sec  32.4 MBytes  271 Mbits/sec  0.046 ms    0/23076 (0%)
    [  3] 170.0-171.0 sec  33.9 MBytes  284 Mbits/sec  0.044 ms    0/24176 (0%)
    [  3] 171.0-172.0 sec  34.2 MBytes  287 Mbits/sec  0.041 ms    0/24402 (0%)
    [  3] 172.0-173.0 sec  34.5 MBytes  289 Mbits/sec  0.033 ms    0/24612 (0%)
    [  3] 173.0-174.0 sec  34.7 MBytes  291 Mbits/sec  0.051 ms    0/24763 (0%)
    [  3] 174.0-175.0 sec  32.5 MBytes  273 Mbits/sec  0.090 ms    0/23206 (0%)
    [  3] 175.0-176.0 sec  30.8 MBytes  258 Mbits/sec  0.051 ms    1/21953 (0.0046%)
    [  3] 176.0-177.0 sec  29.4 MBytes  247 Mbits/sec  0.044 ms    0/20995 (0%)
    [  3] 177.0-178.0 sec  31.1 MBytes  261 Mbits/sec  0.034 ms    0/22208 (0%)
    [  3] 178.0-179.0 sec  33.8 MBytes  283 Mbits/sec  0.173 ms    0/24107 (0%)
    [  3] 179.0-180.0 sec  32.9 MBytes  276 Mbits/sec  0.155 ms    0/23466 (0%)
    [  3] 180.0-181.0 sec  32.2 MBytes  270 Mbits/sec  0.034 ms    0/22993 (0%)
    [  3] 181.0-182.0 sec  30.6 MBytes  257 Mbits/sec  0.039 ms    0/21830 (0%)
    [  3] 182.0-183.0 sec  35.0 MBytes  294 Mbits/sec  0.134 ms    0/24979 (0%)
    [  3] 183.0-184.0 sec  32.0 MBytes  268 Mbits/sec  0.051 ms    0/22812 (0%)
    [  3] 184.0-185.0 sec  34.6 MBytes  290 Mbits/sec  0.036 ms    0/24650 (0%)
    [  3] 185.0-186.0 sec  34.7 MBytes  291 Mbits/sec  0.034 ms    0/24729 (0%)

    on 5GHz
    40MHz,
    Switching between MCS22 and MCS23
    Switching between short GI on and off

    [  3] 117.0-118.0 sec  34.2 MBytes  287 Mbits/sec  0.057 ms    0/24365 (0%)
    [  3] 118.0-119.0 sec  33.4 MBytes  280 Mbits/sec  0.055 ms    0/23841 (0%)
    [  3] 119.0-120.0 sec  31.6 MBytes  265 Mbits/sec  0.035 ms    0/22567 (0%)
    [  3] 120.0-121.0 sec  35.2 MBytes  296 Mbits/sec  0.055 ms    0/25139 (0%)
    [  3] 121.0-122.0 sec  32.7 MBytes  274 Mbits/sec  0.057 ms    0/23306 (0%)
    [  3] 122.0-123.0 sec  33.8 MBytes  283 Mbits/sec  0.060 ms    0/24087 (0%)
    [  3] 123.0-124.0 sec  30.3 MBytes  254 Mbits/sec  0.115 ms    0/21628 (0%)
    [  3] 124.0-125.0 sec  32.8 MBytes  275 Mbits/sec  0.031 ms    0/23420 (0%)
    [  3] 125.0-126.0 sec  31.8 MBytes  267 Mbits/sec  0.051 ms    0/22673 (0%)
    [  3] 126.0-127.0 sec  34.9 MBytes  293 Mbits/sec  0.039 ms    0/24888 (0%)
    [  3] 127.0-128.0 sec  30.4 MBytes  255 Mbits/sec  0.123 ms    0/21713 (0%)
    [  3] 128.0-129.0 sec  30.1 MBytes  253 Mbits/sec  0.040 ms    0/21477 (0%)
    [  3] 129.0-130.0 sec  31.7 MBytes  266 Mbits/sec  0.073 ms    0/22636 (0%)
    [  3] 130.0-131.0 sec  31.5 MBytes  264 Mbits/sec  0.044 ms    0/22457 (0%)
    [  3] 131.0-132.0 sec  31.3 MBytes  263 Mbits/sec  0.051 ms    0/22348 (0%)
    [  3] 132.0-133.0 sec  34.0 MBytes  285 Mbits/sec  0.048 ms    0/24243 (0%)
    [  3] 133.0-134.0 sec  33.7 MBytes  283 Mbits/sec  0.046 ms    0/24063 (0%)
    [  3] 134.0-135.0 sec  35.9 MBytes  301 Mbits/sec  0.043 ms    0/25585 (0%)
    [  3] 135.0-136.0 sec  35.9 MBytes  302 Mbits/sec  0.046 ms    0/25641 (0%)
    [  3] 136.0-137.0 sec  35.9 MBytes  302 Mbits/sec  0.041 ms    0/25642 (0%)


Log in to reply