Hi Maike,
Mike Knisely wrote: > > Hmmm.... Interesting. Can you expand their Green address space to a > larger range? For example, if they were 192.168.23.0/24, you could make > them 192.168.22.0/23. That would include the 192.168.22.0/24 and > 192.168.23.0/24 networks. Never thought of that. I will put it in my toolbox for future use. We came up with an alternative way of doing it. (The IT dept is not too sophisticated and trying to get their network guys to change this would have been a problem.) I am not sure what we could have done if we did not source nat between the two green ips. I quess the main problem here was that endian was not their default gateway hence routing rules where not setup to route to the alternative green/red/orange network addresses other than to send traffic out to their current default gateway. Source NAting the green and red ips if necessary is a good technique to get a router working when you do not control the default gateway. ----- http://www.jumpingbean.co.za Jumping bean your java and linux experts http://www.cyberconnect.co.za Cyber Connect - More than just broadband -- View this message in context: http://www.nabble.com/Mutliple-Green-Network-IP-and-OpenVPN-routing-tp20564014p20595476.html Sent from the efw-user mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
