not to mention the cost in readdressing your entire network when you change an
upstream provider.
Nat was a fix to a problem of lack of addresses, however, the use of private
address space 10/8, 192.168/16 has allowed many to enjoy a simple network
addressing scheme.
I have and will continue
On Mar 24, 2014, at 9:36 AM, Alexander Lopez alex.lo...@opsys.com
wrote:
not to mention the cost in readdressing your entire network when you
change an upstream provider.
Nat was a fix to a problem of lack of addresses, however, the use of
private address space 10/8, 192.168/16 has
-Original Message-
From: Naslund, Steve [mailto:snasl...@medline.com]
Sent: Monday, March 24, 2014 10:48 PM
To: Owen DeLong; mark.ti...@seacom.mu
Cc: nanog@nanog.org
Subject: RE: misunderstanding scale
Look at it this way. If I see an attack coming from behind your NAT, I'm
I have seen this error whenever the destination server responds with some
strange response, I have mostly seen it with iptables mucking packets.
Problem occurs on the transport layer not the application so the application
has no idea what to make of it...
Original message
4 matches
Mail list logo