Hi Marco, You are asking too much for 30M of business worldwide. Just outgoing connections redundancy is enough for 99% of them. Older times, they have DMZ and their own Web server. It does not make sense now - server may be in the cloud, but mostly it is not needed - they have an account on some platform. Eduard -----Original Message----- From: Marco Moock via NANOG <nanog@lists.nanog.org> Sent: Thursday, November 6, 2025 14:08 To: North American Network Operators Group <nanog@lists.nanog.org> Cc: Marco Moock <mm@dorfdsl.de> Subject: Re: Artificial Juniper SRX limitations preventing IPv6 deployment (and sales) On 06.11.2025 07:18 Vasilenko Eduard wrote:
The first time I configured Cisco 2500 with ISP redundancy in 1998. It worked fine: If the link to the primary ISP was down, the office (50 employees company) still have connectivity through the other link. And yes, the office network was not flat - it had many subnets.
In case of failure all the connections fail and need to be restablished. That is not something I call redundancy. If you host services inside such a network, both IP addresses must be present in the DNS and that means clients can use any and take some time until they notice the failing connection. An established connection will break this way too. Redundancy is different and means your network is connected by 2 ISP - independent of their address ranges. _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/JKKZN4DX...