Link to home
Start Free TrialLog in
Avatar of c_hockland
c_hocklandFlag for Greece

asked on

issue with route add

I have a server connected to the Fw

server is also connected to ISP router ( as default GW)

i have done

route add x.x.x.x mask 255.255.255.255 y.y.y.y ( FW interface )

but cannot ping the other side of the FW
tracert times out on the fist hop
server can ping FW ( same subnet)

when i do route print i see the route

any ideas ?
ASKER CERTIFIED SOLUTION
Avatar of Qlemo
Qlemo
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The FW may be blocking ICMP traffic. See if you're allowing this.
Avatar of c_hockland

ASKER

the other side of the FW is 10.221.64.2
inside 192.168.3.35


how can i check if it forwards traffic from 3.35 to 64.2 ?
actually i have

route inside 0.0.0.0 0.0.0.0 10.221.64.1  ( 64.1 ) is the router after the FW

so it does FW traffic from inside to the router
It might help if we knew the brand of the FW, and the devices behind it (on 10.221.64.x). You'll have to check step by step each device which is involved in the route.

We'll assume you can reach the FW fine. Then you'll need to set up a route for 10.221.64.0/24 to it, and test both IPs. Then the device behind those, which you have set the host route for. It also helps to make a traceroute on the target device towards your own FW's IPs, then your server.
Of course and in any case you will need the route back, too - is that set up on the target network?
Avatar of Infamus
Infamus

route inside 0.0.0.0 0.0.0.0 192.168.3.35

It has to be the next hop IP address.