[aklug] Re: Alaskan external monitoring

...and to their residential customers too.

Just confirmed by debugg ppp on my SoHo and forcing reconnect (clear dialer
0).

from router logging...

...
002544: Sep 23 15:12:27.130 AKDT: Vi2 IPCP: O CONFREQ [ACKsent] id 2 len 22
002545: Sep 23 15:12:27.130 AKDT: Vi2 IPCP: Address 216.137.215.40
(0x0306D889D728)
002546: Sep 23 15:12:27.130 AKDT: Vi2 IPCP: PrimaryDNS 216.152.176.1
(0x8106D898B001)
002547: Sep 23 15:12:27.130 AKDT: Vi2 IPCP: SecondaryDNS 216.152.176.2
(0x8306D898B002)
002548: Sep 23 15:12:27.142 AKDT: Vi2 IPCP: I CONFACK [ACKsent] id 2 len 22
002549: Sep 23 15:12:27.142 AKDT: Vi2 IPCP: Address 216.137.215.40
(0x0306D889D728)
002550: Sep 23 15:12:27.142 AKDT: Vi2 IPCP: PrimaryDNS 216.152.176.1
(0x8106D898B001)
002551: Sep 23 15:12:27.146 AKDT: Vi2 IPCP: SecondaryDNS 216.152.176.2
(0x8306D898B002)
002552: Sep 23 15:12:27.146 AKDT: Vi2 IPCP: State is Open
002553: Sep 23 15:12:27.146 AKDT: Di0 IPCP: Install negotiated IP interface
address xxx.xxx.xxx.xx

On Wed, Sep 23, 2015 at 2:44 PM, Royce Williams <royce@tycho.org> wrote:

> Interesting - and surprising. Those are the same IPs as their
> authoritative DNS servers. It's generally considered good practice to keep
> those separated.
>
> Royce
>
> On Wed, Sep 23, 2015 at 2:23 PM, Josh <hatlessman@gmail.com> wrote:
>
>> Oops, bad at email. Sorry.
>>
>> MTA hands out 216.152.176.1, 216.152.176.2 as dns servers (at least for
>> our Business DSL)
>>
>> On Wed, Sep 23, 2015 at 2:21 PM, Josh <hatlessman@gmail.com> wrote:
>>
>>> MTA hands out 216.152.176.1, 216.152.176.2 as dns servers (at least for
>>> our Business DSL)
>>>
>>> On Sat, Sep 19, 2015 at 9:13 AM, JP <jp@jptechnical.com> wrote:
>>>
>>>> That is pretty cool Royce.
>>>>
>>>> Have you considered AWS free tier? Free for a year and easy to move to
>>>> a new account after it expires.
>>>> On Sep 19, 2015 8:23 AM, "Royce Williams" <royce@tycho.org> wrote:
>>>>
>>>>> I'm spinning up a cooperative effort to provide free, independent
>>>>> external monitoring and trending for Alaskan geeks.
>>>>>
>>>>> http://akmon.techsolvency.com/
>>>>>
>>>>> The goal is to capture baseline health for Alaskan shared
>>>>> infrastructure and core external services. I want to enable everyone
>>>>> to quickly and definitively resolve the recurring questions of "Is it
>>>>> working from outside our network?" and the "Is it our local upstream?"
>>>>>
>>>>> It's currently running out of a Digital Ocean VPS in SFO, so the
>>>>> latency has many upstream dependencies -- but it's independent from
>>>>> any specific Alaskan infrastructure. I may try to set up a Seattle
>>>>> instance if I can find hyper-affordable VPS hosting there.
>>>>>
>>>>> It's currently just SmokePing, but other stuff can be added pretty
>>>>> easily.
>>>>>
>>>>> Suggestions welcome, especially hosts to add.
>>>>>
>>>>> I'm not sure why some of the smokeping HTTPS polling isn't working.
>>>>> It's using the EchoPingHttps poller. Anybody have any experience in
>>>>> this area?
>>>>>
>>>>> Royce
>>>>> ---------
>>>>> To unsubscribe, send email to <aklug-request@aklug.org>
>>>>> with 'unsubscribe' in the message body.
>>>>>
>>>>>
>>>
>>
>

-- 
-- 
Matt Mannhardt
"Why yes, as a matter-of-fact, I DO own the road...
but I'll share it with you if you're nice."
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.