[MAINT] Network Work on Code Sunday, Oct 1, 1-4pm EDT

GWB gwb at 2realms.com
Mon Oct 2 20:50:13 EDT 2017


So AT&T's network equipment works when nothing is connected to it?
Clearly this is a success story.  If the tech had been allowed to try
the new modem, that would have greatly sped up the troubleshooting
process.  If it had worked as before, then problem solved.  If not,
then you could debug your network topography on your side.

That's actually more frustrating than I thought.  Maybe another phone
call to ask them to just please try a different modem before you spend
all that time chasing a problem that might not exist.

I have managed to keep the static (fixed) IP I have, but not without a
struggle.  The solution is sometimes just having a "dumb" modem
connected to the LAN with the switching equipment at the telecomm set
to assign a fixed IP.  Sometimes I have to lease a fixed IP from a
different provider who then contracts with a local telecomm.  In any
event, it's worth it, and necessary.

Check around.  Anywhere from Cambridge to Dedham should be any number
of telecomm trunk leasing outfits.

Gordon

On Mon, Oct 2, 2017 at 6:57 PM, Derek Atkins <derek at ihtfp.com> wrote:
> [removed -announce]
>
> On Mon, October 2, 2017 6:09 pm, GWB wrote:
>> Derek,
>>
>> Sorry to hear that, and its frustrating.  Perhaps AT&T could, in the
>> meantime, install a different modem temporarily to see if that solves
>> the problem?  I've been through this with various T line providers,
>> and their default response is often "Something you did", even when the
>> internal set up has not changed in years.  Not all of them do this,
>> but the repair techs are sometimes tied by their instructions from on
>> high.
>
> Alas, they basically said "disconnect all your equipment to prove to us
> it's *OUR* problem", and of course when I did do that I was able to show
> there was no problem.  So from their perspective it's a problem on my end,
> not theirs.
>
> The tech actually did have a new modem box for me, but wasn't allowed to
> install it.  The fact that I have static IPs from them is half the problem
> with why he couldn't just replace the modem.  Also the fact that the
> problem only occurs when my network devices are connected.  :(
>
> I've still got a few avenues to explore.
>
> The fact that it started at midnight just seems suspicious (or highly
> coincidental).
>
> -derek
>
>>
>> Gordon
>>
>> On Mon, Oct 2, 2017 at 12:28 PM, David Carlson
>> <david.carlson.417 at gmail.com> wrote:
>>> That might be difficult, as it may be a loose connector or even
>>> corrosion
>>> inside a cable or connector or component in a power supply or ???
>>>
>>> Good luck.
>>>
>>> David C
>>>
>>> On Oct 2, 2017 10:42 AM, "Derek Atkins" <warlord at mit.edu> wrote:
>>>
>>>> Hi,
>>>>
>>>> Just a quick follow-up.
>>>>
>>>> AT&T did come, and with their help we debugged the network only to
>>>> discover that it's something inside my network that is causing their
>>>> modem to go all futzy.
>>>>
>>>> I'm now in the process of trying to debug further, but it's going to
>>>> take time.  Expect further interuptions until I can isolate the issue.
>>>>
>>>> -derek
>>>>
>>>> Derek Atkins <warlord at MIT.EDU> writes:
>>>>
>>>> > Hi,
>>>> >
>>>> > tl;dr:  AT&T is coming to fix some network issues tomorrow, Sunday,
>>>> > between 1-4pm EDT; service can last up to 2 hours and may involve
>>>> > several network outages.
>>>> >
>>>> > LONG VERSION:
>>>> >
>>>> > As some of you may have noticed, there have been some network issues
>>>> to
>>>> > code which started just over a week ago.  One of the downsides was
>>>> > significant packet loss and gncbot disappearing from IRC.  Alas, I
>>>> had
>>>> > been out of the country while this was happening and couldn't start
>>>> to
>>>> > really look into it; I restarted gncbot several times while I was
>>>> away
>>>> > but due to the persistent network issues it regularly would lost
>>>> > contact.
>>>> >
>>>> > I'm seeing anywhere from 20-40% packet loss and ping times to my
>>>> > immediate router anywhere from 200-1000ms (whereas it's usually
>>>> 3-4ms).
>>>> > I called AT&T, my ISP, and they are sending a tech tomorrow, Sunday,
>>>> > October 1, between 1-4pm EDT.  The maintenance could potentially take
>>>> 2
>>>> > hours once they arrive, but of course it all depends on what the
>>>> issue
>>>> > is.
>>>> >
>>>> > This will affect code, lists, and wiki services including email,
>>>> gncbot,
>>>> > etc.
>>>> >
>>>> > I'll attempt to keep people informed over IRC, assuming of course
>>>> that I
>>>> > can get online prior to the work being done.
>>>> >
>>>> > Please let me know if you have any questions.
>>>> >
>>>> > -derek
>>>>
>>>> --
>>>>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>>>        Member, MIT Student Information Processing Board  (SIPB)
>>>>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>>>>        warlord at MIT.EDU                        PGP key available
>>>> _______________________________________________
>>>> gnucash-user mailing list
>>>> gnucash-user at gnucash.org
>>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>>> -----
>>>> Please remember to CC this list on all your replies.
>>>> You can do this by using Reply-To-List or Reply-All.
>>>>
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -----
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>
>
> --
>        Derek Atkins                 617-623-3745
>        derek at ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
>


More information about the gnucash-user mailing list