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

    Split incoming traffic - multiple IP-adresses

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 4 Posters 600 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.
    • H
      hebein
      last edited by

      Sorry, actually I do not know the correct technical termini for my problem:

      I have a WAN with multiple IP-adresses: x.y.z.80/29
      I would like to split up the incoming and outgoing traffic. EG traffic coming for x.y.z.86 all forward to 10.130.1.20
      or traffic incoming for x.y.z.85:1090 forward to 10.130.1.21:1090
      or all traffic outgoing from 10.139.1.22 through x.y.z.84

      How do i achieve that? I have a NG 1100.

      regards,
      Gunther

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Not clear, what you're trying to achieve exactly.
        If want a specific external IP to be forwarded to a specific internal IP and outgoing packets from that specific internal IP should get that specific external IP, you can do that with NAT 1:1. Firewall > NAT > 1:1
        Add a new rule, just enter the external IP (e.g. x.y.z.86), at "Internal IP" select "single host" and enter your internal IP (e.g. 10.130.1.20), enter a description and save the rule.

        So packets for the public IP x.y.z.86 get forwarded to 10.130.1.20, while packets coming from 10.130.1.20 going out to the internet get the IP x.y.z.86.

        If you don't want NAT 1:1 you can forward incoming packets with port forwarding rules (Firewall > NAT > Port Forward) and set outbound NAT rules separately in Firewall > NAT > Outbound. You will have to switch the outbound NAT into the hybrid mode first and then add rules for the WAN interface to fit your needs.

        1 Reply Last reply Reply Quote 0
        • H
          hebein
          last edited by

          ok, that's exactly what I am doing but what is not working :(

          1 Reply Last reply Reply Quote 0
          • RicoR
            Rico LAYER 8 Rebel Alliance
            last edited by Rico

            Show screenshots so we can see what you really did.

            -Rico

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

              Port forward rules for the inbound connections. Outbound NAT for the outgoing connections. It works.

              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.