Hi All,
Untangle newbie here... Hoping you guys can help me out!
We have two separate networks connected via a dedicated 100Mb fibre link.
SiteA Network hosts our internal servers
SiteB Network needs to access our internal servers
NetworkA is 172.16.x.x / 22
NetworkB is 192.168.90.x / 24
We have configured a network connecting the two together 10.6.5.x
Eth2 on Untangle at SiteA has been configured with an IP of 10.6.5.1
We have installed a Cisco 2811 at SiteB which we have configured with an IP of 10.6.5.2
Static Routes have been created at SiteA (Untangle) as per below:
Target 192.168.90.0 Netmask 255.255.255.0 Gateway 10.6.5.2
Static Routes have been configured at SiteB as per below:
route add 172.16.0.0 MASK 255.255.0.0 192.168.90.200
route add 10.6.5.0 MASK 255.255.255.0 192.168.90.200
192.168.90.200 is the internal IP assigned to SiteB Cisco 2811.
We are able to ping between the networks i.e.:
From SiteB we can Ping SiteA Gateway 172.16.1.254 (Untangle)
From SiteA we can ping SiteB Gateway 192.168.90.200 (Cisco 2811)
Where I am stuck is the fact that from SiteB I cannot ping beyond the Untangle gateway of 172.16.1.254 i.e. 172.16.1.29
After trawling through the forums I saw people having similar issues when using eth2 on Untangle and they were advised they needed to add packet filter rules to pass the traffic between eth2 and eth1
Please see configured Packet Filter rules attached.
After adding the Packet Filter Rules I am still unable to ping, telnet etc to anything located on the SiteA internal Network from SiteB.
Can someone steer me in the right direction as to why I may not be able to get to anything inside the Internal Network of SiteA from SiteB
Do I need to add an Alias IP to eth2 for the Internal Network on Untangle?
Look forward to your feedback. Cheers
Packet Filter Rules.jpgEth2 Interface.JPGEth1 Interface.JPG
Untangle newbie here... Hoping you guys can help me out!
We have two separate networks connected via a dedicated 100Mb fibre link.
SiteA Network hosts our internal servers
SiteB Network needs to access our internal servers
NetworkA is 172.16.x.x / 22
NetworkB is 192.168.90.x / 24
We have configured a network connecting the two together 10.6.5.x
Eth2 on Untangle at SiteA has been configured with an IP of 10.6.5.1
We have installed a Cisco 2811 at SiteB which we have configured with an IP of 10.6.5.2
Static Routes have been created at SiteA (Untangle) as per below:
Target 192.168.90.0 Netmask 255.255.255.0 Gateway 10.6.5.2
Static Routes have been configured at SiteB as per below:
route add 172.16.0.0 MASK 255.255.0.0 192.168.90.200
route add 10.6.5.0 MASK 255.255.255.0 192.168.90.200
192.168.90.200 is the internal IP assigned to SiteB Cisco 2811.
We are able to ping between the networks i.e.:
From SiteB we can Ping SiteA Gateway 172.16.1.254 (Untangle)
From SiteA we can ping SiteB Gateway 192.168.90.200 (Cisco 2811)
Where I am stuck is the fact that from SiteB I cannot ping beyond the Untangle gateway of 172.16.1.254 i.e. 172.16.1.29
After trawling through the forums I saw people having similar issues when using eth2 on Untangle and they were advised they needed to add packet filter rules to pass the traffic between eth2 and eth1
Please see configured Packet Filter rules attached.
After adding the Packet Filter Rules I am still unable to ping, telnet etc to anything located on the SiteA internal Network from SiteB.
Can someone steer me in the right direction as to why I may not be able to get to anything inside the Internal Network of SiteA from SiteB
Do I need to add an Alias IP to eth2 for the Internal Network on Untangle?
Look forward to your feedback. Cheers
Packet Filter Rules.jpgEth2 Interface.JPGEth1 Interface.JPG
