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

BGP and public IP

Scheduled Pinned Locked Moved pfSense Packages
8 Posts 3 Posters 3.2k 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.
  • P
    peco1si
    last edited by Sep 24, 2008, 1:02 PM

    Hi

    I have a problem with my bgp. As you see on the picture I have 2 WANs, DMZ and LAN.

    If I go out through WAN1 then my public IP is 1.1.1.1, if WAN1 is down then I go through WAN and my public IP is 2.2.2.2. My problem is that I always need to have one public address no matter which WAN I go through.

    How can I solve that problem?

    Tnx

    p.s. I know my english it's not the best but I hope you understand what is my problem
    pfsense.jpg
    pfsense.jpg_thumb

    1 Reply Last reply Reply Quote 0
    • P
      peco1si
      last edited by Sep 29, 2008, 6:11 AM

      Anybody?

      1 Reply Last reply Reply Quote 0
      • G
        GruensFroeschli
        last edited by Sep 29, 2008, 6:39 AM

        Maybe you should reformulate your problem.

        What i dont understand: you say "My problem is that I always need to have one public address no matter which WAN I go through."
        But that's the base principle of routing isnt it?
        –> No problem to solve...

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • J
          jahonix
          last edited by Sep 29, 2008, 8:38 AM

          I understand it that way that peco1si has a public IP 3.3.3.3 (DMZ) he wants to use no matter which WAN is available.

          How is inbound traffic supposed to know which route to take to reach your 3.3.3.3? You would have to update your external DNS to reflect this change.
          Do BGP/OSPF/RIP help here? (I guess I still have some reading/homework to do here. Which is which and what does it do…)

          1 Reply Last reply Reply Quote 0
          • J
            jahonix
            last edited by Sep 30, 2008, 9:31 AM

            Well, great, your subject had it already "BGP and public IP".
            Guess I better get some sleep…

            GruensFroeschli, do you have an idea?

            1 Reply Last reply Reply Quote 0
            • P
              peco1si
              last edited by Oct 15, 2008, 9:38 AM

              ok
              I solved problem with nat outbount
              Interface  Source  Source Port  Destination  Destination Port  NAT Address  NAT Port  Static Port
              WAN    192.168.5.0/24  *              *                    *                      3.3.3.3      *      NO

              I create virtual IP 3.3.3.3 as Proxy ARP, and now my problem is that I can't ping this IP from outside. why?

              tnx

              1 Reply Last reply Reply Quote 0
              • G
                GruensFroeschli
                last edited by Oct 15, 2008, 1:13 PM

                Because you cannot ping PARP type VIPs.
                http://forum.pfsense.org/index.php/topic,7001.0.html

                Use CARP instead.

                We do what we must, because we can.

                Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

                1 Reply Last reply Reply Quote 0
                • P
                  peco1si
                  last edited by Oct 17, 2008, 6:09 AM

                  great… now works everything  ;D

                  tnx you all

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    [[user:consent.lead]]
                    [[user:consent.not_received]]