On Mon, 2008-06-30 at 20:45 -0700, Tom Eastep wrote:
> Brian J. Murrell wrote:
> > On Mon, 2008-06-30 at 16:45 -0700, Tom Eastep wrote:
> >> I think that adding routing rules for things that need to use the main 
> >> table 
> >> is more straightforward.
> > 
> > Indeed, if you know ahead of time and are able/willing to reload your
> > firewall to deal with changes.
> 
> Brian,
> 
> You're being deliberately dense.

I think in fact just failing to communicate effectively.

> There is no reason to 'reload your firewall 
> to deal with the changes'.

As long as I have already planned for them in the route_rules.

> You only have to understand the nature of the 
> changes that your applications might apply to your main table and supply 
> routing rules *in advance* that anticipate those changes.

Right.  Understood completely.  My "reload your firewall" comment was in
response to the scenario where something I had not planned for ahead of
time comes along and thus I have to update the route_rules
configuration.

> I have been down this road many times; I've been thinking about the problem 
> a lot longer than you have and I don't believe that there is a simple 
> answer.

Indeed.  And I recognize that, which is why I put my idea up for
criticism.  I knew if there were flaws with it, I could count on the
collective experience here to find them.

> I'm still willing to be convinced; but the 'provider tables contain 
> only default routes' approach is a dead end as far as I'm able to see.

Yeah, it very well could be.  I do recognize you are the word of
experience here.  But sometimes even hairbrained proposals sometimes
make the experienced people think in ways or about solutions they had
not considered before.  I'll keep thinking about it.  :-)

b.

Attachment: signature.asc
Description: This is a digitally signed message part

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to