I have a network with the main router being the internet facing gateway. I have added another router gateway with its WAN connected to an untrusted LAN network.
the untrusted LAN and WAN have static IP's in the 192.168.222.x range.
the trusted network is in the 10.168.222.x range , with the LAN side of the main gateway being 10.168.222.1 and the new router being 10.168.222.12 .
I added a static rule to the routing table on the main gateway.
destination 192.168.222.0
mask 255.255.255.0
gateway 10.168.222.12
metric 0
interface LAN
the new router has the 192.168.222.0 rule in its routing table and knows it is the WAN , but I even tried adding firewall and IP masquerading rules pointing to the WAN just in case.
the new router will ping the 192.168.222.x network fine , also the 10.168.222.x .
tracert to 192.168.222.x goes to the main gateway and is flung out its WAN to get lost on 'tinternet.
WTF ? I has assumed any addressed packets to the 192.168.222.x network would arrive at the gateway and get passed onto the LAN of the new gateway where they would be passed to the WAN then onwards to the machine in question.
any ideas as to where I am fcuking up ?


Reply With Quote

