Re: ISPs can easily decrease net abuse

From: Laurent (laurent_at_faked.mblelop.com)
Date: 12/02/03 

Date: Tue, 2 Dec 2003 08:14:49 -0500

Juergen Nieveler wrote:
> JF Mezei <jfmezei.spamnot@istop.com> wrote:
>
>> With private address spaces and good routers with NAT, A
>> lot of businesses can operate with just a couple of
>> internet adresses.
>
> Unless they want to use VoIP or something else that
> doesn't really work with NAT. NAT has already killed the
> SpeakFreely-Project...

NAT kills many, MANY things. It almost cost us instant-messaging and IRC
file-sharing. Now these can all "somewhat" work...

>> Also, consider some of the huge blocks that were
>> allocated to a few companies early on. Digital Compaq
>> and HP each had their huge own block of IP adresses. HP
>> now has all of those, even though HP today has nowhere
>> near the same number of employees that the individual
>> companies had.
>
> Just think of the huge Class-A-chunks given to the US
> Army... every rifle has it's own IP. Wait, maybe they
> already planned for Landwarrior even back then :-)

Wasn't it the other way around? Like the army gave to ARIN most of the
address space except this huge class-a chunk? (I'm not sure how the
handover from DARPA to other agencies went along the years, but since the
'Internet' was a military project at first, I'm thinking it's them that
gave us the address space they don't want)

>> Every appliance and vehicle could have its own IP
>> address. So when you plug your fridge into your home LAN
>> it would have its own public IP address, a bit like its
>> serial number.
>
> Hence the invention of UPnP. Of course, you'll need to
> install a firewall on your fridge to prevent hackers from
> breaking into it :-)

"DAMMIT! Honey we got hacked! Someone stole our mayounnaise!"

Laurent

Relevant Pages

  • Re: EBS 2008, TMG and external firewall. Dont want double NAT
    ... This is done because Exchange is bound to the internal interface and leaves the external interface to be *completely* controlled by TMG...a good security guideline by the way. ... If you are disabling NAT then you'll need to change this from a publishing rule to an access rule, but it should still work fine. ... The first is an access rule allows traffic from the internal IP to the external interface and to the messaging server ... One of the default rules is an "internet access for all users" that allows http and https by default. ...
    (microsoft.public.windows.server.sbs)
  • Re: Routing and Remote Access NAT - I need to modify TTL
    ... with two interfaces: PUBLIC (internet) and PRIVATE ... use it as a gateway, they can access hosts on the PUBLIC interface, TTL is ... but the replay that comes back to the NAT ... They relay on the fact that client computers accept packets with TTL=0, ...
    (microsoft.public.windows.server.networking)
  • Re: Routing and Remote Access NAT - I need to modify TTL
    ... with two interfaces: PUBLIC (internet) and PRIVATE ... use it as a gateway, they can access hosts on the PUBLIC interface, TTL is ... but the replay that comes back to the NAT ... They relay on the fact that client computers accept packets with TTL=0, ...
    (microsoft.public.windows.server.networking)
  • Simultaneous NAT overload (internet) and NAT overlapping for IPsec
    ... There is a pure IPsec tunnel between SITE1 and SITE2. ... SITE1 also has an internet connection via ISP1 which is used to ... the NAT overload from SITE1. ... interface on ISP1) its "also" translating the addresses across to ...
    (comp.dcom.sys.cisco)
  • Re: Routing and Remote Access NAT - I need to modify TTL
    ... with two interfaces: PUBLIC (internet) and PRIVATE ... Hosts on the LAN successfully acquire IP addresses from the NAT SERVER ... use it as a gateway, they can access hosts on the PUBLIC interface, TTL ... They relay on the fact that client computers accept packets with TTL=0, ...
    (microsoft.public.windows.server.networking)