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

    LAN/WAN on the same subnet

    Scheduled Pinned Locked Moved Wireless
    18 Posts 4 Posters 4.7k 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.
    • D
      doktornotor Banned
      last edited by

      @Shadow:

      I'm trying to have my lan and wlan interfaces on the same network : 192.168.1.0/24.

      Why? Because it works too well now?  ::)

      Either get a spare management interface or start from scratch with just WAN assigned and configure from WAN.

      1 Reply Last reply Reply Quote 0
      • S
        Shadow aok
        last edited by

        Because i want to ? Isn't that enough ?

        The only way to make wlan work in that state is to set it to another network like 192.168.4.0/24.
        But this way dhcp relay would give them an 192.168.1.X ip from 192.168.1.102 with a gateway on 192.168.1.1. So connectivity will fail.
        And since i can't have dhcp relay on lan AND dhcp server on wlan, i don't have a workign solution.

        I can probably can set a spare management interface using an usb ethernet adapter, that's not an issue.

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

          @Shadow:

          But this way dhcp relay would give them an 192.168.1.X ip from 192.168.1.102 with a gateway on 192.168.1.1. So connectivity will fail.

          Uh, what? Configure a new scope (pool) on the DHCP server for 192.168.4.0/24. Use that scope for the WLAN clients. It works perfectly fine with the AD DHCP.

          1 Reply Last reply Reply Quote 0
          • S
            Shadow aok
            last edited by

            Yeah, it's a working solution, but i'd prefer having everything on the same subnet.

            But i guess i can use it that way and start from scratch another time.

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

              You can try from WAN if you don't have a spare NIC handy. From the interfaces that are going to get bridged, it's basically a no go. Reliably ended up cut off everytime I tried. The console needs to grow a bridge creation feature.

              1 Reply Last reply Reply Quote 0
              • S
                Shadow aok
                last edited by

                I'll try from wan outside office hours.

                From this setup :
                WAN1 : re1 (DHCP/DHCP6)
                WAN2 : re2 (DHCP/DHCP6)
                LAN : re0 (192.168.1.1/none)
                WLAN : ath0 (192.168.4.1/none)

                I should go to this ?
                WAN1 : re1 (DHCP/DHCP6)
                WAN2 : re2 (DHCP/DHCP6)
                LAN : BRIDGE0 (192.168.1.1/none)
                WLAN : ath0 (none/none)
                Bridge0 : re0

                1 Reply Last reply Reply Quote 0
                • P
                  pLu
                  last edited by

                  1 Reply Last reply Reply Quote 0
                  • dotdashD
                    dotdash
                    last edited by

                    @Shadow:

                    I should go to this ?
                    WAN1 : re1 (DHCP/DHCP6)
                    WAN2 : re2 (DHCP/DHCP6)
                    LAN : BRIDGE0 (192.168.1.1/none)
                    WLAN : ath0 (none/none)
                    Bridge0 : re0

                    The bridge should consist of WLAN (ath0) and LAN (re0).
                    It won't let you make a bridge with one interface. Make the bridge with LAN and WLAN first, then change LAN to the bridge interface.
                    Good luck.

                    1 Reply Last reply Reply Quote 0
                    • S
                      Shadow aok
                      last edited by

                      I know that :)
                      My question is what to do with the LAN interface which is currently on re0.

                      1 Reply Last reply Reply Quote 0
                      • dotdashD
                        dotdash
                        last edited by

                        @dotdash:

                        Make the bridge with LAN and WLAN first, then change LAN to the bridge interface.

                        1 Reply Last reply Reply Quote 0
                        • S
                          Shadow aok
                          last edited by

                          Problem is, bridge0 can't be set on lan interface since lan is already a member of bridge0.
                          You mean bridge0 on re0?

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

                            @Shadow:

                            You mean bridge0 on re0?

                            Huh? What? You just told us that re0 is your LAN… See, this is exactly why I told you that you should restart from scratch. (Not to mention how utterly pointless this whole thing is.)

                            1 Reply Last reply Reply Quote 0
                            • S
                              Shadow aok
                              last edited by

                              pfSense interface named LAN is currently set on re0 port.

                              Ok, i have my answer :

                              http://www.stephenyeong.idv.hk/wp/2010/03/pfsense-wireless-bridge-working/

                              Forgot one step.

                              WAN1 (DHCP/DHCP6) : re1
                              WAN2 (DHCP/DHCP6) : re2
                              LAN (192.168.1.1/none) : BRIDGE0 (OPT1+WLAN)
                              WLAN (none/none) : ath0
                              OPT1 (none/none) : re0

                              Changes made through WAN and now it's working fine :)
                              Thanks.

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