If you're talking about assigning RFC1918 space to router interfaces that transit traffic, a la @home, keep in mind that this can break PMTU-D, and makes for messy (and slow) traceroutes when external hosts try to resolve unresolvable reverse DNS entries. If you're talking about giving the workstations in your NOC private IP addresses, using NAT to access your core routers, I see no more a problem with that than I do with people using home DSL routers that utilize NAT. -C On Tue, Aug 14, 2001 at 04:59:34PM -0700, Roeland Meyer wrote:
The demonstration is easy.
1) Convince them that it is really no-goodnik to show private addrs on the Internet. 2) then make them believe it religiously. 3) then show them a traceroute and explain that everyone on the planet has traceroute.
The only reasonable conclusion, from that sequence, is that ALL routers and routing hosts need a static IP addr.
|> -----Original Message----- |> From: R Z [mailto:mypop3mail@yahoo.com] |> Sent: Tuesday, August 14, 2001 2:50 PM |> To: nanog@merit.edu |> Subject: NOC servers with public/private ip address |> |> |> |> Hi, all, |> |> We are an ISP with some internet routers. The question is if |> we should use |> public or private ip address in NMS/NOC to manage these |> routers. If we want |> to save ip address and use private ip address, we need to |> have private |> address on the internet routers. Although I am almost religious that |> internet routers should NEVER have private address in the |> routing table, I |> still need more reasons to convince other people. Can |> someone pls tell me |> the pros and cons of using private ip address? Is there any |> issue with |> private ip address? What is the practice in your network? |> |> Your insight is highly appreciated. |> Richard |> |> |> |> _________________________________________________________ |> Do You Yahoo!? |> Get your free @yahoo.com address at http://mail.yahoo.com |>
-- --------------------------- Christopher A. Woodfield rekoil@semihuman.com PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B