nanog mailing list archives
Re: rfc1918 ignorant (fwd)
From: Haesu <haesu () towardex com>
Date: Thu, 24 Jul 2003 10:31:34 -0400
Hmm this could affect routing protocols which use the primary address..
I haven't tried doing that with igp protocols.. But with BGP, it works does manage to bind itself to the working address. (Or if you are sourcing update to loopback, that would be fine too)
Right but this one benefit doesnt make right the wrongs! I guess one thing you could do (if you really wanted to implement hacks) is to use the rfc1918 space on your routers and then nat them to a global ip at your borders.. achieves all your goals anyhow (not that i'd recommend it ;)
The thing is... some people want to hide the IP of the interface that faces their transit on the border router, as most /30 demarcation subnet is assigned from the transit. And since they would run either bgp or static route between the transit and their border router, it shouldn't break routing.. -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: haesu () towardex com Cell: (978) 394-2867
Current thread:
- RE: rfc1918 ignorant (fwd) Dave Temkin (Jul 23)
- Re: rfc1918 ignorant (fwd) Petri Helenius (Jul 23)
- RE: rfc1918 ignorant (fwd) Randy Bush (Jul 23)
- <Possible follow-ups>
- RE: rfc1918 ignorant (fwd) Daniel Senie (Jul 23)
- Re: rfc1918 ignorant (fwd) Jeff Wasilko (Jul 23)
- Re: rfc1918 ignorant (fwd) Haesu (Jul 23)
- Re: rfc1918 ignorant (fwd) Stephen J. Wilcox (Jul 24)
- Re: rfc1918 ignorant (fwd) Haesu (Jul 24)
- RE: rfc1918 ignorant (fwd) Darren Bolding (Jul 24)
- Re: rfc1918 ignorant (fwd) Jeff Wasilko (Jul 23)