Wireshark-users: Re: [Wireshark-users] Using Wireshark for a DSL "link no surf" problem

From: "Jamie O. Montgomery" <Jamie.Montgomery@xxxxxxxxxxxxx>
Date: Wed, 18 Jun 2014 03:17:39 +0000

I work with DSL at work, so I'd be interested in seeing your screen captures to see if I can help.

Jamie Montgomery | Comporium
Network Facilities Engineering | Engineering Associate II

The information contained in this e-mail message and any attachments thereto are confidential, privileged, or otherwise protected from disclosure, and are intended for the use of the individual or entity named above. Dissemination, distribution or copying of this message and any attachments by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please immediately notify the sender by telephone or e-mail and destroy the original message, attachments, and all copies.

On Jun 17, 2014 10:18 PM, Kok-Yong Tan <ktan@xxxxxxxxxxxxxxxxxxx> wrote:
According to a more helpful member of the ISP's tech support staff, he tells me that he *CAN* see the layer 2 link from his end.  Just that there's no layer 3 traffic flowing across it, just the occasional layer 2 "keep alive" pulses.  

Also, I can connect directly into the DSL modem.  With reference to this user manual for my DSL modem 


I have solid green lights for the Power, LAN and DSL LEDs but a totally dark Internet LED (which I think mirrors exactly what the helpful tech support rep is saying).  In the diagnostic page of the DSL modem, it says that "ATM OAM segment ping" and "ATM OAM end to end ping" fails.  Also, PPPoE server session and authentication to server fails.

I have screenshots of the various webpages on the DSL modem with more info if it's of any help (I don't know if it can be posted on this mailing list--some mailing lists prohibit attachments).
-- 
Reality Artisans, Inc.              #   Network Wrangling and Delousing
P.O. Box 565, Gracie Station        #   Apple Certified Consultant
New York, NY 10028-0019            #   Apple Consultants Network member
<http://www.realityartisans.com> #   Apple Developer Connection member
Cell: (646) 327-2918 #   Ofc: (212) 369-4876

On Jun 17, 2014, at 16:31 , Pedro Tumusok <pedro.tumusok@xxxxxxxxx> wrote:

Usually the CPE gives you some data about the physical link that can be used to figure out what the issue is.
Are you sure there is L2 connectivity?

Pedro


On Tue, Jun 17, 2014 at 11:53 PM, Kok-Yong Tan <ktan@xxxxxxxxxxxxxxxxxxx> wrote:

> On Jun 17, 2014, at 14:28, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
>
>> On 06/17/2014 08:42 PM, Kok-Yong Tan wrote:
>> Is it possible to use Wireshark to troubleshoot a DSL "link no surf" problem?  The ISP insists it's a CPE issue but the problem only started after their Tier 1 tech monkeyed with the DSLAM and/or the CPE (remotely) in some manner.  I find it suspicious that the problem was intermittent packet loss until they tinkered, whereupon the problem became a "link no surf" issue (i.e., there's Layer 2 connectivity but zero Layer 3 traffic passing).
>
> Depends on what you can trace in the CPE, as in, how close to the DSL interface.
> Otherwise you'll need capture hardware on the DSL....
>
> Good luck,
> Jaap
>

I can get up to the DSL modem itself.  In hindsight, I'm thinking this isn't going to be of much use and the only way to debug this is with capture hardware on the DSL side as you suggested.  Drat.
--
Sent from my iPad2 with greater chance of typographical, grammatical and other disasters.  Your indulgence is even more humbly requested.
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe



--
Best regards / Mvh
Jan Pedro Tumusok

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe