-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sean Covel wrote:
> Thanks for your response. Tom Eastep was correct, it was a stale > RFC1918 file. The address that the request was coming from USED to be > in the RFC1918 range but was recently re-assigned. We should be clear here. The address was not in the RFC1918 range but rather was listed in the rfc1918 file (big difference). That is because with Shorewall versions prior to 2.0, the rfc1918 file did double duty in that it listed both RFC 1918 reserved addresses *and* bogon address ranges. Beginning with Shorewall 2.0, these two lists were split so that the rfc1918 file now lists just the RFC 1918 reserved ranges and the bogons file lists the rest. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBdn1gO/MAbZfjDLIRAq17AJ901x22hfWAQfI7CywYjYsik7ZLEwCgm1qU LfpVp8/pV3E/yjhsmZE3Fkw= =0aks -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
