Skip to main content

Port forwarding with Zyxel router and XAMPP

Better late than never. I really planned to have a home-based web server so that I can explore a little bit of systems administration, just simply. I'm not really much of an administrator but it would be cool if I know a bit about this stuff. I had a little background with PHP and web development so I think I can handle it. Gladly it's not that difficult. With a little bit of installations and configuration, and we're done.

First off, install XAMPP. Download the application from their website and install. Just accept the default options and we're good to go. I got a little info with XAMPP and Lithium for further exploration here. So accessing the host where you install the XAMPP will get you the web server's default page. In my case, it's localhost and it displays the XAMPP default page. Things are looking good.

I'll give details on installation of XAMPP later in my other blog post.

And now for the port forwarding bit. Port forwarding means you forward a port to a specific server hosting whatever you want. Be it a web server or an SMTP or anything you want. This can be done in the router. I use Zyxel as this is a fee package from my ISP so I'll be dealing with it. I must say if you have a different router than I am, I cannot guarantee a reply (or any help at all). Adding a new server to forward a port to can be done in NAT section under Network. You can login and go to Advanced Wizard to view the configuration. Go to Port Forwarding tab and add the server you want to host. In my case I added 192.168.1.35 (my dev PC) and I'm hosting port 8080 for my Apache Web Server.

That's it, ask a friend to access you public IP and share info with them.

Comments

Popular posts from this blog

Restoring .dat data to MSSQL

This is just a document in case I forgot to restore data files to MSSQL. I had this problem before when a colleague gave me a .dat files to be restored to SQL server. I had a 2008 version of the server and had no trouble restoring it. The problem is, I forgot how I did it when I had a new PC and I upgraded it to 2012 SQL server. But this is a simple task (although I had a full day remembering how I did it and I had no luck finding the solution from google). First off, click restore, like so I had trouble with the database whether or not to add a new database and restore the file to it, or not. Simple answer is no need. With the next image you can see that the configuration is very simple. Just set it to device as the source and find the .mdf file. It automatically displays a suggestion for the database name and you're done. Click OK and wait a couple of minutes for SQL server to restore the data. [EDIT] In case you are restoring a backup file without an extension. You c...

Python Hydrology

Recently I'm learning Python and encountered the Hydrology book. Had to upgrade some of python packages and some libraries needed to get working with the book. There is an instruction though about mostly using pip install packages need for the book. The problem is I can't get it work. It's missing some things so I did a little google and hopefully this is a compilation of the things I need to work with the examples of the book. First off, I updated the apt-get $ sudo apt-get update Next is I installed the pip package manager. I'm not too sure but I have Ubuntu 10 and it doesn't have the pip installed. So I installed using the command below. $ sudo apt-get install python-pip Now the development packages for python. $ sudo apt-get install python-dev Most of the examples uses the scientific number packages so I installed numpy and other packages I'm not quite aware of. It's just that some of the examples probably in the later part of the book use...

Setting Up IIS on a Local Network: A Developer's Journey

Today, I embarked on a mission to set up an IIS server on our local network. The primary objective? To create local network versions of our applications for testing and development purposes. Additionally, we're in the process of setting up a CI/CD server to automate our workflows. However, like many journeys, this one had its share of hurdles. The initial hiccup arose when I realized that .NET was installed before IIS, leading to compatibility issues. Despite attempting to install IIS through the control panel and tweaking .NET components, the problem persisted. "Nada." After some trial and error, a breakthrough emerged. The solution? Executing dism as an Administrator in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 directory: \> dism /online /enable-feature /featurename:IIS-ASPNET45 /all And just like that, the clouds parted, and the path forward became clear. With IIS up and running seamlessly, our developers rejoiced, and testing commenced with renewed vigor. H...