[c-nsp] single static ip address for customer(s)

[Michael Sprouffske]

I would agree with Nick about keeping your ip address's at a pop for cleaner route tables. I do in some places advertise /32 instead of the blocks on 2 of my routers. We started to do that for business customers and found that we aren't liking it. It's a pain dealing with the same block on 2 routers.

Sent from my iPhone

On Jun 21, 2012, at 4:00 PM, Nick Hilliard <nick at foobar.org> wrote:

> On 21/06/2012 23:18, Aaron wrote:
>> In other words, they buy a single static ip address out of a class c that is
>> able to be switched and routed in that area of the network where they
>> currently reside..BUT, then they want to move locations and KEEP their
>> existing static ip.
> 
> this is a contractual problem, not a technical one.
> 
> Look, if you want to handle this sort of thing with ibgp, there's no reason
> not to, other than money and the fact that it doesn't scale well.  I'm sure
> there are plenty of router vendors who would be happy to sell you kit
> capable of handling millions of prefixes.
> 
> But seriously, if you sell /32s, then put a note into the contract to say
> that they are limited to specific PoPs and if the customer changes
> location, the address will change too.  Or alternatively, teach your
> customers about dynamic DNS.  Or sell / bundle them a VPS instead.  Linux
> containers are _great_ for this sort of thing.   There's really very little
> reason to have static IP addresses for your home account.
> 
> [incidentally, Class Cs stopped existing in any meaningful way in ~1993 -
> 1994.  You probably meant a /24.]
> 
> Nick
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/