> However, if someone is adamant that you need to set up network connectivity > between machines with such an unfriendly combination of IP addresses, I > suggest you simply set up multiple host-specific routes on the netflter > machine, telling it where to find each different 192.168.0.* destination > address, and don't have a standard 192.168.0.0/24 route on that system. Unfortunately, this is exactly what I can't do :( This is because there are two of each 192.168.0.* IP address. The original destination IP address has to taken into account when determining whether packets route through eth1 or eth2. I like the idea of MARKing the packets before they are routed. DNATing them and then routing based on how they were previously MARKed. As I get more comfortable with this (assuming nobody claims I'm trying to do the impossible), I'll try and put together some rules I might use to accomplish this. Al This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify Thales Underwater Systems on +44 1963 370 551. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person.
