New local routes list

My list is static and old, but it's worked till now. With MWeb cutting off local transits (which I support), I couldn't access news24 and the other MWeb hosted sites, because my router was sending the requests to my local only account, so I ditched all local routing. Now I'm ready for the difficult task of updating my RouterBoard route list (the last time I did it was was ages ago, and I followed a step by step guide), but where do I get a SAIX-user specific list?

What side of the iron curtain is this one this one taken from? Does anyone know which ISP needs which list? Are ISP specific lists even available? Is there an easy way to modify the list for a specific ISP? Thanks in advance.

****, because of Telkom and MTN's stubborn greed, we now need ISP specific local route lists. GIVE IT UP, IDIOTS AT TELKOM AND MTN, YOU LOST, MWEB WON, NOW PEER FREELY OR HAVE EVERYONE HATE YOU MORE THAN THEY ALREADY DO (WHICH I DIDN'T THINK WAS POSSIBLE).

Routes are routes, you don't need 'ISP specifc routes'.

They all update them so if you keep your route list fairly up-to-date you shouldn't have any issue however Mweb have been known in the past for not properly announcing their routes to other networks.

I use these local routes

If I'm on MWeb, news24 is local, but it's international from SAIX, so no, not all routes are the same any more. Unless I'm missing something, but I don't think so.

Drunkard #1 said:

not all routes are the same any more

Click to expand...

Precisely, that's why you need to keep your list updated. It's not a once-off thing.

I know I need to update them, but the list of local routes that works for IS customers, is going to have routes the aren't local for SAIX customers, because IS peers with MWeb, and SAIX doesn't. I need a SAIX list.

Non-Mweb-Peered Local Routes

Hi Drunkard #1,

You're certainly not the only person being affected by this issue using our local routes list, others have emailed asking similar questions.

It's open to debate, though the easiest approach which wouldn't require altering existing routing scripts would be to regard all Mweb owned IP ranges as being international. This, however, would affect Mweb-peered networks from regarding the Mweb IP ranges as being local. So another approach would be to release "non-peering" routes lists, which excludes Mweb IP ranges, which would leave the current local routes lists in tact for users on Mweb-peered networks.

Non-Mweb-Peered Local Routes

The following routes databases exclude Mweb owned IP ranges:
CIDR: http://developers.locality.co.za/routes-nonpeered.txt
Subnet: http://developers.locality.co.za/routes-nonpeered-rs.txt

I didn't mean to get you working on a Saturday, but thanks. Hope it wasn't too much trouble.

Drunkard #1 said:

I didn't mean to get you working on a Saturday, but thanks. Hope it wasn't too much trouble.

Click to expand...

Not at all, I'm glad I could be of assistance — and I hope it'll benefit others too.

Thanks Locality!

Now I have to update my Traffic Splitter app to fetch your new list