[UCIMC-Tech] networking for WRFU streaming - public-facing IP? socket? + wrfu.net domain
Chris Ritzo
critzo at chambana.net
Sat Dec 26 22:20:04 EST 2015
Hi Stuart,
Excellent!
On 12/26/2015 05:06 PM, Stuart Levy wrote:
> Hello Chris,
>
> We've plugged in a computer - it's currently in the IMC office, running
> Ubuntu 12.04.5 LTS, and has MAC address
> 00:23:ae:65:2a:4c
> and at the moment has been given DHCP address 192.168.42.121. It has
> an "imctech" account on it with a password which Barry knows and I
> assume you do too.
>
> It thinks its name is "rfustream.ucimc.org" - let me know if that should
> change.
*.ucimc.org is appended to the computer's hostname by DHCP for machines
getting leases inside the building. For the public DNS entry, do you
want this hostname? or something else?
rfustream.ucimc.org can be the FQDN visible to the world as well, or
something different if you prefer. Did you want stream.wrfu.net?
I'll place a host entry in DHCP so this machine will always receive that
internal IP address.
>
> It's running Airtime software- I can send its admin passwords if you care.
>
> Port forwarding:
>
> It would be nice, somehow (even if indirectly via tunnelling if
> necessary), to have access to
> ssh port 22 (or another port is OK if you prefer)
> http port 80 (and/or https port 443) for airtime admin
> (preferably public) http port 80 for main WRFU.NET page, which
> I'll set up once it's visible
> (must be public) tcp port 8000 for Icecast streaming
This is absolutely possible and I'll configure port forwarding for ports
22, 80, 443, and 8000 tomorrow morning.
>
> From the icecast2 documentation it *sounds* as though there's no need
> for any UDP Port forwarding
>
>
> Barry asks:
> - It looks as though the IMC has five assigned public IP
> addresses. Do we know what they are for, aside from the .168 firewall?
Before we signed up for UC2B, we had a block of five public IPs from
Comcast, and I think this is why we have five. Currently I believe only
one is being used-- for the firewall-- and we use static internal IPs
with port forwards for any services hosted inside the building.
>
> - Is the 192.168.47(WRFU) VLAN still configured on the firewall?
> He thinks it would be a good thing to have if possible - to separate
> WRFU computers (the studio computer, the automation computer, and the
> streamer) from the rest of the internal IMC equipment.
Yes, this VLAN is still configured on the firewall, but it's not
currently in use. There is/was VLAN separation between the staff
machines and the public computers. Servers we've typically put on a
separate VLAN as well.
If you want to get too much into VLAN separation, you're talking about
some more work to ensure VLANs are configured correctly on the building
switches (Cisco), managing the trunk ports between switches and
assigning the VLANs to appropriate switchports connected to the wall
jacks where things are located. Setting this up is not hard, but you're
getting into more system and network administration, which as you know
has been historically difficult to manage and pass on to new tech people
in an all volunteer situation.
I'd recommend we keep things simple at first, and involve IMC staff and
board people appropriately (if that's not already happening) in these
decisions. I just want to ensure we're setting something up that will
have enough ongoing support.
>
> - He'll be in town tomorrow (Sun), if there's need to be present
> work with you remotely.
>
> Thanks for your help...
>
> Stuart
>
>
> On 12/24/15 7:08 AM, Chris Ritzo wrote:
>> Remote access would be via SSH, Stuart, and we could look into whether
>> the servers we have support IPMI. For physical access to that space, you
>> would need to coordinate with IMC staff. Remote access could also be
>> set up for a machine in the studio, like the Dell Optiplex you mentioned.
>>
>> With the servers that are there now, none are running critical services
>> for Chambana.net anymore, which is why these are available. When we were
>> using them, we had easier physical access for the cases you describe.
>>
>> Since you're already working with the Dell Optiplex, if it makes the
>> most sense to you as a staring point, we could see about activating the
>> fourth jack in the studio for it. Whatever makes the most sense for you,
>> Don, and other WRFU folks.
>>
>>
>>
>> On 12/23/2015 10:27 PM, Stuart Levy wrote:
>>> 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?
>>>
>>> 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.
>>>
>>> On 12/23/15 11:52 AM, Barry Todd wrote:
>>>> Chris,
>>>> I can connect with Stuart to do the physical checking on the ports in
>>>> the room. Or whatever room is needed.
>>>> Which of the rack servers are you saying are available to use as a
>>>> streaming server?
>>>>
>>>> On Dec 23, 2015 5:58 AM, "Chris Ritzo" <critzo at chambana.net
>>>> <mailto:critzo at chambana.net>> wrote:
>>>>
>>>> Thanks, Stuart, for continuing to research and work on this on
>>>> your end.
>>>> I'm happy to help with some of the items you mention and
>>>> coordinate with
>>>> others as needed. -Chris
>>>>
>>>> On 12/22/2015 05:17 PM, Stuart Levy wrote:
>>>> > Hello again,
>>>> >
>>>> > For WRFU streaming, there are some networking needs - hope not
>>>> difficult:
>>>> >
>>>> > * if we put the streaming machine in the office, it needs
>>>> a live
>>>> > ethernet jack. There's a block of four jacks in the office's
>>>> northwest
>>>> > corner. Three are live, the fourth is unused and currently
>>>> shows no link:
>>>> >
>>>> > port "1", is available but not currently live.
>>>> > one (blue wire) feeds the automation computer (in the
>>>> office)
>>>> > one (gray wire) goes through the wall to feed a 4-port
>>>> switch in the
>>>> > studio. DHCP on switch ports gives a net-192.168 address.
>>>> > another (blue wire) goes through wall to a spare wire on
>>>> studio
>>>> > floor - maybe for people with laptops etc. DHCP gives a
>>>> net-10
>>>> > address.
>>>> >
>>>> > * The server needs a public-facing IP address and DNS name.
>>>> >
>>>> > Is this (imc-tech) the place to ask for an IP assignment /
>>>> routing
>>>> > from some specific jack?
>>>>
>>>> I can assist with the public-facing IP, DNS name/entries, static
>>>> internal IP (dhcp host entry) and forwarding rule in the firewall.
>>>>
>>>> Routing to a specific jack in the studio will require some
>>>> coordination
>>>> with someone local familiar with the locations of network
>>>> switches,
>>>> perhaps Barry or (is Volo still supporting?).
>>>>
>>>> This should be straightforward, with a little trial and error
>>>> potentially, depending on where you wish to have the server.
>>>> Note that
>>>> it is not required to have the server in the same physical
>>>> location as
>>>> the booth. I'm reasonably confident that one of the racked
>>>> machines
>>>> upstairs will work well for this server, but this is the choice of
>>>> local
>>>> folks. If you want to use a racked server, the IMC staff will
>>>> need to
>>>> provision access for someone with server experience and a
>>>> reinstall of
>>>> the operating system should be done. Happy to help coordinate with
>>>> someone if this is the route you wish to go.
>>>>
>>>> >
>>>> > * WRFU.NET <http://WRFU.NET> needs to get back on the
>>>> map. So:
>>>> >
>>>> > 1) Who administers the WRFU.NET <http://WRFU.NET> domain?
>>>> (It's currently valid,
>>>> > held by Joker.com, expiring on Feb 3rd, with no IP address
>>>> > assignments.) It would be natural for people to look
>>>> there, as
>>>> > well as on ucimc.org <http://ucimc.org> itself, to find the
>>>> station.
>>>>
>>>> I can also assist with pointing wrfu.net <http://wrfu.net> to a
>>>> location of your choice.
>>>> It was taken down some time ago after the drupal cms it was
>>>> running was
>>>> compromised.
>>>>
>>>> >
>>>> > If a DNS entry gets assigned for the streaming server's
>>>> assigned IP,
>>>> > then how about a name like "stream.wrfu.net
>>>> <http://stream.wrfu.net>" for that?
>>>> >
>>>> > 2) There should be a WRFU.NET <http://WRFU.NET> /
>>>> WWW.WRFU.NET <http://WWW.WRFU.NET> web page with a blurb
>>>> > about the station, a link to the IMC, and a "WRFU Stream"
>>>> button.
>>>> > This could be hosted on the streaming server itself, or
>>>> elsewhere
>>>> > (on the ucimc.org <http://ucimc.org> server?), whichever
>>>> makes sense.
>>>> >
>>>> > 3) In short I think there should be at least these entries
>>>> in the
>>>> > wrfu.net <http://wrfu.net> domain:
>>>> > WRFU.NET <http://WRFU.NET> (zone and A record)
>>>> > WWW.WRFU.NET <http://WWW.WRFU.NET> (another A record or a
>>>> CNAME)
>>>> > STREAM.WRFU.NET <http://STREAM.WRFU.NET> (another A
>>>> record or a CNAME)
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > IMC-Tech mailing list
>>>> > IMC-Tech at lists.chambana.net <mailto:IMC-Tech at lists.chambana.net>
>>>> > https://lists.chambana.net/mailman/listinfo/imc-tech
>>>> >
>>>>
>
More information about the IMC-Tech
mailing list