Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Clone Wireless ath driver?

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    11 Posts 3 Posters 4.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      littlejohn
      last edited by

      Hi there,

      Hope it works for you, I managed to do this with a D-Link DWA-556 (atheros based). One interface is called ath0, and the other one ath0_wlan1

      I then followed the sticky post on bridging wireless with lan and just had to set the mode to "access point" on both devices for it to work. Followed the sticky twice and was up and running!

      Only major issue so far ()with the driver itself was ath_rx_proc: no mbuf! This is fixed by increasing kern.ipc.nmbclusters from 0 to 65536 in /boot/loader.conf (see http://forum.pfsense.org/index.php?topic=27258.msg141959#msg141959 ).

      Regards,
      John

      1 Reply Last reply Reply Quote 0
      • J
        jlepthien
        last edited by

        Yeah. My first card is called ath0_wlan0 and if I add an interface OPTX I can actually choose a ath0_wlan1 interface. But upon saving this the at0_wlan1 gets overridden to an internal interface vr2. I cannot even assign my second WLAN interface :(

        | apple fanboy | music lover | network and security specialist | in love with cisco systems |

        1 Reply Last reply Reply Quote 0
        • L
          littlejohn
          last edited by

          If that's any help, my setup is working with 2.0-BETA4 (amd64) built on Sat Nov 20 08:25:10 UTC 2010.

          Just checked, the parent interface is called ath0, the cloned one is called ath0_wlan1. Hope you get it sorted, might be a bug…

          Regards,
          John

          1 Reply Last reply Reply Quote 0
          • J
            jlepthien
            last edited by

            I hope so, too…

            I just saw that my box reboots upon assigning and saving the new interface ath0_wlan1 and then jumps back to vr2. Anybody has got the same problem? I am on newest NanoBSD snap...

            | apple fanboy | music lover | network and security specialist | in love with cisco systems |

            1 Reply Last reply Reply Quote 0
            • J
              jlepthien
              last edited by

              Here is what happens on console if I try to add that interface:

              Fatal trap 12: page fault while in kernel mode
              cpuid = 0; apic id = 00
              fault virtual address  = 0xc38dc008
              fault code              = supervisor read, page not present
              instruction pointer    = 0x20:0xc09f1f6b
              stack pointer          = 0x28:0xe2e24bf4
              frame pointer          = 0x28:0xe2e24c10
              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 (ath0 taskq)
              trap number            = 12
              panic: page fault
              cpuid = 0
              Uptime: 3h42m31s
              Cannot dump. Device not defined or unavailable.
              Automatic reboot in 15 seconds - press a key on the console to abort

              | apple fanboy | music lover | network and security specialist | in love with cisco systems |

              1 Reply Last reply Reply Quote 0
              • J
                jlepthien
                last edited by

                Is this an open bug? Or how can I add a ticket and where? Is everbody able to open tickets? Thanks…

                | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                1 Reply Last reply Reply Quote 0
                • J
                  jlepthien
                  last edited by

                  Okay I just opened a ticket for that. http://redmine.pfsense.org/issues/1048

                  Please tell me if that is correct or if I have to do anything different when opening a ticket. Thanks…

                  | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    That's a driver issue we can't do anything about, most cards work, at least one specific chipset will just panic. Needs to be reported upstream.

                    1 Reply Last reply Reply Quote 0
                    • J
                      jlepthien
                      last edited by

                      Works with snap starting from 12/5 now…

                      Could it be that I was right when I said that this seemed to be the same problem as in this http://forum.pfsense.org/index.php/topic,29839.0.html thread? Now the problems there seem to be gone as well...

                      | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        huh, yeah it's possible that triggered the other issue, was panicing in ath but that doesn't necessarily mean anything.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.