[j-nsp] juniper-nsp Digest, Vol 75, Issue 55

[chenoi A]

Thanks to all, actually i noticed previous reply from mark on the exception, i know it can be done x.x.x.0 and x.x.x.255 but from my understanding and normal practise , this two will be exclude from my loopback ip plan , i do agree with mark on this.
 
1. to ensure smooth interoperability between machine/setting
2. well manage plan
3. no hazzle infuture...
 
anyway...it was good comment from you cougar and i much appreciated it. yup in doing something they must be a away ..a solution...and alternative...
 
Thanks again...
 

--- On Sat, 2/28/09, juniper-nsp-request at puck.nether.net <juniper-nsp-request at puck.nether.net> wrote:

From: juniper-nsp-request at puck.nether.net <juniper-nsp-request at puck.nether.net>
Subject: juniper-nsp Digest, Vol 75, Issue 55
To: juniper-nsp at puck.nether.net
Date: Saturday, February 28, 2009, 9:00 AM

Send juniper-nsp mailing list submissions to
	juniper-nsp at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/juniper-nsp
or, via email, send a message with subject or body 'help' to
	juniper-nsp-request at puck.nether.net

You can reach the person managing the list at
	juniper-nsp-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of juniper-nsp digest..."


Today's Topics:

   1. Re: Loopback IP address in BGP Peering (Cougar)
   2. Re: Loopback IP address in BGP Peering (Mark Tinka)


----------------------------------------------------------------------

Message: 1
Date: Sat, 28 Feb 2009 12:31:15 +0200 (EET)
From: Cougar <cougar at random.ee>
Subject: Re: [j-nsp] Loopback IP address in BGP Peering
To: Mark Tinka <mtinka at globaltransit.net>
Cc: juniper-nsp at puck.nether.net
Message-ID: <alpine.LNX.1.10.0902281224550.16605 at lost.data.ee>
Content-Type: TEXT/PLAIN; FORMAT=flowed; CHARSET=US-ASCII


On Sat, 28 Feb 2009, Mark Tinka wrote:

> Remember, your Loopback address takes a netmask of /32. So
> you can have as many address as you (plan to) have
> routers... with the exception of x.x.x.0 and x.x.x.255, of
> course.

What kind of exception is this? In CIDR world you can use any address you 
like except first and last _LAN_ addresses when netmask is /30 or less. 
With /31 and /32 can use any address and so far I haven't seen any 
problems using x.x.x.0 or x.x.x.255 in Junipers.

---
Cougar


------------------------------

Message: 2
Date: Sat, 28 Feb 2009 23:40:19 +0800
From: Mark Tinka <mtinka at globaltransit.net>
Subject: Re: [j-nsp] Loopback IP address in BGP Peering
To: Cougar <cougar at random.ee>
Cc: juniper-nsp at puck.nether.net
Message-ID: <200902282340.25047.mtinka at globaltransit.net>
Content-Type: text/plain; charset="iso-8859-1"

On Saturday 28 February 2009 06:31:15 pm Cougar wrote:

> What kind of exception is this? In CIDR world you can use
> any address you like except first and last _LAN_
> addresses when netmask is /30 or less. With /31 and /32
> can use any address and so far I haven't seen any
> problems using x.x.x.0 or x.x.x.255 in Junipers.

That may very well be - but my suggestion is just because it 
can be done, doesn't mean it's a great idea "all around". 
These are the types of practices that come back and bite you 
due to varying levels of support for implementing .0 and 
.255 across various pieces of software. I'm not presuming 
the OP has only Junipers to deal with in their network.

Given the number of addresses one may potentially save in, 
say, a /24 sliced only for Loopbacks vs. not getting 
stressed by why this may break some things in the network; 
I'd much rather sacrifice those two addresses, thank-you-
very-much.

Keep it simple, keep it stupid, keep it unambiguous. The 
physics don't change, just how you apply them.

Then again, to each his own...

You probably want to spend some time wading through:

http://tinyurl.com/dzw4cj
http://tinyurl.com/av8rwm
http://tinyurl.com/chwjms

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL:
<https://puck.nether.net/pipermail/juniper-nsp/attachments/20090228/18f5212a/attachment-0001.bin>

------------------------------

_______________________________________________
juniper-nsp mailing list
juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

End of juniper-nsp Digest, Vol 75, Issue 55
*******************************************