<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
How does remote access work to the rack servers in the attic? I'd
expect it to be a pretty stable environment, but am hoping not to
have to call up someone with a key to the space and coordinate
schedules if something flakes out... I'd want to reboot it
periodically as kernel updates come out, and what if it somehow
doesn't come up? How does that kind of thing happen with the
machines you already run there?<br>
<br>
Re the non-rack alternative, I borrowed another computer from the
donated collection, thanks to Sophia and Don - this one (Dell
Optiplex 760, core2 duo) seems to work fine.<br>
<br>
<div class="moz-cite-prefix">On 12/23/15 11:52 AM, Barry Todd wrote:<br>
</div>
<blockquote
cite="mid:CAB+US64QtLLYjEzhSWXcekUSTN5+FNz_Vmb1CYe99B+BN_-OZQ@mail.gmail.com"
type="cite">
<p dir="ltr">Chris, <br>
I can connect with Stuart to do the physical checking on the
ports in the room. Or whatever room is needed. <br>
Which of the rack servers are you saying are available to use as
a streaming server?</p>
<div class="gmail_quote">On Dec 23, 2015 5:58 AM, "Chris Ritzo"
<<a moz-do-not-send="true" href="mailto:critzo@chambana.net">critzo@chambana.net</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks,
Stuart, for continuing to research and work on this on your
end.<br>
I'm happy to help with some of the items you mention and
coordinate with<br>
others as needed. -Chris<br>
<br>
On 12/22/2015 05:17 PM, Stuart Levy wrote:<br>
> Hello again,<br>
><br>
> For WRFU streaming, there are some networking needs -
hope not difficult:<br>
><br>
> * if we put the streaming machine in the office, it
needs a live<br>
> ethernet jack. There's a block of four jacks in the
office's northwest<br>
> corner. Three are live, the fourth is unused and
currently shows no link:<br>
><br>
> port "1", is available but not currently live.<br>
> one (blue wire) feeds the automation computer (in the
office)<br>
> one (gray wire) goes through the wall to feed a
4-port switch in the<br>
> studio. DHCP on switch ports gives a net-192.168
address.<br>
> another (blue wire) goes through wall to a spare wire
on studio<br>
> floor - maybe for people with laptops etc. DHCP
gives a net-10<br>
> address.<br>
><br>
> * The server needs a public-facing IP address and DNS
name.<br>
><br>
> Is this (imc-tech) the place to ask for an IP
assignment / routing<br>
> from some specific jack?<br>
<br>
I can assist with the public-facing IP, DNS name/entries,
static<br>
internal IP (dhcp host entry) and forwarding rule in the
firewall.<br>
<br>
Routing to a specific jack in the studio will require some
coordination<br>
with someone local familiar with the locations of network
switches,<br>
perhaps Barry or (is Volo still supporting?).<br>
<br>
This should be straightforward, with a little trial and error<br>
potentially, depending on where you wish to have the server.
Note that<br>
it is not required to have the server in the same physical
location as<br>
the booth. I'm reasonably confident that one of the racked
machines<br>
upstairs will work well for this server, but this is the
choice of local<br>
folks. If you want to use a racked server, the IMC staff will
need to<br>
provision access for someone with server experience and a
reinstall of<br>
the operating system should be done. Happy to help coordinate
with<br>
someone if this is the route you wish to go.<br>
<br>
><br>
> * <a moz-do-not-send="true" href="http://WRFU.NET"
rel="noreferrer" target="_blank">WRFU.NET</a> needs to get
back on the map. So:<br>
><br>
> 1) Who administers the <a moz-do-not-send="true"
href="http://WRFU.NET" rel="noreferrer" target="_blank">WRFU.NET</a>
domain? (It's currently valid,<br>
> held by Joker.com, expiring on Feb 3rd, with no IP
address<br>
> assignments.) It would be natural for people to
look there, as<br>
> well as on <a moz-do-not-send="true"
href="http://ucimc.org" rel="noreferrer" target="_blank">ucimc.org</a>
itself, to find the station.<br>
<br>
I can also assist with pointing <a moz-do-not-send="true"
href="http://wrfu.net" rel="noreferrer" target="_blank">wrfu.net</a>
to a location of your choice.<br>
It was taken down some time ago after the drupal cms it was
running was<br>
compromised.<br>
<br>
><br>
> If a DNS entry gets assigned for the streaming
server's assigned IP,<br>
> then how about a name like "<a moz-do-not-send="true"
href="http://stream.wrfu.net" rel="noreferrer"
target="_blank">stream.wrfu.net</a>" for that?<br>
><br>
> 2) There should be a <a moz-do-not-send="true"
href="http://WRFU.NET" rel="noreferrer" target="_blank">WRFU.NET</a>
/ <a moz-do-not-send="true" href="http://WWW.WRFU.NET"
rel="noreferrer" target="_blank">WWW.WRFU.NET</a> web page
with a blurb<br>
> about the station, a link to the IMC, and a "WRFU
Stream" button.<br>
> This could be hosted on the streaming server itself,
or elsewhere<br>
> (on the <a moz-do-not-send="true"
href="http://ucimc.org" rel="noreferrer" target="_blank">ucimc.org</a>
server?), whichever makes sense.<br>
><br>
> 3) In short I think there should be at least these
entries in the<br>
> <a moz-do-not-send="true" href="http://wrfu.net"
rel="noreferrer" target="_blank">wrfu.net</a> domain:<br>
> <a moz-do-not-send="true" href="http://WRFU.NET"
rel="noreferrer" target="_blank">WRFU.NET</a> (zone and A
record)<br>
> <a moz-do-not-send="true"
href="http://WWW.WRFU.NET" rel="noreferrer" target="_blank">WWW.WRFU.NET</a>
(another A record or a CNAME)<br>
> <a moz-do-not-send="true"
href="http://STREAM.WRFU.NET" rel="noreferrer"
target="_blank">STREAM.WRFU.NET</a> (another A record or a
CNAME)<br>
><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> IMC-Tech mailing list<br>
> <a moz-do-not-send="true"
href="mailto:IMC-Tech@lists.chambana.net">IMC-Tech@lists.chambana.net</a><br>
> <a moz-do-not-send="true"
href="https://lists.chambana.net/mailman/listinfo/imc-tech"
rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/imc-tech</a><br>
><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>