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

    Blocking off wireless network.

    Scheduled Pinned Locked Moved Firewalling
    64 Posts 3 Posters 14.3k 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.
    • C
      CaptainWTF
      last edited by

      @doktornotor:

      @kejianshi:

      Go back into the firewall rule you just created and uncheck "Not".

      LOL WTF? Why? Wasn't the main point to to isolate the WLAN from LAN and allow everything else?

      Yes but its on a totally seperate interface so doesn't it do that anyways if the subnet is different?

      And what if there were particular devices I wanted  to have access to certain things on the LAN network from the WLAN network. how would I go about doing that. Cause I do have a networkable receiver that i've an app on my phone to control it, as well as airplay abilities.

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        "I don't wanna block off WLAN from LAN entirely."

        I think he will need to block per client.  But I'd rather do that after DHCP is known to work on the AP subnet and after DDWRT is up.

        I think he will want to create an alias of things to either allow or block and add that rule after things are working.

        But yeah - doktornotor's way would isolate the AP subnet from the LAN subnet totally while still allowing internet - I just though selective isolation was the point.

        If you keep that rule as doktornotor says, that can also work fine so long as you create an alias of clients you wish to allow to the LAN subnet, put that rule first on the list of firewall rules.

        However, I prefer to not block anything at all until DD-WRT is up and going because you will probably be accessing the DD-WRT menu from the LAN interface, unless I'm mistaken?

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

          @kejianshi:

          "I don't wanna block off WLAN from LAN entirely."

          I think he will need to block per client.  But I'd rather do that after DHCP is known to work on the AP subnet and after DDWRT is up.

          I think he will want to create an alias of things to either allow or block and add that rule after things are working.

          Correct. More so I want to block all clients, and allow the ones I wish.

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            If you keep that rule as doktornotor says, that can also work fine so long as you create an alias of clients you wish to allow to the LAN subnet, put that rule first on the list of firewall rules.

            However, I prefer to not block anything at all until DD-WRT is up and going because you will probably be accessing the DD-WRT menu from the LAN interface, unless I'm mistaken?

            Anyway - Try out that port with a computer and see if it works.  And please post the Services > DHCP server > AP screen.

            We want to make sure DHCP is good to go before starting into DDWRT again.

            Still

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

              I think we got AP working, I can now get internet access through the DD-WRT router. Next up. need to work on configuring the router as the AP.

              1 Reply Last reply Reply Quote 0
              • K
                kejianshi
                last edited by

                Cool - Can you post your DHCP for the AP on pfsense page?

                I just want to be sure there will be no issues.

                If that is fine, I think you will be ready for configuring the DD-WRT again.

                I think its probably best to have a IP range on the AP subnet that is reserved for static so that your AP will work well and not conflict with the DHCP range that pfsense will assign.

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

                  Issue resolved. Apparently I cant use the WAN port on my AP to plug in from the pfsense box. as soon as I switched the cable over from the WAN port to a LAN port on the router(AP) it started pulling DHCP requests from the pfsense box & I was able to get WAN access.

                  So now everything is working okay. But what I can do still is ping devices on my LAN network from the AP which I don't want.

                  And thanks to Kejianshi and Doktor for all of the help they've been giving.  I appreciate it greatly.

                  1 Reply Last reply Reply Quote 0
                  • K
                    kejianshi
                    last edited by

                    Thats fixable - Wanna fix it now?

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

                      @kejianshi:

                      Thats fixable - Wanna fix it now?

                      Sure

                      1 Reply Last reply Reply Quote 0
                      • K
                        kejianshi
                        last edited by

                        OK - The original rule that doktornotor gave you will allow web access but block access to LAN subnet.

                        Set that as he said before.

                        Then onece you have that working let me know.

                        Make sure you have web access but cant ping lan.  Then let me know when that part is done.

                        1 Reply Last reply Reply Quote 0
                        • K
                          kejianshi
                          last edited by

                          WTF - Its working…

                          I'm glad too.  I said you would get this going and I hate being wrong.  :P

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

                            @kejianshi:

                            WTF - Its working…

                            I'm glad too.  I said you would get this going and I hate being wrong.  :P

                            haha, Thanks.

                            Turns out the AP didnt like using WAN port as LAN.

                            As for the denied access from AP to LAN and exceptions being created. that works as well all thanks to Kejianshi.

                            thanks once again :)

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

                              Oh noes, it's working? WTF really :D

                              1 Reply Last reply Reply Quote 0
                              • K
                                kejianshi
                                last edited by

                                Between the epic CaptainWTF saga and the Pink floyd I was down to one last breath and 6 feet from the edge and wondering…

                                Will this ever work?

                                (might have been some Creed in there also)

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