Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: April 2014 SR102 router - Wireshark unable to get correct DSL credentials  (Read 8645 times)

dan_123

  • Just arrived
  • *
  • Posts: 1

Hi All,

I've just made the switch to Sky (my company forced my hand) and they've sent me though an SR102.  My set-up up until yesterday was a draytech modem with a 2013 Airport extreme.  I was getting 12mb with my previous provider (yesterday) and I had outstanding connectivity and reliability, and now with Sky's kit I'm getting 3mb. 

I had looked on forums earlier this week and looked at how to get the credentials, however, I'm not sure if the new "Sky Shield" is getting in the way, but when copying option 61 as printable text, it gives me the value "=<lo" instead of my dsl credentials. 

I've tried extracting the details as per this youtube vid:
http://youtu.be/BdcsmYX7eEQ and also by changing the router to WANOE however both attempts returned the same result.

Has anyone else encountered this issue? and/or have any advice?  Any ideas or suggestions are more than welcome!


TL;DR - unable to get username and password from the latest Sky Router, SR102 using Wireshark and in need of a hand.

Cheers,

Dan
Logged

JamesK

  • Reg Member
  • ***
  • Posts: 163

I can't really offer you any more advice. There's a couple of PDF's on the SkyUser forum which pretty much go through the same steps as what you have done following the YouTube video.

It's probably worth asking the same question on there as there will be more users with the SR102 who will have wanted to extract the username and password.

I know there used to be issues with WireShark running on Windows 8, and if you're running it on Linux you have to run it with root privileges so you can view the Option 61 text. So might be making sure you have the latest version, and forcing WireShark to run with Admin privileges, or even trying a different computer.
Logged
Virgin M500+Asus RT-AX86U

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33884
  • Trinity: Most guys do.
    • http://www.kitz.co.uk

Just a quick thought...  I wonder if the sky o2user@ login would work.   Not sure though

Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Neville Hillyer

  • Just arrived
  • *
  • Posts: 5

A bit late in the day but this may help others arriving here.

Please see my post at:

http://www.skyuser.co.uk/forum/extracting-sky-router-passwords/58491-difficulty-replacing-sr102-dg834pn-2.html

This has a simple Bash script (very easy on OS X and Linux) which gets name and password without WireShark.

Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43573
  • Penguins CAN fly
    • DSLstats

Thank you for that information.
Logged
  Eric

speedyrite

  • Member
  • **
  • Posts: 44

Another method for getting the login username and password from SR101 & SR102 is to use one of the online calculators
(either https://www.cm9.net/skypass/ or http://www.ph-mb.com/products/sky-calc )
selecting the Router Type as Sagen F@ST and entering the LAN MAC address of the SR101/SR102.
Logged

Neville Hillyer

  • Just arrived
  • *
  • Posts: 5

Another method for getting the login username and password from SR101 & SR102 is to use one of the online calculators
(either https://www.cm9.net/skypass/ or http://www.ph-mb.com/products/sky-calc )
selecting the Router Type as Sagen F@ST and entering the LAN MAC address of the SR101/SR102.

In addition to the MAC address these methods usually require another piece of information such as a key or password whereas my method discovers both in seconds.
Logged

speedyrite

  • Member
  • **
  • Posts: 44

In addition to the MAC address these methods usually require another piece of information such as a key or password whereas my method discovers both in seconds.

Quite so (and that info is readily available on a label stuck to the back of the router). Was just pointing out (for the benefit of mankind in general) that there is also a third method alternative to the Wireshark method and the script method you have described! ;)
Logged

Neville Hillyer

  • Just arrived
  • *
  • Posts: 5

My post on the Sky forum says that I could not get the numbers printed on the router to work which is why I wrote my Bash script.

Have you tried it?
Logged

speedyrite

  • Member
  • **
  • Posts: 44

Yes it worked for my SR101, and I recall reading a while back at least one report of success with it for SR102.
« Last Edit: August 31, 2015, 09:59:52 PM by speedyrite »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7390
  • VM Gig1 - AAISP L2TP
Re: April 2014 SR102 router - Wireshark unable to get correct DSL credentials
« Reply #10 on: September 01, 2015, 05:07:01 PM »

in my case I had to wait ages, probably close to 30 mins for the router to send out the dhcp request.

So one option is to be patient.

Others have reported that disabling dhcp on the pc and connecting it to the sr102 wan port is successful, but in my case It worked using a normal lan port and just waiting ages, you can filter dhcp packets in wireshark to make it easier.
Logged

Neville Hillyer

  • Just arrived
  • *
  • Posts: 5
Re: April 2014 SR102 router - Wireshark unable to get correct DSL credentials
« Reply #11 on: September 01, 2015, 05:42:23 PM »

I tested my method very carefully. It describes how to get an instant result. However, this may not be easy if you have a computer without Bash.
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7390
  • VM Gig1 - AAISP L2TP
Re: April 2014 SR102 router - Wireshark unable to get correct DSL credentials
« Reply #12 on: September 01, 2015, 06:01:57 PM »

I remember a bit more now, if nothing is happening after say 30 mins, login to the sr102 in the web gui, and it should be moaning about the net been down, and you can click an option on its wizard for it to try and fix itself, I think this may trigger a dhcp request.
Logged