<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 2014-03-28 14:06, Tom Hayward wrote:<br>
</div>
<blockquote
cite="mid:CAFXO5Z1RfUKX51nZAm0PDd=V5mHhh7vP=2uxC-FgOdmOFsw_EQ@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Mar 28, 2014 at 1:49 PM, Dean Gibson AE7Q <a class="moz-txt-link-rfc2396E" href="mailto:hamwan@ae7q.net"><hamwan@ae7q.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Does that also explain part of why I can't access any of the HTTP sites in my prior list, but I could a week ago? Ie, there's a bit of randomness in the redundancy selection of an origination point?
</pre>
</blockquote>
<pre wrap="">
If they were 44net HTTP sites, then yes, this could explain it.
The AMPR routes have been removed from HamWAN's Corvallis router for now, meaning they'll all go through the Seattle router. This should fix routing for you. Unfortunately it leaves HamWAN with a single point of failure (or a single point of success, considering AMPR has never supported redundancy in the first place).
Tom KD7LXL
</pre>
</blockquote>
<br>
Yes, I can access all my "problem" sites now. If I understand what
you are saying, the current configuration:<br>
<ol>
<li>Has a single point of failure for access to 44net addresses.</li>
<li>Has multiple routes (ie, redundancy) to the rest of the
Internet.</li>
</ol>
<p>Or is that possible? That would seem like the best (current)
configuration.<br>
</p>
<p>-- Dean<br>
</p>
<p>ps: Moving my antenna 8 ft to the east gives a 9dBm increase in
signal-strength. Pictures pending (eg, when the rain stops).<br>
pps: While setting up the antenna, I received a hand-delivered
"stop work order" from my homeowner's association. A quick phone
call and two words ("federal preemption") fixed that. Details
with the pictures to follow ...<br>
</p>
</body>
</html>