Welcome, Guest. Please login or register.
Did you miss your activation email?
Sunday 01 December 2024, 06:55:38 am

Login with username, password and session length

Download the latest community FREE version  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Handling a subnet conflict.
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Handling a subnet conflict.  (Read 6428 times)
trymes
Full Member
***
Offline Offline

Posts: 36


« on: Thursday 15 September 2011, 11:00:20 pm »

OK, so I have a subnet conflict. Renumbering one subnet or the other would make the most sense, but is not an option.

Setup:

Site1a has LAN 192.168.0.0/24 and a connection to Site2 via IPSec.
Site1b has LAN 10.3.0.0/16 and is connected to Site1a via ethernet at 192.168.0.43 (BLUE).
Site2   has LAN 10.3.0.0/16.

I have gotten around the subnet conflict between Site1b Site2 in the past using IPSec between Site1a and Site1b over the internet. I used a dummy subnet in the IPSec setup (10.33.0.0/16) for Site1b and configured a NAT rule at Site1b that mapped packets to/from 10.33.0.0/16 to/from 10.3.0.0/16. This worked quite well.

Now, I have replaced the Site1b router with Endian and replaced the IPSec tunnel with an ethernet connection that is assigned to BLUE with IP address 192.168.0.43. I have assigned a static route on Site1a's router that directs any traffic for 10.33.0.0/16 to 192.168.0.43, the BLUE interface for Site1b.

I thought that I should be able to use a destination or source  NAT rule using the "Map Network" option, but I have not been able to make that work.

What am I missing here?

Tom
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.055 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com