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

    NAS as Separate Interface?

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 857 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.
    • B
      bfisbeck
      last edited by

      I currently have a pfSense box w/ 3 ethernet ports. Due to location constrictions, I am attempting to setup the following:

      eth0 -> WAN
      eth1 -> LAN, 192.168.1.xxx (switch connected to access point, wired devices, etc)
      eth2 -> NAS, 192.168.2.1

      I have attempted to setup the NAS as its own interface, then bridge this connection to LAN. I am able to ping the NAS IP, but trying to access the HTTP front-end sends me to the pfSense login.

      I also attempted to remove the bridge and instead create a rule to allow all traffic on NAS interface, but I still have the same results.

      Is this a possible setup? Am I overlooking additional configuration options?  Are there disadvantages to this setup?

      Thank you in advance.

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

        Why do you have to route traffic to the NAS? Why not just put it on LAN on a switch port?

        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
        • S
          seed
          last edited by

          The NAS IP should be on a network that is 192.168.2.0/24 and be set to DHCP or a static IP in that network. The .1 address should be reserved for the interface gateway for eth2. Then do the rules to allow to access it from your LAN ips or the 192.168.1.0/24 network.

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