A closer look at the Ethereal capture file reveals that echo requests are going
out on the proper (private) interface, but with the source ip of the public
interface.
curiouser an curiouser
S
All:
... maybe a mispost to the checkpoint list, .... Idunno ...
Checkpoint FW1 v4 (192.168.1.1) won't forward packets to an internal network,
172.16.21.0
route add 172.16.21.0 mask 255.255.255.0 192.168.1.100
the gw of choice ( 192.168.1.100) is an hp9308m switch, altho' I don';t see an
issue here, since Ethereal shows 'ping 172.16.21.63' going out the public
interface of the checkpoint box. Other routes on checkpoint to internal
networks work fine.
route add 172.16.21.0 mask 255.255.255.0 192.168.1.100 works fine on my PC,
192.168.1.222
Maybe this has nothing to do with checkpoint at all, any suggestions welcome
atb
S
Notice: This email was scanned by the C-SPAN InoculateIT AntiVirus Engine and
is virus free.
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to LISTSERV AT amadeus.us.checkpoint DOT com
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
fw-1-owner AT ts.checkpoint DOT com
=================================================
|
