I also did manage to find a work-around for the little OSPF problem I've been having. What's happening is that on the customer's router, when the T-1 link is up, the routes, including the all important default route, are populated through OSPF. If the T-1 goes down, then all the OSPF generated routes disappear, including the all important default route.
Upshot—if the T-1 goes down, the customer can't see the Internet.
But oddly enough, when the T-1 goes down, OSPF still shows a neighbor connection through the DSL link. But it won't populate the routes.
The work-around? A static default route through the DSL connection but weighted so heavily that the default route through OSPF (in which case goes through the T-1) is preferred if it exists.
So now, the T-1 goes down, the OSPF routes disappear, leaving the static default route over the DSL so the customer can still see the Internet.
It works, but I don't like it.
You have my permission to link freely to any entry here. Go
ahead, I won't bite. I promise.
The dates are the permanent links to that day's entries (or
entry, if there is only one entry). The titles are the permanent
links to that entry only. The format for the links are
simple: Start with the base link for this site: https://boston.conman.org/, then add the date you are
interested in, say 2000/08/01,
so that would make the final URL:
You can also specify the entire month by leaving off the day
portion. You can even select an arbitrary portion of time.
You may also note subtle shading of the links and that's
intentional: the “closer” the link is (relative to the
page) the “brighter” it appears. It's an experiment in
using color shading to denote the distance a link is from here. If
you don't notice it, don't worry; it's not all that
It is assumed that every brand name, slogan, corporate name,
symbol, design element, et cetera mentioned in these pages is a
protected and/or trademarked entity, the sole property of its
owner(s), and acknowledgement of this status is implied.