Hello guys,
I have established a home network (not connected to the internet) with a TP-LINK WR810N v.2.0. In order to connect to the host computer which is running an apache server, I can address it via its IP address. Trying to reach it by putting in the host computers hostname, nothing happens. Unfortunately the router’s firmware doesn’t offer a DHCP table and as it is v.2.0, openwrt is not supported yet as far as I know. Does anyone of you know if there is a way to enable all computers of the home network to gain access to my host computer by putting in the hostname (not the IP) of the host computer)?
Thanks in advance
Suffice
There might be a more elegant solution than this:
on each computer edit /etc/hosts putting the ip and name
127.0.0.1 localhost
xxx.yyy.zzz.aaa Apache server name
1 Like
Thank you a lot for your quick answer and your good and clever thought.
To clarify: It’s a project for a workshop in which different people are to access my host computer via wlan with their mobile devices.
Any other thoughts?
the easiest solution would be to run your own DNS server, so when people type in my-apache-server into their web browers URL they get redirected to your server and don’t have to worry about IP addresses.
3 Likes
I agree with prior answers, ie. using HOSTS (possible with mobile/tablet devices but a real pain) or using DHCP on a device with better functionality.
Your wireless-access-point (tpl thingy) can remain your wlan/wireless-access-point as long as dhcp can be disabled; and then use another device (pc or another router for dhcp, and have it just point to whichever devices acts as gateways).
Many [home] devices have a dumb-limited-http interface that hides options that few use (such as another external-gateway) but can be tricked by disabling their dhcp functions (and thus some populate fields from whatever device now does that function). How to do this is very device (even firmware) specific, and somewhat time-consuming, but possible for a huge number of home devices
1 Like