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

    Wireless Router LAN/OPT1 Bridge - Wireless only works if LAN is connected

    Scheduled Pinned Locked Moved Wireless
    6 Posts 3 Posters 1.8k 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.
    • A
      atzouris
      last edited by

      I actually have two hardware/software setups

      IT-100 pfhacom running pfsense 2.0.3 (works as desired)
      Alix-2D13 pfsense version 2.2 (has issue with no LAN connection on power on)

      I have successfully configured pfsense as a wireless router and it works on both hardware/software setups.  In the simplest configuration I have LAN and OPT1 (ath0) bridged.  After a power on, It all works using pfsense 2.0.3 but when using pfsense 2.2 works but … I need to have a LAN connection in order to get Wireless Clients to associate.  Is there a simple solution to make pfsense 2.2 work as a wireless router without the LAN connected on boot?  Perhaps this is by design in regards to the LAN + OPT1 bridge  but I'm looking for a workaround.  I desire to have the Wireless Router work wireless without requiring to have LAN device connected.

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

        Yes, because you are doing it wrong. You need to assign the bridge, not individual interfaces.

        Hint: stop creating pointless bridges.

        1 Reply Last reply Reply Quote 0
        • A
          atzouris
          last edited by

          Never new that I could assign a bridge.  It was right there in assign interfaces.  However, I still get the same behaviour.

          WAN (wan)      -> vr1            ->
          LAN (lan)          -> vr0            -> v4: 10.0.1.1/24
          OPT1 (opt1)    -> ath0_wlan0 ->
          OPT2 (opt2)    -> vr2              ->
          OPT3 (opt3)    -> bridge0      ->

          where bridge0 is a bridge of LAN, OPT1, and OPT2.

          I'm clearly missing something here.

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

            I just had a reply written, hit post, and got the attached. Hit back - reply is gone.

            Goddamn hotel captive portal/proxy messing around with SSL sessions.  You hearing me all you lunatics who think this is a good idea?

            ![Screen Shot 2015-02-28 at 8.40.07 PM.png](/public/imported_attachments/1/Screen Shot 2015-02-28 at 8.40.07 PM.png)
            ![Screen Shot 2015-02-28 at 8.40.07 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-02-28 at 8.40.07 PM.png_thumb)

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/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
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              @atzouris:

              Never new that I could assign a bridge.  It was right there in assign interfaces.  However, I still get the same behaviour.

              WAN (wan)      -> vr1            ->
              LAN (lan)          -> vr0            -> v4: 10.0.1.1/24
              OPT1 (opt1)    -> ath0_wlan0 ->
              OPT2 (opt2)    -> vr2              ->
              OPT3 (opt3)    -> bridge0      ->

              where bridge0 is a bridge of LAN, OPT1, and OPT2.

              I'm clearly missing something here.

              Forget about LAN, OPT1, and OPT2.  You want a bridge between vr0, vr2, and ath0_wlan0.

              Create a bridge with members vr2 and ath0_wlan0

              In Interfaces > (assign) CHANGE the assigned interface for LAN from vr0 to BRIDGE0

              Go back and add vr0 to the bridge.

              No idea why you're bridging vr0 and vr2.  Get a switch and plug it into vr0.  Save vr2 for use as a router interface.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/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
              • A
                atzouris
                last edited by

                Thanks for the details as they were very helpful.  It now works as desired.

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