102
Ctrl-C
6y

!rant

I was in a hostel in my high school days.. I was studying commerce back then. Hostel days were the first time I ever used Wi-Fi. But it sucked big time. I'm barely got 5-10Kbps. It was mainly due to overcrowding and download accelerators.

So, I decided to do something about it. After doing some research, I discovered NetCut. And it did help me for my purposes to some extent. But it wasn't enough. I soon discovered that my floor shared the bandwidth with another floor in the hostel, and the only way I could get the 1Mbps was to go to that floor and use NetCut. That was riskier and I was lazy enough to convince myself look for a better solution rather than go to that floor every time I wanted to download something.

My hostel used Netgear's routers back then. I decided to find some way to get into those. I tried the default "admin" and "password", but my hostel's network admin knew better than that. I didn't give up. After searching all night (literally) about how to get into that router, I stumbled upon a blog that gave a brief info about "telnetenable" utility which could be used to access the router from command line. At that time, I knew nothing about telnet or command line. In the beginning I just couldn't get it to work. Then I figured I had to enable telnet from Windows settings. I did that and got a step further. I was now able to get into the router's shell by using default superuser login. But I didn’t know how to get the web access credentials from there. After googling some and a bit of trial and error, I got comfortable using cd, ls and cat commands. I hoped that some file in the router would have the web access credentials stored in cleartext. I spent the next hour just using cat to read every file. Luckily, I stumbled upon NVRAM which is used to store all config details of router. I went through all the output from cat (it was a lot of output) and discovered http_user and http_passwd. I tried that in the web interface and when it worked, my happiness knew no bounds. I literally ran across the floor screaming and shouting.

I knew nothing about hiding my tracks and soon my hostel’s admin found out I was tampering with the router's settings. But I was more than happy to share my discovery with him.

This experience planted a seed inside me and I went on to become the admin next year and eventually switch careers.

So that’s the story of how I met bash.
Thanks for reading!

Comments
  • 15
    Thanks for a great story ;)
  • 7
    That admin had class.
  • 3
    cool
  • 4
    I njoyed the story !
  • 3
    Sweet!!!
  • 2
    Nice! Nice! Nice!
    That's the kind of stories I like to hear!
  • 1
    @irene Haha, thanks! 😁
  • 1
    Thank you everyone for reading this story. I hadn't expected this kind of response. I'm starting to feel like home at devRant.

    I'm going to get those stickers now. 😎
  • 1
    Nice story.. btw how do you cover your tracks in this case?
  • 3
    @AnonymusPanther well, when you're logged in and someone else (admin) tries to login, they can see which IP has already logged in. This can then be looked up from LAN info to find device name. However, if you're using a self-configured IP, the same does not appear in LAN info. So, admin won't be able to trace the IP back to your device name. It is also possible to configure directly using Telnet. (something which I discovered later on)
Add Comment