This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrate RIPE IP range to new transit network

Hello

we have an RIPE IP-range

Currently we have ISP-A as Sponsoring-LIR and plan to switch to ISP-B
ISP-A uses part of our range as transit network

With ISP-B I would like to use an external transit network

E.g. (all "fictional" IPs):

 

Our range might be 7.7.7.0/8
ISP-A uses 7.7.7.0/30 as transit

-> resulting in an ETHx interface with e.g. IP in the 7.7.7.1/8 and gateway 7.7.7.2  All other IPs of the 7.7.7.0/8 as additional addresses on the UTM

ISP-B should use 80.222.111.29/29 as transit to announce your range.

Is it possible to migrate here without interrupt / small window?

How would I map that?

Like this:

  • Interface ETHx keeps the IPs
  • Interface ETHy gets ISP-B
  • ISP-B gets an IP in the transit network towards us as next hop
  • ETHy gets a default-gw assigned
  • ETHx gets its default-gw removed

Thanks for any help



This thread was automatically locked due to age.
Parents
  • OK, that's exactly what I thought you wanted, Ingo, but I wasn't "seeing" the picture.  Your plan should work.

    You could use Sachin's suggestion along with appropriate Multipath rules to smooth the transition, and then delete the items no longer needed afterwards.  Also, you may need new firewall rules for traffic coming from your private LANs to the Internet.  You will definitely need one or more firewall rules for traffic from the Internet to the 193 subnet.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Thanks for the confirmation :)

    It is basic routing to be honest, but it is better to check beforehand than to run into trouble and having to debug under timepressure

    Thanks so far

    Case closed

Reply Children
No Data