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

    pfSense as wireless AP transmit power adjustments?

    Scheduled Pinned Locked Moved Wireless
    45 Posts 4 Posters 8.6k Views 4 Watching
    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.
    • provelsP Offline
      provels @JonathanLee
      last edited by

      @JonathanLee Weird, but whatever works. With ng I get a -40db signal, with na I get -70.

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 0
      • stephenw10S Online
        stephenw10 Netgate Administrator
        last edited by

        5Ghz is more easily attenuated by anything.

        1 Reply Last reply Reply Quote 2
        • JonathanLeeJ Offline
          JonathanLee @johnpoz
          last edited by

          @johnpoz
          It is the same upstream.

          https://github.com/freebsd/freebsd-src/pull/880

          https://redmine.pfsense.org/issues/14925

          Make sure to upvote

          provelsP 1 Reply Last reply Reply Quote 0
          • provelsP Offline
            provels @JonathanLee
            last edited by provels

            @JonathanLee Is this the Compex or the Apple card? I have the Compex and my txpower was set at 30 by pfSense. Also, the "txpower 40" argument seems to have no effect, stays at 30 for me.
            Maybe that's because you're using na and not ng. EDIT - Yeah, that's it.

            [23.05.1-RELEASE][root@fw.workgroup]/root: ifconfig ath0_wlan0 txpower 40
            [23.05.1-RELEASE][root@fw.workgroup]/root: ifconfig ath0_wlan0
            ath0_wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
                    description: ATH0_WLE200
                    ether 04:f0:21:4f:6e:e3
                    inet6 fe80::6f0:21ff:fe4f:6ee3%ath0_wlan0 prefixlen 64 scopeid 0x9
                    groups: wlan
                    ssid WIFI_LAN_nomap channel 11 (2462 MHz 11g ht/20) bssid 04:f0:21:4f:6e:e3
                    regdomain FCC country US indoor ecm authmode WPA2/802.11i
                    privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit
            =>        txpower 30 scanvalid 60 pureg protmode OFF ampdulimit 64k
                    ampdudensity 8 shortgi puren -ldpc -uapsd wme burst -apbridge
                    dtimperiod 1 -dfs
                    parent interface: ath0
                    media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap>
                    status: running
                    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
            
            
            

            Peder

            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

            JonathanLeeJ 1 Reply Last reply Reply Quote 1
            • JonathanLeeJ Offline
              JonathanLee @provels
              last edited by

              @provels

              @provels Take a look at this file with the built in editor in pfsense GUI

              Screenshot 2023-10-31 at 7.49.01 AM.png

              This may have blocked you from turning it up. It might be limited by way of this file. . .

              Scroll down and find WiFi 11g and check for something called max power

              Make sure to upvote

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