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

    Public ip selected for local IP

    Routing and Multi WAN
    2
    5
    730
    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.
    • P
      Pentium
      last edited by

      Thank you for any assistance.
      I have two problems.

      Trouble one:
      the provider has two different subnets on  a single physical adapter eth1.

      my network:

      WAN1 eth0  (default GW)
      –> 82.113.100.176 / 28 GW 82.113.100.177

      WAN2  eth1
      --> 90.182.100.240 / 29  GW 90.182.100.241
      --> 90.182.101.240 / 29  GW 90.182.101.241  (I do not know how to add this range.)

      LAN  eth2
      -->  192.168.1.0/24  GW 192.168.1.1

      if the problem will find a solution. My idea is to use a virtual adapter eth1:0

      This, but I can not solve.

      Trouble two:
      I would like to specify that the computer communicates:
      192.168.1.100 out through port eth1 WAN2 and will have a fixed IP 90.182.100.245
      192.168.1.101 out through port eth1 WAN2 and will have a fixed IP 90.182.100.246
      It is a mail server which have the reverse record for these IP

      I looked for help in Firewall: NAT: Outbound but no adjustment does not lead to success.
      Only if I change the default gateway in the System: Gateways changes to all local IP addresses to WAN2 eth1.

      Thank you very much for your time and possible solutions.

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

        I see that you have two possible solutions.

        Use an outside switch and two pfSense interfaces.
        One on 90.182.100.240 / 29  GW 90.182.100.241
        and one on  90.182.101.240 / 29  GW 90.182.101.241

        Have your provider remove their gateway interface and route 90.182.101.240 / 29 to your pfSense interface on the other subnet, say 90.182.100.242.

        If they did that you could use it as VIPs or as an interface subnet inside or route it somewhere else or do whatever you want.

        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
        • P
          Pentium
          last edited by

          Yes, this option I come real. Create a new interface for pfSense.
          Zyxel USG could work with virtual LAN the cards with options gates :(

          ISP will not cooperate …

          even solve the problem of two WAN IP to a specific local IP

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

            @Pentium:

            Yes, this option I come real. Create a new interface for pfSense.
            Zyxel USG could work with virtual LAN the cards with options gates :(

            ISP will not cooperate …

            even solve the problem of two WAN IP to a specific local IP

            Get a different ISP. One who knows how to properly route traffic.

            Or, another option is unless there's some reason to need both subnets, give those back and get a /28.

            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
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              @Derelict:

              Use an outside switch and two pfSense interfaces.
              One on 90.182.100.240 / 29  GW 90.182.100.241
              and one on  90.182.101.240 / 29  GW 90.182.101.241

              I need to add that even this is ugly and really should be two different broadcast domains to two different ISP interfaces. But it will probably work as long as there is not traffic going out and back in the same interface. If there is traffic between the two /29s you will probably have problems.

              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.