Skip to main content

Hack D-Link Wifi Router

Someone setup a non-secure wifi around my apartment, I never connected it till yesterday since I worried it's may be a honeypot. I had some me time yesterday night, so I setup a virtual machine to connect the wifi.

Wireshark show me the guy had a XP workstation and a iPad. Port 137 opened. Iwas not  sure it's a honeypot since I don't think A high level hacker keep the port open on LAN.

Then I opened, I want to see was it possible to enable port mirror so I can captured packages. It turned to D-Link management web interface but I didn't have admin password. I thought it should be default password, but unfortunately the guy changed password.

After studied the interface and XML files, eventually I got previous wifi password and his PPPOE credential. People usually set same password everywhere, so I tried it on web interface...successful. I actually don't know anything about hack skill, but just a little knowledge of website code. Very interesting experience. :-)

Why I hacked it? Actually I want to learn how to use Wireshark. Another valuable thing is I find D-Link router is not proper secured.

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $