[25845] in resnet
Re: NAT and RIAA
daemon@ATHENA.MIT.EDU (Jason Healy)
Wed Jan 26 22:53:47 2011
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Transfer-Encoding: 8bit
Message-ID: <E7D6E192-1EE7-48BC-832A-BD05C783EDF5@logn.net>
Date: Wed, 26 Jan 2011 22:53:25 -0500
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: Jason Healy <jhealy@logn.net>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <4D406B72.6030309@scranton.edu>
We also log PAT/NAT so we can correlate IPs on the inside and the outside. I have a question for those of you that are doing this. Have you noticed that the ports in the RIAA reports don't always match up correctly? For example, I often get notices that identify an IP and a port, but the port they list does *not* match the external IP, though it *may* match an internal one that was NATed to that external IP.
What do you do in this case? Do you tell the RIAA that they need to provide a complete 100% match, or do you assume that the user with the matching internal port is the one you're looking for?
Jason
--
Jason Healy | jhealy@logn.net | http://www.logn.net/
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
