This is continuation of the previous article beginning to install Squid 3.5.4…, that is about the preparation before ready to install 3.5.4 on Ubuntu server virtual machine using VMware on windows. This method can be implemented to the Ubuntu Server Virtual Machine or to the real machine. As you may know on Ubuntu Server Virtual Machine using VMware we can not divide the hard drive into some partitions as manually. The partitions is created automatically by VMware itself. With this conditions we can start to build squid 3.5.4 as the transparent proxy on Ubuntu Server.
Increase the internet access speed significantly while saving quota bandwidth usage is the main goal of the open source squid development as the proxy server. This far Squid developers have many experiments and improvement to build the proxy server that more stable in high performance. Until the time this article was written, Squid have released version 3.5.4, squid 4 is still experimental. Different with squid 2.7, squid 3.5.x is need to be compiled to use this version. This would give more flexibility in the application and development of squid to build proxy server.
DNS Server is the database server which will be distributed and mapping the hostnames to the IP address and otherwise. This is the process which must be passed when we are connected to the internet to access any servers in the world. So when we use the specific dns server such google dns, we will follow the domain database rules on this server. For example if google dns has blocked any webhosting server, we will not be able to access the webhosting server using this dns server. I personally prefer to use google dns because the resolve dns response more quickly and widely, but this would depend on your purposes.
Firstly I do apologize to the respectable agratitudesign visitors, I personally still learn and research to find the solution in the case that I have found that’s all would like to write into the blog as a record of my research and lesson. I'm sure there some of you still disappointed about less of my response, I really sorry about it, many questions that sometimes makes me a bit stuck. Think about the concept, to resolve the problem, which is very likely different situations, but I thank you, that the questions of you sometimes as an inspiration to me.
After understanding the process to create internal hotspot web interface login page, we are going to go one step further to create external hotspot web interface login page using internal hotspot web interface that we have just created. In other word we are going to place the hotspot web login page files to the live server or website hosting file. So that when the hotspot client want to login to use internet hotspot, they will directed to the external hotspot web interface. Of course you must have the hosting account to put hotspot files to the live server.
Creating Internal Hotspot Web Interface Login Page is covering the process to create web page design, customizing the hotspot server variables inside the template web pages, styling the display of hotspot login pagein order to make it more attractive for the client. It could reflecting of the quality of your hotspot services. The styling of the hotspot login page gives a distinct impression, identity and professionalism for your hotspot network services that you have build. The hotspot client may use different types of media screen when they want to login to your hotspot network. Therefore bootstrap will help you to create a responsive design and flexibility of the style to the hotspot web interface.