Navigation

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

    Some error disables wired connections

    General pfSense Questions
    4
    11
    701
    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.
    • R
      rocketdog last edited by

      Hello, again..

      I have yet another problem. It have occured a couple of times the last few days. Suddenly from nowhere, all my "wired" connections becomes unusable, however the WIFI still works - and LAN and WIFI is  bridged!

      When I turn on the monitor on my pfsense-box, I am able to ping my gateway etc - hence why WIFI still works - but all other local hosts are unpingable.
      The only solution is to reboot pfSense.

      Here is a photo taken 20-30 seconds after it occured:

      I guess it is the miniupnp-string.
      Does anyone have any idea what the reason could be? If you need more information about my setup, feel free to ask.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned last edited by

        Perhaps stop bridging in the first place? Especially when your wifi is extremely unstable and flooding log with galores of "stuck beacon" errors.

        1 Reply Last reply Reply Quote 0
        • R
          rocketdog last edited by

          @doktornotor:

          Perhaps stop bridging in the first place? Especially when your wifi is extremely unstable and flooding log with galores of "stuck beacon" errors.

          Bridging is the only way I made pfSense work both with LAN and as an AP. However, I've been running this setup for months, and the problems just started after the 2.2.4-upgrade.

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned last edited by

            @rocketdog:

            Bridging is the only way I made pfSense work both with LAN and as an AP.

            Huh???

            1 Reply Last reply Reply Quote 0
            • R
              rocketdog last edited by

              @doktornotor:

              @rocketdog:

              Bridging is the only way I made pfSense work both with LAN and as an AP.

              Huh???

              I had a hard time setting the pfsense-box up, and was happy enough when I finally made wifi and lan work on the same IP-range. So I've used the same setup ever since.
              However, back to the problem.. :P

              1 Reply Last reply Reply Quote 0
              • KOM
                KOM last edited by

                I don't have this issue but I think I remember having read that you can use a generic AP without having to bridge if you disable DHCP on the AP and then plug one of its LAN connections into one of your pfSense LAN ports.

                1 Reply Last reply Reply Quote 0
                • R
                  rocketdog last edited by

                  Alright. I might check it out later.

                  Does anyone know what the wifi-problem is? the 'ath0: stuck beacon ; resetting (bmiss count 4)' ?

                  1 Reply Last reply Reply Quote 0
                  • Derelict
                    Derelict LAYER 8 Netgate last edited by

                    Wi-Fi support in FreeBSD blows chunks when compared with all the decent, low-cost, purpose-built APs on the market these days?

                    Chattanooga, Tennessee, USA
                    The pfSense Book is free of charge!
                    DO NOT set a source port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 0
                    • R
                      rocketdog last edited by

                      @Derelict:

                      Wi-Fi support in FreeBSD blows chunks when compared with all the decent, low-cost, purpose-built APs on the market these days?

                      Remembered I had an TP-Link WIFI Router lying around collecting dust. So I plugged it straight into the LAN-interface.
                      Laptops connects just fine, but Android and Chromecast clients does not work at all.

                      1 Reply Last reply Reply Quote 0
                      • Derelict
                        Derelict LAYER 8 Netgate last edited by

                        Sounds like Wi-Fi just isn't your thing.

                        (Did you disable the DHCP server on the TP-Link?)

                        (I said "AP" (Access Point).  Not "Router")

                        Chattanooga, Tennessee, USA
                        The pfSense Book is free of charge!
                        DO NOT set a source port in a port forward or firewall rule unless you KNOW you need it!
                        Do Not Chat For Help! NO_WAN_EGRESS(TM)

                        1 Reply Last reply Reply Quote 0
                        • R
                          rocketdog last edited by

                          @Derelict:

                          Sounds like Wi-Fi just isn't your thing.

                          (Did you disable the DHCP server on the TP-Link?)

                          (I said "AP" (Access Point).  Not "Router")

                          Correct. I never had much time fooling around with it. Except once trying to turn a usb-dongle into a AP..after many hours/days of cursing, it worked…but whatever.

                          Yes, I disabled DHCP. Androids can finally connect. Now it's just the darn Chromecast left. I remember some setting when I had the AP running at the pfsense which made the Chromecast work, can't find it on this cheap TP-Link-thing though.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post