[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

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 ?
0
c_hockland
Asked:
c_hockland
1 Solution
 
QlemoDeveloperCommented:
You are trying all that from the server, or is there a workstation involved? I'll assume the former.
If you can ping the FW from server, you'll have to make sure there is no other route having precedence - unlikely with a host route (mask 255.255.255.255).
More likely, the issue is with the FW itself not forwarding traffic, or the other side of the FW doesn't. What's on the other side of the FW?
0
 
RafaelCommented:
The FW may be blocking ICMP traffic. See if you're allowing this.
0
 
c_hocklandAuthor Commented:
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 ?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
c_hocklandAuthor Commented:
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
0
 
QlemoDeveloperCommented:
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?
0
 
InfamusCommented:
route inside 0.0.0.0 0.0.0.0 192.168.3.35

It has to be the next hop IP address.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now