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

    Please test wireless in latest snapshots

    1.2.1-RC Snapshot Feedback and Problems-RETIRED
    20
    62
    36.2k
    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.
    • S
      sullrich
      last edited by

      We made some changes to the kernel configuration.  Please retest the latest 1.2.1 snapshots that where just copied up.

      Thanks!!

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

        can i update my embedded or should it be fresh install?

        1 Reply Last reply Reply Quote 0
        • H
          hansru
          last edited by

          Hello,

          Running 1.2.1 snapshot July 24 23.13 running on Alix (full version on Microdrive) is working now with Wireless. Previous versions of 1.2.1 did not work with WiFi,

          regards,
          Hans

          1 Reply Last reply Reply Quote 0
          • D
            DeCex
            last edited by

            Upgraded this morning to this version: pfSense-Full-Update-1.2.1-TESTING-SNAPSHOT-20080724-2313

            Still no go for wireless client. It say connected fine but cant access internet though pfSense. I post some screenshot to explain some.

            system.jpg
            system.jpg_thumb
            opt1.jpg
            opt1.jpg_thumb
            interface.jpg
            interface.jpg_thumb
            wireless_status.jpg
            wireless_status.jpg_thumb

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

              seems to fire up ok using an atheros card and do some basic browsing, but

              pfsense:~#  athstats
              /libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by "athstats"

              also straight after rebooting managed to get the dreaded

              ath0: stuck beacon; resetting (bmiss count 4)
              ath0: stuck beacon; resetting (bmiss count 4)
              ath0: stuck beacon; resetting (bmiss count 4)
              ath0: stuck beacon; resetting (bmiss count 4)

              and

              ath0: ath_chan_set: unable to reset channel 6 (2437 Mhz, flags 0x490 hal flags 0x150)

              more testing todo and findling with settings

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

                Running the snapshot built "Fri Jul 25 13:43:33 EDT 2008". Wireless doesn't work when bridged with LAN. However, it does work if setup on it's own subnet.

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

                  Did some testing, not sure if anyone found this before. Anyway…

                  After bridging the Wireless with the LAN, the following is appears when running dmesg:

                  bridge0: invalid MTU for re0

                  I checked the bridge0 interface, and it had an MTU of 2290, just like ath0. Obviosly that MTU is invalid for a standard ethernet NIC, thus it refuses to join bridge.

                  From there, I attempted to set ath0 (Wireless) MTU via pfSense webConfigurator, but the MTU setting was ignored. So, I manually set it via the shell. However, bridge0 still had an MTU of 2290 after changing ath0's MTU.

                  Finally, I decided to manually destroy bridge0, and recreate it. Now, that I had ath0 set with an MTU of 1500, both ath0 and re0 would have the same MTU.

                  ifconfig bridge0 destroy
                  ifconfig bridge create
                  ifconfig bridge0 addm ath0 addm re0 up

                  After recreating the bridge with both devices having an MTU of 1500, the bridge worked properly. The only left was to create a firewall rule to allow traffic in on the Wireless interface, which I did via the webConfigurator.

                  Hopefully the above is of use to somebody.

                  1 Reply Last reply Reply Quote 0
                  • T
                    the6thday
                    last edited by

                    @JTY:

                    Did some testing, not sure if anyone found this before. Anyway…

                    After bridging the Wireless with the LAN, the following is appears when running dmesg:

                    bridge0: invalid MTU for re0

                    I checked the bridge0 interface, and it had an MTU of 2290, just like ath0. Obviosly that MTU is invalid for a standard ethernet NIC, thus it refuses to join bridge.

                    From there, I attempted to set ath0 (Wireless) MTU via pfSense webConfigurator, but the MTU setting was ignored. So, I manually set it via the shell. However, bridge0 still had an MTU of 2290 after changing ath0's MTU.

                    Finally, I decided to manually destroy bridge0, and recreate it. Now, that I had ath0 set with an MTU of 1500, both ath0 and re0 would have the same MTU.

                    ifconfig bridge0 destroy
                    ifconfig bridge create
                    ifconfig bridge0 addm ath0 addm re0 up

                    After recreating the bridge with both devices having an MTU of 1500, the bridge worked properly. The only left was to create a firewall rule to allow traffic in on the Wireless interface, which I did via the webConfigurator.

                    Hopefully the above is of use to somebody.

                    Hi,

                    thank you…
                    I can verify this... I had the exact same problem, manually changing the MTU and recreating the Bridge worked perfectly...

                    Now I can finally use Itunes remote on my Ipod  ;D

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

                      after resetting the interface config and this time just choosing 802.11g and running as an accesspoint I've had no more problems, other than the athstats error.

                      Thanks guys t is good to finally have a usable wireless connection.

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

                        @JTY:

                        After bridging the Wireless with the LAN, the following is appears when running dmesg:

                        bridge0: invalid MTU for re0

                        I checked the bridge0 interface, and it had an MTU of 2290, just like ath0.

                        How did your ath0 get a MTU of 2290? I just setup a LAN ath bridged to WAN and did not see that, it defaults to 1500.

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

                          @cmb:

                          @JTY:

                          After bridging the Wireless with the LAN, the following is appears when running dmesg:

                          bridge0: invalid MTU for re0

                          I checked the bridge0 interface, and it had an MTU of 2290, just like ath0.

                          How did your ath0 get a MTU of 2290? I just setup a LAN ath bridged to WAN and did not see that, it defaults to 1500.

                          I had done a fresh install of 1.2.1 TESTING, and setup OPT1 (ath0) during install. Once I rebooted, ath0 was set with an MTU of 2290.

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

                            i am running build built on Sat Jul 26 21:27:41 EDT 2008

                            When I was configuring the interface I had to manualing change the mtu to 1500

                            After I changed it I had no more problems.

                            I tried to reproduce the error by deleting the interface and reconfiguring it and nothing seemed to reproduce the change in mtu to 2290.

                            I then remembered I initially tried to configure turbo G in the wireless configuration>standard drop down menu.  And used channel 6 channel list, which is list as a turbo G channel.

                            When I configure my card to these settings I get this

                            ifconfig ath0
                            ath0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290
                            ether 00:11:95:c2:27:a9
                            inet6 fe80::211:95ff:fec2:27a9%ath0 prefixlen 64 scopeid 0x3
                            inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255
                            media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
                            ssid TAMU channel 6 (2437 Mhz 11g) bssid 00:11:95:c2:27:a9
                            authmode WPA privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 31.5
                            scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7
                            roam:rate11g 5 pureg protmode RTSCTS wme burst dtimperiod 1

                            Note even though turbo G is listed on the dropdown menu's it is not supported in freebsd 7(last line in man pages).

                            I don't have time to confirm my last statement but I believe I read this about a week ago and I doubt it has changed since then.

                            Hope this helps.</hostap></up,broadcast,running,simplex,multicast>

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

                              OK. I just tried deleting the OPT1 (ath0), then rebooting. After rebooting, I recreated the interface, and once again it was set with an MTU of 2290. And, no I'm not using Turbo mode.

                              1 Reply Last reply Reply Quote 0
                              • D
                                DeCex
                                last edited by

                                Installed the pfSense-Full-Update-1.2.1-TESTING-SNAPSHOT-20080727-1206

                                I ran the ifconfig command and got this;
                                fxp0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                fxp1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 2290
                                lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
                                bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290

                                This is from 1.2 -stable ifconfig log. (works)

                                fxp0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500
                                fxp1: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
                                ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>mtu 1500
                                lo0: flags=8049 <up,loopback,running,multicast>mtu 16384
                                pfsync0: flags=41 <up,running>mtu 2020
                                pflog0: flags=100 <promisc>mtu 33208
                                enc0: flags=0<> mtu 1536
                                bridge0: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500</up,broadcast,running,simplex,multicast></promisc></up,running></up,loopback,running,multicast></up,broadcast,running,promisc,simplex,multicast></up,broadcast,running,simplex,multicast></up,broadcast,running,promisc,simplex,multicast></up,broadcast,running,simplex,multicast></up,loopback,running,multicast></up,broadcast,running,promisc,simplex,multicast></up,broadcast,running,simplex,multicast></up,broadcast,running,simplex,multicast>

                                1 Reply Last reply Reply Quote 0
                                • B
                                  BRuTAL_HiTMAN_
                                  last edited by

                                  yeah it won't let me bridge my wireless with my LAN either, i mean it says it does it, but then it just sits on "learning" in the Interfaces tab in the "Bridge (bridge0)" category.

                                  EDIT: Update, about 20-30 mins after bridging the connections unsuccessfully the router rebooted on it's own which worried me, but then upon loading the connections seem have to successfully bridge!

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

                                    Updated to the latest snapshot, and the problem continues. I have done further testing on this. When booting up the interface is now showing an MTU of 1500. However, after switching to Access Point mode, it automatically changes MTU to 2290. (Disregard the IP, I tested without bridging so I could try to determine which feature/function caused the MTU to change.)

                                    Before enabling AP mode:

                                    ifconfig ath0

                                    ath0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                            ether 00:c0:a8:c1:6b:82
                                            inet6 fe80::2c0:a8ff:fec1:6b82%ath0 prefixlen 64 scopeid 0x2
                                            inet 192.168.2.1 netmask 0xffffffff broadcast 192.168.2.1
                                            media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
                                            status: no carrier
                                            ssid GoatsBlood channel 1 (2412 Mhz 11g)
                                            authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan
                                            bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5
                                            protmode OFF burst

                                    ifconfig ath0

                                    ath0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 2290
                                            ether 00:c0:a8:c1:6b:82
                                            inet6 fe80::2c0:a8ff:fec1:6b82%ath0 prefixlen 64 scopeid 0x2
                                            inet 192.168.2.1 netmask 0xffffffff broadcast 192.168.2.1
                                            media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
                                            ssid GoatsBlood channel 1 (2412 Mhz 11g) bssid 00:c0:a8:c1:6b:82
                                            authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit txpower 31.5
                                            scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7
                                            roam:rate11g 5 protmode OFF burst -apbridge dtimperiod 1</hostap></up,broadcast,running,simplex,multicast></up,broadcast,running,simplex,multicast>

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

                                      It's definitely Access Point which is causing the MTU to be 2290. If I switch the interface to Ad-Hoc, the MTU is 1500. The moment I switch it back to Access Point, it becomes 2290. My guess is, this is some behavior in the driver itself. Perhaps pfsense could do a 'ifconfig ath0 mtu 1500' after setting the interface parameters.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        sullrich
                                        last edited by

                                        We commited a change to enforce mtu 1500.  Please try a recent snapshot.

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

                                          I have upgraded to the latest RC1 snapshot, and the problem still continues. Once Access Point is enabled, ath0 changes MTU to 2290.

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

                                            I decided to ask on the freebsd-net mailing list, and the response I got was, that 2290 is the default MTU for 802.11.

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