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

    Latest snapsot wireless bridged as well as static not working

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    140 Posts 12 Posters 73.1k 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.
    • AhnHELA
      AhnHEL
      last edited by

      ok, funny thing.

      Once booted, enter GUI and go to Interfaces/LAN

      Uncheck or Check Disable the Userland FTP-Proxy application

      Hit Save and then Apply.

      Bridge is working with proper MTU!

      I reproduced this 3 times, test on yours please.

      AhnHEL (Angel)

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

        @onhel:

        ok, funny thing.

        Once booted, enter GUI and go to Interfaces/LAN

        Uncheck or Check Disable the Userland FTP-Proxy application

        Hit Save and then Apply.

        Bridge is working with proper MTU!

        I reproduced this 3 times, test on yours please.

        That'll do the same thing as just clicking Save without changing anything.

        Pretty sure I have a lead on the cause of this issue, it's some sort of FreeBSD bug, looking for a solution.

        1 Reply Last reply Reply Quote 0
        • AhnHELA
          AhnHEL
          last edited by

          At least we're down to a one click fix

          ;D

          AhnHEL (Angel)

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            @onhel:

            At least we're down to a one click fix

            ;D

            In the tests I've done on this little WRAP I have next to me, saving is what reset it to 2290 :) Not quite what I'd call a fix yet…

            A FreeBSD bug in hostapd is the likely culprit, as cmb said we're all hoping for a fix.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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

              Please, keep as posted on the progress  :)

              1 Reply Last reply Reply Quote 0
              • X
                xbipin
                last edited by

                @onhel:

                ok, funny thing.

                Once booted, enter GUI and go to Interfaces/LAN

                Uncheck or Check Disable the Userland FTP-Proxy application

                Hit Save and then Apply.

                Bridge is working with proper MTU!

                I reproduced this 3 times, test on yours please.

                i cant believe this, the solution is this simple, i just tried it and within less than 30 secs it started working like there was no problem at all

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

                  @xbipin:

                  i cant believe this, the solution is this simple, i just tried it and within less than 30 secs it started working like there was no problem at all

                  It's not really that simple. That doesn't do anything differently from manually running the commands I noted earlier in the thread. It will make it work for a bit, but it won't stay working.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    actually when i tried manually those commands it never used to work but currently at least its running fine for the past like 15mins, lets see how long it lasts

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

                      Confirmed, this… workaround  :) works. I have stable wireless connection for more then 2 hours now.

                      1 Reply Last reply Reply Quote 0
                      • X
                        xbipin
                        last edited by

                        i can confirm it to work now in stable state for more than 24 hours, im on the 31st may 2009 1.2.3 7.2 base snapshot

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

                          I don't see any updates for 1.2.3 7.2 based after May 30th…  ???

                          1 Reply Last reply Reply Quote 0
                          • AhnHELA
                            AhnHEL
                            last edited by

                            I'm back on 7.1 builds.  Clicking Save in Interfaces/LAN fixes the "wireless bridge MTU and promiscuous mode" bug in the 7.1 build as well.  Besides, 7.1 builds are up to 1.2.3 RC2.

                            AhnHEL (Angel)

                            1 Reply Last reply Reply Quote 0
                            • X
                              xbipin
                              last edited by

                              i tried the 3rd june 1.2.3 7.1 but pppoe wont work so i went back to the 31st may 1.2.3 7.1 base release and work fine with the wireless workaround

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

                                this is more of a firewall issue but it affects some how the wireless interface so I'm going to post it here  :)
                                my firewall setup can be seen in attached files
                                when rules on the LAN interface setup first time everything works OK but after reboot I get this message in dmesg:

                                Configuring firewall...
                                ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled
                                ipfw:
                                rule 2: setsockopt(IP_FW_DEL)
                                :
                                Invalid argument
                                ipfw:
                                rule 3: setsockopt(IP_FW_DEL)
                                :
                                Invalid argument
                                
                                

                                when the router is up my wireless wont work. I'm getting dhcp ip address and all other info right but I can connect to the firewall or internet.
                                Looks like this error makes firewall do something to the wireless interface. Wireless is bridged to LAN

                                removing and recreating these rules would fix the problem.

                                lan.png
                                lan.png_thumb
                                wan.png
                                wan.png_thumb
                                wireless.png
                                wireless.png_thumb
                                ipsec.png
                                ipsec.png_thumb

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

                                  We were able to get the changing MTU issue that was causing the problem on the systems I saw resolved in FreeBSD, and have added that patch to our snapshots as of a couple days ago. Those of you who could replicate issues, please test the latest snapshot from here and report back.
                                  http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/?C=M;O=D

                                  1 Reply Last reply Reply Quote 0
                                  • X
                                    xbipin
                                    last edited by

                                    just downloaded and reflashed to pfSense-1.2.3-20090609-0445 and the wireless issue has been solved, works perfect now, so finally we r over with it, keep in mind 1.2.3 RC2 is FreeBSD 7.2 base now

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

                                      @xbipin:

                                      just downloaded and reflashed to pfSense-1.2.3-20090609-0445 and the wireless issue has been solved, works perfect now, so finally we r over with it, keep in mind 1.2.3 RC2 is FreeBSD 7.2 base now

                                      Thanks for the report!  That's good news, glad to see it seems to be fixed in FreeBSD now. Yes, 1.2.3 will be on FreeBSD 7.2 unless some major reason appears to not use it. Thus far it's been a painless change.

                                      1 Reply Last reply Reply Quote 0
                                      • X
                                        xbipin
                                        last edited by

                                        how about making it on FreeBSD 8 and when can the nanobsd images be available for testing for embedded?

                                        any plans of adding some basic packages to the embedded images to add some more functionality, eg: siproxd and other basic commonly used packages bcoz for home networking, there r not any specific features i use of pfsense other than traffic shaping and wireless.

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

                                          @xbipin:

                                          how about making it on FreeBSD 8

                                          It was committed to FreeBSD by Sam Leffler so it's in 8. It was also MFCed to RELENG_7. We have the same patch on top of 7.2, because it won't get changed in RELENG_7_2.

                                          @xbipin:

                                          and when can the nanobsd images be available for testing for embedded?

                                          You'll see there are nanobsd folders on the snapshot server now, we'll have images up soon.

                                          @xbipin:

                                          any plans of adding some basic packages to the embedded images to add some more functionality, eg: siproxd and other basic commonly used packages bcoz for home networking, there r not any specific features i use of pfsense other than traffic shaping and wireless.

                                          siproxd is in embedded in 1.2.3. You can install many other packages if you want. http://doc.pfsense.org/index.php/Installing_packages_on_embedded

                                          Packages and embedded will change in a yet to be determined way once we're switched to nanobsd embedded. We will be making all embedded suitable packages available in some fashion (easier than the above).

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            xbipin
                                            last edited by

                                            one feature which has been talked about much under wireless but hasn't been implemented as yet is the option to select the transmit and receive antenna for wireless bcoz not all have 2 antennas and this has been discussed in the wireless forum and was also said it would be added in future releases but haven't seen it as yet. i tried running the below commands and restarting the box but then the wireless clients would connect but were not able to surf so then i have to click the save button on the wireless page and then everything comes to normal but then the below values change to default, rx=0 tx=1 div=1

                                            sysctl dev.ath.0.txantenna=0
                                            sysctl dev.ath.0.rxantenna=0
                                            sysctl dev.ath.0.diversity=0

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