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

    5 Eth ports and Bridge issue

    Scheduled Pinned Locked Moved General pfSense Questions
    21 Posts 6 Posters 5.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

      By '//192.168.1.3' you mean access it as a Windows share? And you can access it that way from within the 192.168.1.0/24 subnet?
      Does your NAS have any restrictions? It may not allow traffic from outside its own subnet. It may not be able to respond if it doesn't have a route back, so bad subnet mask or gateway.
      Does the NAS have any logs you can look at?

      Steve

      1 Reply Last reply Reply Quote 0
      • S
        sogseal
        last edited by

        @stephenw10:

        By '//192.168.1.3' you mean access it as a Windows share? And you can access it that way from within the 192.168.1.0/24 subnet?
        Does your NAS have any restrictions? It may not allow traffic from outside its own subnet. It may not be able to respond if it doesn't have a route back, so bad subnet mask or gateway.
        Does the NAS have any logs you can look at?

        Steve

        yes I meant windows side, and yes I can access it within the 192.168.1.0/24 subnet. Its a FreeNAS. Im trying to find the logs but I don't see any, but here is network summary I got on freeNas:
        Name IPv4 Address IPv6 Address
        em0 192.168.1.3/24
        Nameserver
        192.168.1.1
        192.168.2.1
        Default route
        192.168.1.1

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

          This could also be windows firewall getting in the way. It will see the NAS as being in a different network zone so may not allow the traffic deppending how you have it set.

          Steve

          1 Reply Last reply Reply Quote 0
          • S
            sogseal
            last edited by

            @stephenw10:

            This could also be windows firewall getting in the way. It will see the NAS as being in a different network zone so may not allow the traffic deppending how you have it set.

            Steve

            thanks bud, ill play around with it more, if not ill connect my wifi router to my switch :)

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by

              Yes if your going to route all traffic out a specific gateway, your vpnv4 then you have to allow rules to get to your other networks.  You can use the aliases for the network in the dropdown list, ie lan and rtn66u

              See how your lan rules show lan net for the source.

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              1 Reply Last reply Reply Quote 0
              • S
                sogseal
                last edited by

                @johnpoz:

                Yes if your going to route all traffic out a specific gateway, your vpnv4 then you have to allow rules to get to your other networks.  You can use the aliases for the network in the dropdown list, ie lan and rtn66u

                See how your lan rules show lan net for the source.

                ahh i see, so add another rule for LAN : source LAN net Destination RTN66U net and for RTN66U: source RTN66U net and destination LAN net. Im beeing retarted, just woke up :) Thanks again for your help

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

                  I would not expect that to make any difference since those aliases are what you already had in place; LAN net = 192.168.1.0/24 and RTN66U net = 192.168.2.0/24. Unless I've misread something.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    doesn't make any difference to the rule..  but just makes it look cleaner ;)

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

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

                      Yep, also means you don't have to change the firewall rules if you change the interface subnet.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • S
                        sogseal
                        last edited by

                        @johnpoz:

                        doesn't make any difference to the rule..  but just makes it look cleaner ;)

                        I like things to look clean ;) btw im going rethink my whole network, sketch it first. Thank you guys for you time and help

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