We have seen the same thing. The actual NAT'd address is correct so this
appears to be only a logging (or viewer) problem.
-----Original Message-----
From: Little, Craig (SSI-SIAP-NP5) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 16, 2000 11:15 PM
To: Firewall List (E-mail)
Subject: [FW1] XlateSrc incorrect
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have just noticed that the XlateSrc column in the Log Viewer is
reporting the incorrect address for my internal addresses.
I have set up a proxy arp for two external addresses which belong to
our Telco, so that they can perform Proxy RADIUS authentication on
our behalf. Our internal range is 156.149.0.0 (useless information,
since it is not routable on the Internet!), and the XlateSrc field is
reporting addresses in the range 28.149.x.y, which is suspiciously
156-128.
Has anybody else experienced this? Is there a solution for it - I'm
not sure if there are any further implications.
Kind Regards,
Craig Little BSc, CPD, CPI, SCJP, CCSA, CCSE
Inter-Networking / Security Consultant
Shell Services International
Phone: +64 4 462 4661
Fax: +64 4 463 4060
Mobile: +64 21 37 5858
mailto:[EMAIL PROTECTED]
http://www.shellservices.com
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOZquqskKSVawnurJEQIvWQCcC/rPggROoqGqK0TJSjUr7b0bFEEAoL0W
2sh1VnO//WyyZeJmiMXBPncY
=QuUb
-----END PGP SIGNATURE-----
<<Craig Little (E-mail).vcf>> �
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
