[volunteers] IP technical information for Via.net

[Rick Moen]

For collective knowledge, this is a refresh of information about our
TCP/IP presence at Via.net, revised to include the new server.



Our IP netblock at Via.net is 157.22.20.224/28, which is a 16-address
CIDR block[1] (netmask = 255.255.255.240), allocated so far as follows:

157.22.20.224 [network address]
157.22.20.225 Gateway to the Internet
157.22.20.226 our (unnamed) Ethernet switch
157.22.20.227 "svlug" (www.svlug.org AKA lists.svlug.org AKA svlug.org host)[2]
157.22.20.228 "brie" (prototype new server box in progress)[3]
157.22.20.229 -unassigned1-
157.22.20.230 -unassigned2-
157.22.20.231 -unassigned3-
157.22.20.232 -unassigned4-
157.22.20.233 -unassigned5-
157.22.20.234 -unassigned6-
157.22.20.235 -unassigned7-
157.22.20.236 -unassigned8-
157.22.20.237 -unassigned9-
157.22.20.238 -unassigned10-
157.22.20.239 [broadcast address]

That is, we can use 10 more IP addresses for other purposes -- and Joe
McGuckin of Via.net has also let us have about 1/4 rack of space, if we
need it.


DNS1: 209.81.9.1
DNS2: 209.81.0.254

Note: Those two nameservers are NOT usable directly by the public at
large, only by Via.net IPs, e.g., by the www.svlug.org's DNS resolver
library via reference in /etc/resolv.conf.


[1] For help understanding CIDR subsets of Class C IPv4 networks,
see this page:  http://linuxmafia.com/faq/Network_Other/netmasks.html
(CIDR = Classless Inter-Domain Routing is the post-1993 scheme for
allocating IP blocks on partial subsets of Class A, B, or C blocks,
rather than using entire class networks, as was done before the IPv4
address shortage.  More at:  http://www.ietf.org/rfc/rfc1519.txt)

[2] IP netblock owner "Zocalo" of Berkeley set reverse DNS for this 
IP to FQDN "lists.svlug.org.", which is suboptimal but OK.

[3] There is not yet reverse DNS.  "lists.svlug.org." would probably 
be the best option, and I'll request that change soon.