[Pedro Tumusok <pedro.tumusok@xxxxxxxxx>]

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