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

having issues to SSH to Unraid Behind Pfsense Port Forwarding

Scheduled Pinned Locked Moved NAT
7 Posts 2 Posters 940 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
    comet424
    last edited by Mar 6, 2019, 12:23 AM

    so I trying to get my Rsync to work and it does ssh I trying to access my remote unraid via the ssh of rysnc.. plus I tried doing ssh <server>.dns address.com not working
    so I not quiet sure how to get it to work...
    as I tried getting Unraid client to connect to Pfsense OpenVPN and that didn't work..

    so I just trying to SSH to my remote unraid box behind a pfsense.. but its not working..im im sure youll say i did something wrong.. but that's ok..
    here some pics i took WAN LAN and NAT hope this helps
    thanks
    2_1551831791423_pfsense3.JPG 1_1551831791423_pfsense2.JPG 0_1551831791423_pfsense1.JPG

    1 Reply Last reply Reply Quote 0
    • C
      comet424
      last edited by Mar 6, 2019, 1:30 AM

      I just noticed maybe my topic needs to be in Firewall section if im in the wrong section please move me to the proper section please

      1 Reply Last reply Reply Quote 0
      • D
        Derelict LAYER 8 Netgate
        last edited by Derelict Mar 6, 2019, 1:49 AM Mar 6, 2019, 1:47 AM

        DO NOT set a source port on a port forward or firewall rule unless you are ABSOLUTELY CERTAIN it is necessary.

        Same goes for STATIC PORT on outbound NAT.

        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
        • C
          comet424
          last edited by comet424 Mar 6, 2019, 2:29 AM Mar 6, 2019, 2:25 AM

          like this? or do I have it wrong still.. when I SSH from my computer to unraid… Pfsense (on the remote side) it showing data to the unraid IP address... but I not getting any ackknowlegement my side... just receives but not getting a signal... and I added on the WAN side because I thought if incoming connection at port 22 would direct it to unraids ssh rysnc… or if im totally wrong... what should the line be so I can edit it
          0_1551839241926_pfsen6.JPG
          0_1551839248300_pfsens4.JPG

          0_1551839260236_pfsens5.JPG
          0_1551839387705_pfsen6.JPG

          1 Reply Last reply Reply Quote 0
          • C
            comet424
            last edited by comet424 Mar 6, 2019, 2:45 AM Mar 6, 2019, 2:39 AM

            if still wrong.. im a visual learner not a words learner... could you edit the photos and write it in red what it should be

            my unraid server is 192.168.1.8 and i wanna port forward port 22 for ssh rysnc… i been toggling etc but i cant seem to get it to work right.

            1 Reply Last reply Reply Quote 0
            • D
              Derelict LAYER 8 Netgate
              last edited by Mar 6, 2019, 2:54 AM

              Still wrong. DELETE EVERYTHING you have done to try to get this working. Everything.

              Delete the port forwards
              Delete the Outbound NAT
              Delete the firewall rules (if deleting the port forward didn't do it for you)

              Then:

              Firewall > NAT, Port forward

              Add

              Interface: WAN
              Protocol: TCP
              Destination: WAN Address
              Destination Port: 22 (SSH)
              Redirect Target IP: 192.168.1.8
              Redirect Target Port: 22 (SSH)
              Description: As you see fit
              NAT Reflection: Use system default
              Filter rule association: Add associated filter rule

              Save and apply. And you're done.

              If that does not work, it is NOT the port forward. It is something else:

              https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html

              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
              • C
                comet424
                last edited by Mar 6, 2019, 3:06 AM

                thank your @Derelict your awesome thank you very much .. that worked

                1 Reply Last reply Reply Quote 0
                7 out of 7
                • First post
                  7/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received