[mdlug] Need ideas for a "telepresence" box

Adam Tauno Williams awilliam at whitemice.org
Sun Jan 27 14:07:25 EST 2013


On Sun, 2013-01-27 at 13:54 -0500, Aaron Kulkis wrote:
> David McMillan wrote:
> > Actually, part of the problem is that they have a strong "no VPN" policy.  Not for "guests," anyway -- the network connection they provide for visitors is port-limited to HTTP only -- even HTTPS is blocked, to say nothing off SSH/SFTP.
> > Basically, you're allowed basic web browsing, and that's it.  Getting them to open *any* other port in the firewall to the outside world looks to be an uphill battle (both ways, barefoot, in the snow, etc etc).  And trying to "sneak" through
> > unguarded ports in their firewall opens us up to lawsuits  or million$ in breach-of-contract penalties.  Which is why I'm searching for an alternative where they "can't stop the signal, Mal."
> >(Another part of the problem is that I can't talk to any actual *techs* in their IT dept -- I keep getting routed to managers who get all glassy-eyed and start reciting their corporate IT mantra whenever I start trying to talk ports, protocols,
> > and client/server architectures)
> It's simple. "You have paid us $X so far.  Without your cooperation, you
> will receive a product which will not work until you do cooperate.  The
> ball is in your court."

Eh, no.  Then the manager you are allowed to talk to calls your manager,
complains about your attitude, and you get disciplined / fired.

There is a perfectly good reason companies insulate their technicians
behind obstructionist management;  primarily it shields them from
dealing with a constant stream of 'exception requests' that will turn
the entire network into a collection of one-off hacks.  I strongly
support obstructionist management.  And remember they are the one's
paying those technicians, not you, and they are usually getting paid
from the IT budget not matter what department or divisions hopeless crap
they are forced to work-on/deal-with.  <rant mode="you should probably
ignore this part">Every department wants to somehow turn its lack of
management and/or poor management from an HR into an IT problem, then
the managers can go golfing and bitch about how IT takes so long to
solve their problems</rant>

The best solution when dealing with an immovable wall of is to just deal
with whatever the problem is yourself.  You can usually get a DSL drop
or other connection into a facility if the cellular option doesn't work
out.  I've never witnessed too much grief in getting a 'stand alone'
ISDN or DSL drop to a piece of equipment; they just route it through
their building and say "from here it is your problem".  Which is exactly
what you want; everybody is happy.  A stand-alone drop is usually
installed with the help of Facilities, not IT, and Facilities is rarely
buried behind so many defenses.

-- 
Adam Tauno Williams  GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA



More information about the mdlug mailing list