With the changes, neither the local Site One routing nor the 102 subnet access from Site Two is working yet. The tunnel still however routes 10.100.100.0 subnet traffic just fine. My current config is as follows, any thoughts? The monowall at Site Two can ping addresses on the 10.100.102.0 subnet through the WAN interface, but it seems like it can even ping addresses that aren't actually in use. No computers actually behind the monowall at Site Two on the 192.168.20.0 subnet can ping any of these addresses, valid or not. The LAN port on the monowall at Site One can ping any LAN subnet addresses, and the OPT1 port can ping any OPT1 subnet addresses.
---Site One:--- Interface(s): eth0 (LAN): 10.100.100.6 /24 eth1 (WAN): (WAN Address of Site One) eth2 (OPT1): 10.100.102.2 /24
IPSec Tunnel: 10.100.100.0/22 (I had to change this from "LAN" to "10.100.100.0/22", as otherwise the tunnel did not come up) 192.168.20.0/24 WAN (WAN Address of Site Two)
Firewall Rule(s): [Tab, Protocol, Source, Port, Destination, Port, Description] (LAN) * LAN net * * * Default LAN -> any (OPT1) * OPT1 net * * * Default OPT1 -> any
---Site Two:--- Interface(s): eth0 (LAN): 192.168.20.1 /24 eth1 (WAN): (WAN Address of Site Two)
IPSec Tunnel: LAN 10.100.100.0/22 WAN (WAN Address of Site One)
Firewall Rule(s): [Tab, Protocol, Source, Port, Destination, Port, Description] (LAN) * LAN net * * * Default LAN -> any
|