Subnets won't see my Lan after Raptor Installation

[julianf]

Hi,

We have just rolled out Raptor Firewall in our network. We have a 128K diginet line to ISP. We also have a diginet line going out to a remote subnet. Our Lan runs on the internal range 172.29.180.0...the remote site is on 172.18.3.0.

This is the layout: WWW
!
128K Line
!
Router A
!
Firewall
!
Main LAN (Subnet 172.29.0.0)
!
Router B
!
64K line
!
Router C
!
Remote Subnet (172.18.3.0)

Now....we can ping them (the remote subnet) from our side...but we are having problems with them pinging us...they can ping our Firewall and the router B, but they cannot ping our servers or beyond the Firewall. I'm not sure if the problem is with Raptor...we have tried adding rules and redirections...but to no avail.

On the main lan..the workstations and server have the default gateway which is the Firewall. It seems as if when the remote site pings us...they get redirected to the firwall....and then it seems that the firewall doesn't know where to send the request!

Any advise would be appreciated.

Julian

 

[zbrownmd]

it's possible that you need to add a route to the firewall point to the remote subnet using you wan router as next hop

in nt/2k
route -p add 172.18.3.0 mask 255.255.0.0 (or 255.255.255.0) ip addr of router b

 

[julianf]

Thanx...

In the need it was routing that did the trick. I actually had to add the route on the servers that the clients on the remote lan needed to access. They could ping us...but the ping could not find thye way back, as it eventually got stuck at the firewall - so we addedd routes on all the servers....This worked.

Thanx,

Julian