|
InlandPNW Convers Server Status, December 2006
Friday, 08 December, 2006, 04:29 PST
Notice to gateway operators and other convers server sysops who were depending upon InlandPNW for upstream linking:
I know that some of you noticed configuration changes that occurred over the past six months that may have left your convers links "high and dry." I sincerely apologize for that. However, your links are welcome.
In March 2006, we had a downstream server link up to InlandPNW who also had several other simultaneous links to upper-tier convers servers. The resulting loops were ugly, and were crashing convers servers all over the world. Consequently, I had to re-implement some restrictions  , and lost my upstream link for a time. The disk crash that occurred here in May 2006 further delayed getting everything restored. For the past several months, however, InlandPNW is enjoying a good solid feed from a top-tier convers hub, and is able to take on additional servers below it.
If you would like to use InlandPNW as your convers hub, drop me a note via the "Contact Us" link, and we'll make it happen. If you have an AmprNet address, you should be able to link in immediately by pointing your convers server to 44.12.3.129. If not, I'll need to add your IP to my access list and you'll need to link to 192.147.172.252.
73,
Brett WA7V
| InlandPNW Convers Server Status, December 2006 | Log-in or register a new user account | 1 Comment |
|
| Comments are statements made by the person that posted them.
They do not necessarily represent the opinions of the site editor. |
Re: InlandPNW Convers Server Status, December 2006
(Score: 1)
by wa7v (Colonel.Panic@BlueScreenOfDeath.com)
on 30 Sep, 07, 15:21
(User information | Send a message http://wa7v.com/)
|
|
As mentioned in this posting, the "Contact Us" form is no longer available. For now, you'll need to follow those instructions for trying to reach me via email (very few folks should have troubles sending me a message anyway). Sorry about that!
73, WA7V
|
|
|
