OK, good luck with it... For only 5 or 10 sites, I'd set the default gateway to the internet out the T1, and then put a static route for each known IP pointing to the Metro-E router address ... But if the Sonic Wall will do it for you, go for it.
Erik Goldoff IT Consultant Systems, Networks, & Security -----Original Message----- From: Andy Ognenoff [mailto:andyognen...@gmail.com] Sent: Thursday, April 02, 2009 12:38 PM To: NT System Admin Issues Subject: RE: OT: Bandwidth Splitting? >How many sites/addresses do you forsee wanting on the Metro-E ? I >still think, if a reasonable number of sites, that a static routing >table would be pretty simple to setup I'm thinking something like 5-10 sites on the Metro-E for now. In looking at the SonicWall policy based routing (thanks Phil!) in combination with their dynamic address objects and groups, I think I can accomplish what I'm looking for with minimal upkeep in the future. In theory, I would just add a dynamic address object for the site I want and then add it to an address group which is what I use for the policy based route. I haven't tested it yet but I think that would do the trick. Everything not assigned via the policy would go out over the T1. And using a dynamic address object should make it work even if site's IP changes. Of course this is all in theory so we'll see what happens when I try it out. - Andy O. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
