Two atheros cards, can't configure second one.



  • I've got an ALIX 3D3 with two CM9 cards.

    The first one (ath0) is my WAN port and is configured and connected fine.

    I'm trying to use the second one as an AP on OPT1, but the configuration won't let me set the Standard (drop-down is empty) or the Channel (drop-down only contains auto).

    Using pfSense-2.0-BETA1-512mb-20100106-1014-nanobsd.



  • Sounds like a bug from the changes needed to support FreeBSD 8's wireless.
    http://redmine.pfsense.org/issues/show/308



  • Thanks for the update.

    I'll try and remember to keep an eye on the issue and try it again when a fix goes in.

    Feel free to contact me if you need anyone to do some testing.



  • Try snapshots newer than this post.



  • I've tried pfSense-2.0-BETA1-512mb-20100125-2206-nanobsd.img.gz, but it still won't let me configure the second interface.

    Sorry for the delay - had a few other jobs to do first ;)



  • The snapshot you tried was older than ermal's post, not newer.

    For some days the snapshot builder seems to have had trouble completing builds.



  • So it is - well spotted. I grabbed it a couple of days after the message!

    I'll try again :)



  • I've tried it again using pfSense-2.0-BETA1-512mb-20100203-1933-nanobsd.img.gz.

    I can now configure the second interface, but I got the following thrown when I applied the changes (after posting the settings without problems).

    Fatal trap 12: page fault while in kernel mode
    fault virtual address  = 0xffff
    fault code              = supervisor read, page not present
    instruction pointer    = 0x20:0xc092cba2
    stack pointer          = 0x28:0xc23f8bb4
    frame pointer          = 0x28:0xc23f8bbc
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process        = 0 (ath1 taskq)



  • This seems to be "permanent" - after a cold reboot I get:

    Fatal trap 12: page fault while in kernel mode
    fault virtual address  = 0xffff
    fault code              = supervisor read, page not present
    instruction pointer    = 0x20:0xc092cba2
    stack pointer          = 0x28:0xc23f8bb4
    frame pointer          = 0x28:0xc23f8bbc
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process        = 0 (ath1 taskq)



  • Is that with two Atheros cards? How do you have it setup (if you can, email me a backup of your config, cmb at pfsense dot org).



  • keylevel:  If you're still watching this thread, what is the current status of this issue?



  • Not sure, as I've not had time to try any snapshots recently.



  • I've seen similar kind of crashes on "apply all changes" to interfaces supported by the rum driver. But I've been able to reproduce the crashes only if the interface is in adhoc or "Access Point". (See http://forum.pfsense.org/index.php/topic,23106.0.html ).

    What interface modes are you using?



  • One of them was configured as an AP.



  • @keylevel:

    One of them was configured as an AP.

    And the other interface is configured in Infrastructure mode?

    If so, how about configuring both wireless interfaces as Infrastructure to see what happens? This will be at least a little bit inconvenient if the system is crashing on startup. You will probably have to temporarily remove one of the wireless NICs, the startup will notice the configuration is different and will prompt you on the console to re-identify the LAN and WAN interfaces and you can leave the wireless interfaces unassigned. Then you could shutdown and reinstall the wireless interface and reboot.

    A weeks ago I was looking into a crash on startup or enabling a wireless interface. It was quite annoying because the crash would usually cause a file system problem and corrupt the configuration file. But that was with the "full" version of pfSense. I hope the nanobsd version is more robust.


Log in to reply