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

To NAT or not to NAT thats the question !

Scheduled Pinned Locked Moved NAT
8 Posts 3 Posters 5.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.
  • T
    tobsen
    last edited by Jan 5, 2006, 10:14 AM

    Hi people

    I have some strange NAT problems and can'n get em solved.
    I am using the PFSense BETA 1.0 on my WRAP and want to FTP and SSH from the universe :-) to my home server.
    I set up for example SSH in NAT like this

    WAN Interface -> Proto TCP -> Port 22 -> NAT IP 192.168.192.4 -> Port 22

    And the firewall rule on the WAN interface is that

    WAN Interface -> Proto TCP -> Source  * -> Port 22 (SSH) -> Destination 192.168.192.4 -> Port 22 (SSH)

    but it won't work :-(
    when I am @home ( from within LAN) it works well and when I am connected via PPTP it is ok too.
    Well I do not get it , some of you maybe ? please help

    FTP is working neither from outside nor from inside out.

    WHAARG !

    so long …and thx

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by Jan 5, 2006, 1:23 PM

      FTP is under observation atm and it looks that something is a bit borked there.

      To access your pfsense from WAN-side you don't need a NAT. Simply create a pass rule at WAN with protocol tcp from source any, port any, destination interface adress, port SSH.

      1 Reply Last reply Reply Quote 0
      • T
        tobsen
        last edited by Jan 5, 2006, 2:39 PM

        thx for the answer…
        ...will ftp work better in beta 2 ?

        the thing with ssh is that i do not want to ssh to my pfsense box but to my FreeBSD server. and i think thats the point where i need a NAT rule for it.
        but this won't work either ! hmm..

        so long...

        1 Reply Last reply Reply Quote 0
        • T
          tobsen
          last edited by Jan 5, 2006, 2:58 PM

          ssh works for now

          the source port for the rule was wrong, I set it to any

          thx

          http://forum.pfsense.org/index.php?topic=408.0

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by Jan 5, 2006, 3:53 PM

            @tobsen:

            thx for the answer…
            ...will ftp work better in beta 2 ?

            we are working on it. check http://cvstrac.pfsense.com/timeline for improvements to expect in beta2.

            1 Reply Last reply Reply Quote 0
            • P
              podilarius
              last edited by Jan 6, 2006, 11:15 PM

              @hoba:

              FTP is under observation atm and it looks that something is a bit borked there.

              To access your pfsense from WAN-side you don't need a NAT. Simply create a pass rule at WAN with protocol tcp from source any, port any, destination interface adress, port SSH.

              I have observed it not working to a remote FTP site.  ;D

              1 Reply Last reply Reply Quote 0
              • T
                tobsen
                last edited by Jan 9, 2006, 12:17 PM

                same for me
                  neither in, nor out  :o

                1 Reply Last reply Reply Quote 0
                • P
                  podilarius
                  last edited by Jan 10, 2006, 6:11 PM

                  OK … its working now in PREBETA2 ... so it should be working in the upcome release (whenever that will be)

                  Thanks guys!!!

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