----- Original Message -----
> From: "Nathan Steele" <[email protected]>

[ quoting me: ]
> > So your airchain machines don't talk to the Internet at all, then?

> Well, they do. And let me state here and now that I did not design the
> layout of our network, and won't claim this to be the best. All
> automation equipment is on a completely seperate network from
> everything else. 

In my opinion, it's ok to be sub-optimal a little bit, *as long as
you know it, and plan around it* (and advise everyone who needs to know
it).

And that's another good point to make right there:

"Should we spend the money to make this tighter" really is a business
rather than engineering decision.  As engineering types, our obligation
is to figure out what short-cutting things might cause, and make sure
the business types have been formally advised in a documentary fashion
(this is called the CYA memo, generally :-).  Once that's done, it isn't
our fault if the station goes off the air cause they cheaped out. :-)

> there is a completely seperate cable modem, firewall/router and
> switches. we have two stations (one using a non Rivendell automation
> system) and each automation is on its own Gigabit switch. Only critical
> machines are on this network and NO internet browsing is done, though
> there must be internet connectivity fro things like now/next data, our
> shoutcast streams, RDCatch, etc.... user accessed machines on this
> network (production computers, etc) have thier DNS settings wrong so
> they can't get to the internet, and they are still running AV software
> anyway.

FWIW: it's often useful to do wire-analysis on such networks, and put
controlled-outbound firewalling on them.

> Again, I try to do the best with what I have, and won't claim security
> to be an area of expertise, though compared to joe average I'm sure
> I"m leagues above, compared to a network security specialist I am surely a
> rank amateur....

It is, as they used to like to say at my last IT Director gig, what it is.

> When I was 19 I studied to be a recording engineer. life happened and
> I had to go back to my hometown (with 0 recording studios) and3 years
> later I went back to school to get an associates degree in electronics,
> which included a handful of computer hardware, programming, and
> networking classes, and of course had been tinkering with computers
> since I was 14 (but audio most of my life). Did 6 years as an AV Tech
> for the local school board, designing installing and repairing audio
> video and lighting systems/ equipment. Met our chief engineer during
> this time and did some part time work for the station. when It came time
> to launch the second station I quit the cushy govt job and Now I"m in
> radio the last 3 years. In some ways I am still a fish out of water, by
> no means a radio veteran, but studios are studios, and audio is audio.
> The rest I just have to take a it comes. Fortunately the Chief is very
> strong on RF and has been in radio most of his life, so I have a good
> mentor on the RF side of things.

"Life happened".  I like that. 

Yeah, that's generally how it goes.

Cheers,
-- jra
-- 
Jay R. Ashworth                  Baylink                       [email protected]
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com         2000 Land Rover DII
St Petersburg FL USA               #natog                      +1 727 647 1274
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to