<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: [MLB-WIRELESS] meshing</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>....sooo when the antenna falls off the roof in high wind..the remote admin can shell in and use his **incredible** coding skills to fix it?</FONT></P>
<P><FONT SIZE=2>hehe ;)</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: sanbar [<A HREF="mailto:sandbar@ozemail.com.au">mailto:sandbar@ozemail.com.au</A>]</FONT>
<BR><FONT SIZE=2>Sent: Monday, 21 January 2002 13:25</FONT>
</P>
<P><FONT SIZE=2>Can't we set up some form of admin peering where there's one local admin </FONT>
<BR><FONT SIZE=2>and a remote admin for each step along the backbone? That way if </FONT>
<BR><FONT SIZE=2>something falls over when someone is away/at work/enjoying a social life </FONT>
<BR><FONT SIZE=2>at the physical location, a remote admin can shell in and fix things?</FONT>
<BR><FONT SIZE=2>If this is the case, downtime won't really be an issue IMHO.</FONT>
<BR><FONT SIZE=2>- Barry</FONT>
</P>
<CODE><FONT SIZE=3><BR>
<BR>
___________________________<BR>
<BR>
WARNING<BR>
This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorised to copy or disclose all or any part of it without the prior written consent of the Metropolitan Fire and Emergency Services Board.<BR>
___________________________<BR>
</FONT></CODE></BODY>
</HTML>