Multihoming Suggestions w/o at Least a /24?
An anonymous reader asks: "I work for a small company who is looking to get a multihomed Internet connection for redundancy.
The logical conclusion would be to get another internet connection to another provider. However, in the case of a primary connection failure, we need to be running BGP to have our internally-hosted sites still accessible to the Internet via the 2nd connection. The problem is that we only have a /28 (16 IPs), which is too small to make it past most route filters, and would then mean that we still couldn't be reached if the primary T1 is down. So, what's our options? (and no, lying and getting a /24 isn't a valid choice)"
The internet is not about fault-tolerance and ability to 'survive nuclear attack' for anybody who isn't an ISP, large corporation or government department.
/16'
That idea went out the window with the introduction of CIDR.
There were good reasons for this, primarily the unmanageable growth of route-tables.
IPV6 will never see the light of day because if IPV4 can't be routed economically out to the edge of the network, then increasing the address space by a large factor will not help matters.
There is no way around this except by removing CIDR for a decent proportion of the internet, but route-tables will of course baloon hugely.
So, while 'the people' want to be able to multihome etc. 'the backbones' don't want to have to scale up their routing capacity by a large factor.
Which all boils down to the conclusion that the powers-that-be on the internet have decreed 'thou shalt not multihome unless thy pockets are extremely deep and thou has at least a
This is unfortunately the way it is, and won't change under the current 'internet regime'.
I gots ta ding a ding dang my dang a long ling long