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

    Putting my pfSense Home Lab on an Extender

    Scheduled Pinned Locked Moved General pfSense Questions
    19 Posts 3 Posters 2.0k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Do you have port forwards for that traffic on the pfSense WAN?

      If not, and it was working before, it must be all routed. So that would mean no NAT on pfSense and a static route in the Asus router to the 192.168.5.X subnet?
      Most SOHO routers have no static route capability so....

      The fact you are seeing traffic hitting the pfSense WAN for 192.168.5.6 implies either it is routed or that you have a port forward (or 1:1 NAT) and that may be preventing you reach the pfSense gui.

      T 1 Reply Last reply Reply Quote 0
      • T
        The_Director @stephenw10
        last edited by The_Director

        Sorry @stephenw10 I was away on vacation.

        The Asus router did have a static route to route 192.168.5.0 network traffic to the pfSense router (192.168.1.2).

        Then the pfSense router had rules to allow 192.168.1.0 network traffic though.

        I have tried to disable NAT on the pfsense router, but this made no difference.

        R 1 Reply Last reply Reply Quote 0
        • R
          RobH 0 @The_Director
          last edited by

          @the_director Maybe you could use Powerline or MoCA adapters instead of that extender?

          T 1 Reply Last reply Reply Quote 0
          • T
            The_Director @RobH 0
            last edited by

            @robh-0 Powerline was actually my first choice, but the bedrooms are not on the same circuit. One room is on one breaker, and another room is one a different breaker

            R 1 Reply Last reply Reply Quote 0
            • R
              RobH 0 @The_Director
              last edited by

              @the_director Actually it is OK if they are on separate breakers, they just have to be in the same phase in the panel. In other words, they need to be on the same vertical row.

              T 1 Reply Last reply Reply Quote 1
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Ok, if you have a static route and no NAT then you need a firewall rule on the pfSense WAN to allow traffic from 192.168.1.X to 192.168.5.X. Otherwise it will just be blocked there.

                Also make sure the pfSense WAN does not have 'block private networks' set since that traffic is from a private subnet

                Steve

                T 1 Reply Last reply Reply Quote 0
                • T
                  The_Director @RobH 0
                  last edited by

                  @robh-0 Really! Ok then I may need to give this a try!

                  1 Reply Last reply Reply Quote 0
                  • T
                    The_Director @stephenw10
                    last edited by

                    Thanks @stephenw10! Haven't had much time to play around with this (some unfortunate life events have been underway), but should get some thing this week! Ill test out all your suggestions and update the thread.

                    1 Reply Last reply Reply Quote 1
                    • T
                      The_Director
                      last edited by

                      So I got a little time tonight to play around with it, but unfortunately still getting blocked. Below are some screenshots.

                      Even though I (believe) I set the firewall to all anything though, its still blocking it, which makes no sense to me.

                      The pfSense firewall rules:
                      2022-09-28_20h07_25.png

                      The pfSsense firewall logs:

                      2022-09-28_20h08_06.png

                      Current NAT settings:
                      2022-09-28_20h09_49.png

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Hmm, that certainly seems like it should pass with that allow all rule on WAN.

                        Do you see any alerts in the GUI?

                        Go to Status > Filter Reload and reload the filter with the button there. Make sure it loads cleanly without any errors.

                        Steve

                        T 2 Replies Last reply Reply Quote 1
                        • T
                          The_Director @stephenw10
                          last edited by

                          @stephenw10 will do when I get home from work this evening

                          1 Reply Last reply Reply Quote 0
                          • T
                            The_Director @stephenw10
                            last edited by

                            @stephenw10 This is what I get from the Filter Reload:
                            2022-10-18_15h50_20.png

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Looks fine. And you are still seeing blocked traffic in the firewall log on WAN like that?

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                The_Director @stephenw10
                                last edited by

                                @stephenw10 So if I try to access 192.168.5.6 (an iDrac that sits behind the pfSense box) I get "192.168.5.6 took too long to respond." but I dont see the firewall logging anything like it did before (see below). The 5.6 address is perfectly accessable by a laptop sitting behind the pfSense box, and the laptop can access the external web just fine.

                                2022-10-18_16h18_17.png

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