Hello, IsThisThingOn & Welcome to LQ.
As a general rule, it's good to put a lot of information with your question, but I think I can deal with this. In an IPV4 address aaa.bbb.ccc.ddd, routing was designed to work logically. It was envisaged that the 'd' section was hosts. So your route travels from the left.
The IP scheme you lay out is non standard and makes a total mess of standard routing protocols and it is just going to cause mayhem in every area. I would advise fixing it. You say it's out of your control, but no company wants a system that is incompatible with standard protocols.
Challenge the IP naming system. Raise hell, and send memos. Dream up ways of being awkward about this and use them. If it has to be implemented as is, use your 200+ routes. Leave plenty of dire warnings on paper about breaking standard protocols. Find them routing protocols to read. Guys setting up IPV4 numbering schemes should have the rule book.To route them sanely, you'd have to swap the 'ccc' & 'ddd' like this
224.100.200.nnn
224.100.201.nnn
224.100.202.nnn etc.
The reason for this approach was that the first routing programs were lazy as hell. If line 1 matched, they didn't read line 2, etc. Everything since is compatible.
Last edited by business_kid; 11-11-2021 at 01:08 PM.
|