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

    TCP doesn't work through 1:1 virtual IP

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 549 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.
    • M
      Mars
      last edited by

      Hello,
      I am trying to setup a simple 1:1 public IP (virtual) to LAN IP, from outside I can ping, UDP seems to work but any TCP connection does not, seems packets are lost. I cannot get out from local server 192.168.7.100 (apt-get update doesn't work, TCP traffic seems to not getting out) but I can ping google.com

      Configuration is :

      • Virtual IP set

      • pfsense interfaces assignments are good : LAN IP is 192.168.7.2

      • 1:1 Virtual IP to LAN IP 192.168.7.100

      • Outbond 192.168.7.0/24 * * * Virtual IP public *

      • On 192.168.7.100 gw is pfsense LAN IP 192.168.7.2

      • WAN rules IPv4 TCP/UDP * * ->LAN Net * *

      • LAN rules is IPv4 LAN net * * * *

      I tried some advanced setting as ignore traffic on same interface but nothing works.
      I can ping 192.168.7.100 from outside, pinging Virtual IP public...

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

        How about you pose all of those screenshots instead.

        @mars said in TCP doesn't work through 1:1 virtual IP:

        1:1 Virtual IP to LAN IP 192.168.7.100
        Outbond 192.168.7.0/24 * * * Virtual IP public *

        I do not know why you would do this. 1:1 means just that. 1:1. It looks like you are also trying to outbound NAT the whole /24 to the same VIP which should work fine. But I honestly do not know what would happen in that case.

        @mars said in TCP doesn't work through 1:1 virtual IP:

        WAN rules IPv4 TCP/UDP * * ->LAN Net * *

        This also makes little sense.. You should be passing traffic to 192.168.7.100, not LAN net.

        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
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.