I hate to do this as it is certainly outside the direct parameters of a Shorewall question, but my brain is pretzeled.
I have an office network connected to the internet and a branch office network also connected to the internet. I have an ipsec vpn tunnel setup and running between the two offices, and they are on two private subnets: Office A Office B 192.168.1.0/24 10.254.0.0/24 So far so good. Now for the fun. I have a private fiber link between the offices I would like to dedicate to VOIP traffic. The fiber link is essentially stateless (it's a switched fiber circuit), so I can configure it bridge or routed as I please. Each end of the fiber circuit simply presents as a normal CAT-5 connection which I can plug into a router or NIC. What I'd like to do is keep the existing VPN connection for DATA and add the new fiber circuit dedicated to VOIP between the offices. The place I'm stuck is architecturally. I'm trying to determine the best methodology to route both links between the two offices, one link for VOIP, and one link for DATA. Assuming I can concentrate both links on a single shorewall box on each end, would the multi-isp setup work in this situation? Am I on crack for even trying this? I apologize for broaching this topic here, but I know this list is full of folks who understand linux routing and might be able to point me in the right direction. If someone wants to contact me directly on a consultative basis, I am game for that if this is too far outside the purpose of this list. Any suggestions other than "get lost" would be greatly appreciated. -- Keith Mitchell CTO Productivity Associates, Inc. 5625 Ruffin Rd STE 220 San Diego, CA 92123 858-495-3528 (Work) 858-495-3540 (Fax) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
