[105189] in North American Network Operators' Group
Re: .255 addresses still not usable after all these years?
daemon@ATHENA.MIT.EDU (Tim Durack)
Fri Jun 13 23:20:46 2008
Date: Fri, 13 Jun 2008 23:19:06 -0400
From: "Tim Durack" <tdurack@gmail.com>
To: nanog@merit.edu
In-Reply-To: <20080614112119.a364bcbe.nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org>
Errors-To: nanog-bounces@nanog.org
Funny this discussion surfaced now - I got bitten by this recently.
Was using .255 for NAT on a secondary firewall. When the primary
failed over, parts of the Internet became unreachable...
Tim:>
On Fri, Jun 13, 2008 at 9:51 PM, Mark Smith
<nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org> wrote:
> On Fri, 13 Jun 2008 13:43:36 -0700
> Kameron Gasso <kgasso-lists@visp.net> wrote:
>
>> Christopher Morrow wrote:
>> > go-go-actiontec (vol sends those out, god do they suck...)
>>
>> Crappy CPE's are exactly why we don't hand out .0 and .255 addresses in
>> our DHCP pools. :(
>> --
>> Kameron Gasso | Senior Systems Administrator | visp.net
>> Direct: 541-955-6903 | Fax: 541-471-0821
>>
>
> We avoid them because in the interest of "security", customers who
> would be assigned .0 and .255 have trouble accessing their online
> banking and other financial websites. With IPv4 address space running
> out, we'll probably inevitably have to start handing them out and then
> get our customers to complain to their bank etc.
>
>
> Regards,
> Mark.
>
> --
>
> "Sheep are slow and tasty, and therefore must remain constantly
> alert."
> - Bruce Schneier, "Beyond Fear"
>
>
