Skip to main content

Bought a Cisco Linksys WRT54G2 v1 Router

My wifi router was purchased one years ago, for some reason it’s not stable now, sometimes lost package when I ping it. After chat with my friends Steven, he recommended Cisco Linksys WRT54G2 which he is using, a very stable router. You can install DD-WRT firmware and leverage more new free feature, such as NFS, firewall, VPN…etc. I’m newbie, I’ll try explore more on my spare time. That’s a used router on120RMB (around $20).

I successfully installed it and turned on internet after 30 minutes, but I cannot log in my VPS by SSH on port 21, then I asked Steven’s VPS SSH to give a try, his port is 443, I cannot connect his also!! I suspected firewall on WRT54G2 maybe blocked the two ports since the router much like a Linux system, you can even run iptables command. Finally I figured out my network provider blocked port 21 and 443, how funny it is that I spend 3 hours to investigated firewall, routing table, wifi setting, NAT…etc. But forgot my sweet network provider!!

大意了,大意了!没想到21和443同时被封了,搞得我以为是路由器设定问题,弄了3个小时!最后把VPS端口号改成8080,上的飕飕的。这让我想起弟弟的iPhone没有电话信号了,他做的第一件事是拿去经销商处修理,由于过年,需要30天才能返回,其实最简单的是去先换张卡看看是不是真的手机有问题。随着经验的积累,我们遇到事情好像也更复杂的看待,其实有时候复杂的搞不定还是可以从简单入手的,尤其是系统排错方面。不知IT项目实施方面是否也如此?

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 https://repo.ius.io/ius-release-el7.rpm yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm yum -y install https://packages.endpointdev.com/rhel/7/os/x86_64/endpoint-repo.x86_64.rpm yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.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 = "https://app.terraform.io/api/v2/organizations/ZHENGWU/organization-memberships?page%5Bsize%5D=100" 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 $Test.data.attributes.email