BGP and LAN routable IP



  • I have a failover internet connection , configured via BGP, effectively multi-homing to the same location.  So, I have two fiber internet connections with normal IP's assigned  , then I have a IP subnet configured via BGP that can exist on either of those two connections .

    I now want to run SIP , but, to do so I need a WAN IP on the Phone system that has to sit behind the pfSense as it coordinates the BGP.  I got a /30 assigned, and I announce it , but I am missing something as it doesn't route thru yet.

    So 65.151.37.224/30 is configured on my LAN as a proxy ARP (not sure this was the right choice) 65.151.37.225 will be the phone system , on the LAN interface.

    65.151.24.26 is my primary connection its gateway is ...25  , 65.151.24.30 is my failover with ...29 for its gateway .

    BGP is 65.151.28.1 /24 , which can be on the primary or failover.

    When I tracert or ping it seems to get confused at my primary gateway.

    tracert 65.151.37.224

    Tracing route to 65.151.37.224 over a maximum of 30 hops

    1    <1 ms    <1 ms    <1 ms  10.1.1.254
      2    1 ms    1 ms    1 ms  tuk-edge-14.inet.qwest.net [63.228.222.121]
      3    1 ms    1 ms    1 ms  tuk-cntr-11.inet.qwest.net [205.171.11.70]
      4    1 ms    1 ms    1 ms  69.8.221.42
      5    1 ms    1 ms    1 ms  65.151.24.26
      6    1 ms    2 ms    2 ms  65.151.24.25
      7    1 ms    1 ms    1 ms  65.151.24.26
      8    1 ms    1 ms    1 ms  65.151.24.25
      9    1 ms    1 ms    1 ms  65.151.24.26
    10  148 ms    1 ms    25 ms  65.151.24.25
    11    1 ms    1 ms    2 ms  65.151.24.26
    12    2 ms    2 ms    2 ms  65.151.24.25
    13    1 ms    1 ms    1 ms  65.151.24.26
    14    1 ms    1 ms    1 ms  65.151.24.25
    15    1 ms    1 ms    1 ms  65.151.24.26
    16    2 ms    2 ms    2 ms  65.151.24.25
    17    1 ms    1 ms    1 ms  65.151.24.26
    18    1 ms    1 ms    1 ms  65.151.24.25
    19    1 ms    1 ms    1 ms  65.151.24.26
    20    1 ms    1 ms    1 ms  65.151.24.25
    21    1 ms    1 ms    1 ms  65.151.24.26
    22    1 ms    1 ms    1 ms  65.151.24.25
    23    1 ms    1 ms    1 ms  65.151.24.26
    24    16 ms    7 ms    2 ms  65.151.24.25
    25    1 ms    1 ms    1 ms  65.151.24.26
    26    2 ms    2 ms    1 ms  65.151.24.25
    27    1 ms    1 ms    1 ms  65.151.24.26
    28    1 ms    1 ms    1 ms  65.151.24.25
    29    1 ms    1 ms    1 ms  65.151.24.26
    30    1 ms    1 ms    1 ms  65.151.24.25

    Trace complete.

    ping 65.151.37.224

    Pinging 65.151.37.224 with 32 bytes of data:
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.

    Ping statistics for 65.151.37.224:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    ping 65.151.37.224

    Pinging 65.151.37.224 with 32 bytes of data:
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.
    Reply from 65.151.24.25: TTL expired in transit.

    Ping statistics for 65.151.37.224:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Any help would be appreciated



  • you may be also like it k-12 tool is a free online tool which provides help to college and school district technology directors, state leader who can view broadband services and bandwidth information for school. All IP Address ranges are technically routable. that a private network with an RFC 1918 IP range can reach the public internet without needing these private network routers to be published. You can use them with routing protocols like OSPF, BGP. https://babasupport.org/routers/tp-link-customer-service/778 provide you best solution for all technical issues that may be the router, software etc.


  • Banned

    This post is deleted!

Log in to reply