I am deploying Bering 1.2 systems as firewalls/VPN tunnel endpoints to build what they call extruded subnets in freeswan jargon
Here a little bit of ASCII art
client net 10.230.60.0/24 (for historical reasons) � 10.230.60.1 Bering / customer VPN endpoint xx.xx.xx.xx (any old public address) | internet | xx.xx.xx.xx (any old public address) Bering / outer firewall / NAT / VPN endpoint 192.168.180.1 | DMZ 192.168.180.0/23 | 192.168.180.2 Bering / inner firewall / 2 or 3 NICs 192.168.52.1------------- | | | internal subnet | 192.168.52.0/22 | many extruded subnets in the 10.230.xx.xx range
The idea is to route the path to the various extruded subnets from the tunnel endpoint on the outer firewall through the DMZ wire to the inner firewall and then to the respecive subnet.
- I probably need to assign ip aliases for each subnet to the NIC connected to the extruded subnets.
- I need to add routes for each subnet on the outer and the inner firewall
Is there a canonical way to add many routes and many ip aliases to such a box? Does this make sense at all?
Thanks for comments Erich
THINK P�ntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
