Hi,
I am not sure I understand your use case, but I guess what you want is connecting to the Omega2 from another computer? Or from another Omega2?
Question 1:
What about the /etc/resolv.conf? Could an entry there be a possible solution?
No. In OpenWrt, /etc/resolv.conf
is a softlink to /tmp/resolv.conf
, which in turn is autogenerated from information the Omega gets from your DHCP server, or when you manually configure IP and nameserver, from /etc/config/network
$ ls -la /etc/resolv.conf
lrwxr-xr-x 1 root root 16 Jul 29 2021 /etc/resolv.conf -> /tmp/resolv.conf
$ cat /tmp/resolv.conf
# Interface lan
nameserver 192.168.11.1
search mydomain.ch
What this means is that the Omega2 itself will use the specified nameserver when it wants to connect other hosts. So it has nothing to do with other computers connecting to this Omega2.
Question 2:
In further times using other distributions my solution was to edit the /etc/hosts and /etc/hostname and write a new line with "ip hostname" in it.
But within openWRT I cant find /etc/hostname.
Again, the hostname is something that in OpenWrt is managed via uci
(the universal configuration interface):
$ uci get system.@system[0].hostname
Omega2-xyz
$ uci set system.@system[0].hostname="newhostname"
$ uci commit system
$ uci get system.@system[0].hostname
newhostname
Should I create one to fix the problem?
No
And, while /etc/hosts
exists on openwrt, it is probably not what you are looking for. /etc/hosts
is to assign names to IP addresses for connections made from the Omega2 to other computers. It is a fallback when there is no nameserver in your network.
Question 3:
What else could I do? Meanwhile Im feeling totally hopeless, because I`m working on that since hours. Unfortunately I cant find any resolved.conf file to check out same configs like for example under Linux Mint. I read about configurations in /etc/init.d/network. Could this be a possible solution?
If you want to connect to your Omega2 by name rather than IP, you need a nameserver in your LAN that can provide that information. Usually that would be your internet router, running a local DNS server and including hostname information from DHCP.
Or you can use the so called DNS-SD (service discovery), which is a sort of distributed name server. The Omega2 supports this out of the box using the avahi
software. This allows you to use youomega.local.
style hostnames, however only from computers/browsers/apps that support this (macOS Terminal.app does out of the box, but otherwise usually you need to install a DNS-SD browser on the system you are connecting from before you can use *.local.
hostnames)