Thank you for your thoughtful answer. It appears I didn’t ask a very good
question though :)
The reason for the VPN is because the satellite site doesn’t have an option for
BGP and only has 1 public IP available and we need about 40. The extra latency
associated with the tunnel isn’t to much of
The OpenVPN solution you are mentioning. Is IMHO only really nessesary og you
have plans for further sites in the near future and do not want to renumber
and/or change your BGP configuration in regards to how you peer with $ISP.
A possible option is to announce both Main sites /24 and a cover /2
Run BGP with $ISP on both Main and Satellite site... Just announce a unique /24
prefix from each site. No need to run VPN, unless you are using private
addresses.
Ensure to have ROA & route objects correctly registered at RIR database.
--
have you enabled IPv6 on something today...?
Chriztoff
Hello all,
I’ve been debating with myself the best way to handle this situation. I have a
two site deployment with a /23 prefix available. I wish to assign 1 /24 to site
one (Main), and 1 /24 to site two (Satellite) and then link them via OpenVPN. I
am debating the pro’s and con’s of running bi