FW doesnt seem to route packets

[BSDsnob]

Hello I have a dev and a prod FW environment that I set up identically with the exception that one machine is NG and the other NGX. One interface is set up to be 65.x.x.x the other is internal 192.x.x.x

The 65.x.x.x connects to my router
The router has one interface 65.x.x.1 and the other 66.x.x.1
I have a client connected to 192.x.x.x
I have a default route set via voyager to 65.x.x.1


I can ping from the FW to 65.x.x.1 but not from the client in my dev environment. In my production environment I can ping from the client to the router just fine.

I have to conclude that the FW is not forwarding the packets to the router. Can anyone help me troubleshoot why I can not connect?

[dbedit]

Do a tcpdump or fwmonitor on your fw interface where packets are leaving! If your segments are directly connected you don't have to route anything.

[BSDsnob]

Thank you for your advise, I think I have it narrowed down to the cisco router. Trunking was not set up incase anyone has the same problem.

[usmanshaikh]

Hi,

Can you have a look at this issue and let me know the trunking that you enabled on the routers..

http://cpug.org/forums/showthread.php?t=3924


Cheers
Usman