p2p addresses for point-to-point connections with customers

• Previous message (by thread): p2p addresses for point-to-point connections with customers
• Next message (by thread): p2p addresses for point-to-point connections with customers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Well if you’re null routing the /30 then you or them should have a /32 or larger for NAT or no RFC space behind it. 

-----Original Message-----
From: Tassos Chatzithomaoglou [mailto:achatz at forthnetgroup.gr] 
Sent: Wednesday, 7 November 2012 2:45 a.m.
To: Dobbins, Roland
Cc: NANOG list
Subject: Re: p2p addresses for point-to-point connections with customers

Roland, how do you handle customer requests regarding the remote management of their devices?
i.e. if the customer wants to do any kind of management (ssh, snmp) from outside his router, he must use our infrastructure address (which is configured on his router) as a destination.
Generally, the customer might want to use this wan address for many other things which you shouldn't actually care, since it's his router.

--
Tassos


Dobbins, Roland wrote on 06/11/2012 14:34:
> On Nov 6, 2012, at 7:31 PM, Tassos Chatzithomaoglou wrote:
>
>> Only specific types of icmp messages?
> That, plus the routing session (if any) with your customer, plus anything else that's situationally-specific (GRE tunnel termination, etc.).
>
> ----------------------------------------------------------------------
> - Roland Dobbins <rdobbins at arbor.net> // 
> <http://www.arbornetworks.com>
>
> 	  Luck is the residue of opportunity and design.
>
> 		       -- John Milton
>
>
>
>

• Previous message (by thread): p2p addresses for point-to-point connections with customers
• Next message (by thread): p2p addresses for point-to-point connections with customers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]