BALUG Wiki

User Tools

Site Tools

Trace:
system:ip_addresses

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
Next revision Both sides next revision
system:ip_addresses [2007-04-29T20:11:13+0000]
198.144.194.236 created (hopefully a fairly "complete" start) 		system:ip_addresses [2019-12-12T03:48:45+0000]
michael_paoli updated to (mostly) historical - added some; updates to come
Line 1: Line 1:
 ======IP Addresses====== ======IP Addresses======
- +... to be (majorly) updated 
-**IPv4 addresses** (this host and subnet):​\\ +===== mostly historical information ===== 
-208.96.15.248/​29 network:\\+**IPv4 addresses** (this subnet):​\\ 
 +208.96.15.248/​29 network ​(netmask 255.255.255.248):\\
 208.96.15.248 network\\ 208.96.15.248 network\\
 208.96.15.249 Default Gateway\\ 208.96.15.249 Default Gateway\\
-208.96.15.250 ​[[http://​en.wikipedia.org/​wiki/​Hot_Standby_Router_Protocol|HSRP]]\\ +208.96.15.250 ​"​**vicki**"​ (qemu-kvm host - Silicon Mechanics box primary IP)\\ 
-208.96.15.251 ​[[http://​en.wikipedia.org/​wiki/​Hot_Standby_Router_Protocol|HSRP]]\\ +208.96.15.251 ​**IPMI**\\ 
-**208.96.15.252 ​SF-LUG** (sf-lug.com.,​ etc.\\ +**208.96.15.252 ​sflug** (qemu-kvm "​guest"​ of host "​vicki", ​**sf-lug.com.**, etc.)\\ 
-208.96.15.253 (**useable** ​- reserved for future use(?))\\ +208.96.15.253 (usable ​- reserved for future use(?))\\ 
-**208.96.15.254** for **BALUG** use\\ +**208.96.15.254 ​balug** (qemu-kvm "​guest"​ of host "​vicki", ​for **BALUG** use (balug-sf-lug-v2.balug.org,​ etc.)\\ 
-208.96.15.255 broadcast +208.96.15.255 broadcast\\ 
- +**DNS** (provided by colo at above location / for above subnet): 
-Note that **208.96.15.254** is principally **reserved ​for BALUG** use.  Services that aren't BALUG'​s +216.93.160.11 & 216.93.160.16 
-or conflict or potentially conflict with what BALUG wishes to use on port(s) on that IP may +==== more historical information ==== 
-get "​bumped"​ from that IP address (e.g. the non-BALUG service reconfigured so it doesn'​t +mostly from: http://www.balug.org/dns/ 
-run or also run on that IP).  Note also that in some/many cases BALUG may have no objection +<file> 
-or conflict with some common services not specific to BALUG also running on 208.96.15.254 +Some "​handy"​(?​) information on BALUG DNS and IPs and such.
-(so those may simply peacably coesist and not or not likely be "​bumped"​ off of that IP). +
- +
-Some background/​references/​excerpts on the IPv4 addresses follows:\\ +
-[[http://linuxmafia.com/pipermail/sf-lug/​2007q2/​001427.html|Notes re 2007-04-16 SF-LUG meeting about the colo box]] +
-<html> +
-Cc: nathank +
-From: jim stockford +
-Subject: Re: IP addresses +
-Date: Mon, 23 Apr 2007 08:52:11 -0700 +
-To: Michael Paoli+
  
-hi, michael, note i've copied nathan.+Definitive answers are found in DNS, the list shown below may be neither 
 +current nor complete.
  
-    Take 254. thank you for the explanation.+#this changed approximately 2010-09--2010-10,​ from: 
 +#208.97.167.22 balug-dreamhost.balug.org tab.dreamhost.com #presently hosting [www.]balug.org 
 +#and again approximately 2012-11-20--2013-02-08,​ from: 
 +#​173.236.193.159 balug-dreamhost.balug.org aladfar.dreamhost.com #presently hosting [www.]balug.org;​ note also that [www.]balug.org is VIP distinct from 173.236.193.159 on aladfar.dreamhost.com 
 +#to: 
 +208.97.177.9 balug-dreamhost.balug.org charles-carroll.dreamhost.com #presently hosting [www.]balug.org;​ note also that [www.]balug.org is VIP distinct from 208.97.177.9 on aladfar.dreamhost.com
  
-On Apr 22, 2007, at 7:03 PM, Michael Paoli wrote:+as of 2013-01-28:​ 
 +208.96.15.250 balug-sf-lug-v2.console.balug.org #Xen dom0 --> qemu-kvm (host) of balug-sf-lug-v2.balug.org 
 +208.96.15.251 IPMI 
 +208.96.15.252 sf-lug.com Xen domU --> qemu-kvm guest, formerly primary IP of old sf-lug.com "​tower"​ system which is no longer generally on-line, formerly balug-sf-lug-v1.console.balug.org 
 +208.96.15.254 balug-sf-lug-v2.balug.org #Xen domU --> qemu-kvm guest on balug-sf-lug-v2.console.balug.org, presently hosting www.{beta,​new,​test}.balug.org - 208.96.15.254 was VIP on old sf-lug.com "​tower"​ system which is no longer generally on-line, was formerly balug-sf-lug-v1.balug.org VIP used to host www.{beta,​new,​test}.balug.org balug-sf-lug-v1.balug.org (these services have been or are being mostly or entirely moved to 208.96.15.254 balug-sf-lug-v2.balug.org) 
 +#​208.69.42.167 formerly balug-sf-lug-v2.balug.org Xen domU on balug-sf-lug-v2.console.balug.org,​ moved to 208.96.15.254 
 +#​208.69.42.165 formerly balug-sf-lug-v2.console.balug.org Xen host of balug-sf-lug-v2.balug.org,​ moved to 208.96.15.250
  
-> Well, ... let me/us know if we can snag one of those IPs for BALUG. +These two have been down or unavailable since approximately some months before 2009-11: 
-> +#64.2.3.203 balug-untangle.balug.org #BALUG VMware guest on balug-untangle.console.balug.org 
-> Looks like we've got a network of 208.96.15.248/​29: +#64.2.3.195 balug-untangle.console.balug.org #VMware host of balug-untangle.balug.org 
-> 208.96.15.248 network +</file>
-> 208.96.15.249 Default Gateway +
-> 208.96.15.250 HSRP +
-> 208.96.15.251 HSRP +
-> 208.96.15.252 sf-lug.com. +
-> 208.96.15.253 (useable) +
-> 208.96.15.254 (useable) +
-> 208.96.15.255 broadcast +
-> +
-> ... so, ... could potentially use 208.96.15.253 or 208.96.15.254 +
-> for BALUG (perhaps 208.96.15.254) if you might want to keep the other +
-> available IP contiguous with the existing sf-lug.com. IP). +
-> +
-> Typically on a /29 there would be 5 useable IPs (8 less 2 for network +
-> and +
-> broadcast less one more for router) ​... but with HSRP that drops us to +
-> 3 useable (HSRP using n+1 - two routers, that's 3 IPs - one for each +
-> router + one high availability virtual IP to serve as the default +
-> route). +
-> +
-> At best, if we want to maintain high availability routing, we might be +
-> able to squeeze one more IP out of them ... but anything beyond that +
-> and +
-> we'd have to sacrifice any router redundancy. ​ Since the only "​box"​ we +
-> have on the subnet is the LINUX box, and it's quite capable ​of being +
-> configured with two default routes (and will use whichever one works), +
-> going without HSRP, and instead just having the two IPs for the two +
-> routers +
-> would work as well in terms of high availability routing ... but this +
-> may +
-> not be standard operating procedure for the colo, so they may or may +
-> not +
-> be particularly agreeable to making such a change. ​ In any case, that +
-> would +
-> only gain us one additional useable IP - bringing us from 3 up to 4. +
-> +
-> Squeezing a 5th IP would generally mean sacraficing router/​routing +
-> failover. +
-> +
-> http://​en.wikipedia.org/​wiki/​Hot_Standby_Router_Protocol +
-> http://​tools.ietf.org/​html/​rfc2281 +
-> +
-> Quoting jim stockford:​ +
-> +
->> Here's a clip from the ServePath Network +
->> Team. +
->> Check it out: +
->> +
->> You have been assigned the following block of IP addresses:​ +
->> +
->> ​     First Useable IP address: ​ 208.96.15.252 +
->> ​     Last Useable IP address: ​ 208.96.15.254 +
->> ​     Default Gateway: ​ 208.96.15.249 +
->> ​     Netmask: ​ 255.255.255.248 +
->> +
->> DNS 216.93.160.16 +
->> DNS 216.93.170.17 +
->> +
->> You are assigned power ports 248.8.10 +
->> +
->> Please note that your VLAN is implemented with HSRP for +
->> redundancy. ​ This is why the first 3 useable IP addresses of  <---- +
->> your IP block are reserved and not useable. +
-</html>+
system/ip_addresses.txt · Last modified: 2019-12-12T23:40:50+0000 by michael_paoli

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC0 1.0 Universal
CC0 1.0 Universal Donate Powered by PHP Valid HTML5 Valid CSS Run on Debian Driven by DokuWiki