Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am currently running ubuntu 14.04 LTS on a laptop.
When I cruise in my sailboat I use a wifi extender manufactured by Ubiquiti. This device is configured by accessing its internal webserver, via an ethernet connection. By default, it is configured to respond to the address 192.168.1.20
For several years, I have been able to configure access this device with no difficulty. Now that I am running 14.04 LTS, every time I browse the address 192.168.1.20, I get an Apache2 default web page. It appears that the ability to access local IP addresses directly has been blocked, apparently for security reasons.
How can I restore this simple capability? I do not want to run a web server. All I want to do is access a physical device at 192.168.1.20
Incidently, I cannot change the device address without first accessing the device.
I configure and deploy Ubiquiti equipment as part of my job. As long as your laptop is assigned with an IP address in the same range as the radio network management address, you should be able to access it ok.
Check your assigned address. It's not using 192.168.1.20 perhaps?
Since 192.168.1.20 is the address to which the Ubiquiti device responds, this has in the past allowed me to access the web server built into the device.
Now, for a reason that I do not understand, Ubuntu 14.04 LTS is configured to have apache2 sitting on that address.
When I ping 192.168.1.20, I get a response, but I suspect that is apache2 and not the Ubiquiti device
Reset the wifi extender to stock/oem config with reset switch.
Set your ip in the subnet and range of the extender. If the stock is 192.168.1.1 then put a static .2 in your system. Then try to reach the config page.
I'd think it is almost impossible that the update to 14 did this or has anything to do with it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.