Problems with nat

  • colleagues recently started to set up a pfsense on my network and as usual I already have the first problem.

    I put them an example of the data structure exist and everything done.

    WAN -
    LAN -
    OPT1 -

    I have a virtual IP created to be the proxy server on the LAN, and I have several configured physically containing IPs of the OPT1 class, including a proxy server with the IP servers.

    To share that server with the LAN, I create a nat with the following property,

    Interface: LAN
    Protocol: *
    Source Address: *
    Source Ports: *
    Dest. Address:
    Dest. Ports: 3128
    NAT IP:
    NAT Ports: 3128

    So far so good, the problem is that when I try to connect from the LAN with an IP to proxy, the server does not answer me.

    So I went and revice logs to see and I run this:

    LAN tcp ( <- CLOSED: SYN_SENT 2/0104 B / 0 B
    OPT1 tcp -> SYN_SENT: CLOSED 2/0104 B / 0 B

    Well, here every problem, I would appreciate your help with the issue as soon as possible, thanks in advance.

    PS: I know that the LAN IPs are class A, but I have disabled blocking these IPS.

  • The traffic's passing and getting no reply. Either the proxy server isn't replying, or its reply isn't going back to the firewall to get translated back (may need source NAT as well depending).

  • Sorry for the inconvenience, but I'm new to using the pfsense, you could be more specific.

  • Looking at your description again, the proxy's on a diff subnet from the clients, so the source NAT part isn't necessary.

    Seems like either the proxy isn't replying, or its default gateway is pointed somewhere other than

  • sorry but I'm still having the same problem, the pfsense still gives the same answer when the connection runs


    In this can influence the servers that are making the point on the LAN, whether they are virtualized in Proxmox ??

  • SYN_SENT:CLOSED means it sent the SYN to the destination, and got no SYN ACK in response. The proxy isn't replying back, or is sending its reply to the wrong place.

Log in to reply