Avoiding redundant rules for source based routing.

We use imagestream routers. We have two bandwidth circuits. One is for business customers, one is for residential customers. The resi customers all go out the default route. we have a table 100 for the business customers that sends their traffic out the business circuit with a source rule.

We had alot of issues with communications between the business and residential customers, as well as the business to business customers, however the residential customers could communicate fine amongst themselves.

We were seeing alot of loops.

It turned out that we had routes TO the business customers listed in the default ruleset. So the outside world could communicate with them no problem, but the internal routing wasnt happening.

We ended up duplicating the routes to the business customers instide the table 100 rules, and that got them communicating just fine amongst each other. However we still had loop between residential and business, which required duplicating all the routes to the residential customers inside of table 100.

Without static routes like this the traffic would loop between us and our upstream.

Now the setup we have, with both rulesets duplicated works, but seems labor intensive to mainatain and rather cumbersome.

There has to be a more appropriate solution (non dynamic) for the syntax in the rulesets here.

I hope I made myself clear.