Thanks for your help Three responses follow.
To recap, here is:$ cat /etc/resolv.conf
# Generated by NetworkManager
search tew-818dru
nameserver 192.168.10.1
On Sat, 2018-08-18 at 21:03 +0800, Ed Greshko wrote:
What is the output of hostnamectl on your system
$ hostnamectl Static hostname: amito
Icon name: computer-desktop
Chassis: desktop
Machine ID: 118d9c2c0a1e4b51ab25e3ce8fd57219
Boot ID: 21b543bfb22049e0905befaac3a5851d
Operating System: Fedora 28 (Twenty Eight)
CPE OS Name: cpe:/o:fedoraproject:fedora:28
Kernel: Linux 4.17.14-202.fc28.x86_64
Architecture: x86-64
On Sat, 2018-08-18 at 17:51 +0800, Ed Greshko wrote:
This is a typical DHCP response.... As you can see, it tells the
client the IP
address, subnet mask, broadcast address, DNS server, and Default
router.
Frame 8505: 345 bytes on wire (2760 bits), 345 bytes captured (2760
bits) on interface 0
I don't have such a detailed record of the DHCP setup, but here is an
extract from the system log:
$ journalctl --boot | grep -i dhcp
Aug 19 09:26:47 amito NetworkManager[989]: <info> [1534696007.7446]
dhcp-init: Using DHCP client 'dhclient'
Aug 19 09:26:56 amito NetworkManager[989]: <info> [1534696016.7255]
dhcp4 (enp3s0): activation: beginning transaction (timeout in 45
seconds)
Aug 19 09:26:56 amito NetworkManager[989]: <info> [1534696016.9214]
dhcp4 (enp3s0): dhclient started with pid 1396
Aug 19 09:26:57 amito dhclient[1396]: DHCPREQUEST on enp3s0 to
255.255.255.255 port 67 (xid=0x26730e55)
Aug 19 09:26:57 amito dhclient[1396]: DHCPACK from 192.168.10.1
(xid=0x26730e55)
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5542]
dhcp4 (enp3s0): address 192.168.10.101
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): plen 24 (255.255.255.0)
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): gateway 192.168.10.1
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): lease time 86400
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): nameserver '192.168.10.1'
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): domain name 'tew-818dru'
Aug 19 09:26:57 amito NetworkManager[989]: <info> [1534696017.5543]
dhcp4 (enp3s0): state changed unknown -> bou
It looks like the DHCP setup message from the Trend server does request
the client (amito) to use search domain tew-818dru
On Sat, 2018-08-18 at 10:01 -0700, Samuel Sieb wrote:
This suggests that you might have connected this router to the main
one using a LAN port, which is a recipe for disaster if not
configured correctly. In that case, the Android device might get a
DHCP answer from the new router over the network which is how it
would show up there.
I find this a little perplexing. How else can this router be attached
to the main one except by using a LAN port? It is in fact connected to
port 4. Here is the main router (gateway)'s report of its status:
Name TEW-818DRU
Connection Type Ethernet
Connected to : AP 998
- Port 4
IP Address 192.168.1.70
IP Address Allocation DHCP
IP Address Type Private (NAT)
Hardware Address d8:eb:97:ef:e0:b7
Status On
IPv6 Address: None
I think the strange device, almost certainly an Android phone, is
getting a DHCP response from the secondary router (Trend); but why does
it appear in Trend's list of "Wired Connected Devices"? A bug in
Trend's firmware or something else, maybe more unsettling?
Suggestions:Turn off the DHCP server (and DNS if possible) on this
new router. If possible, set the router to get a DHCP address on the
LAN side. If you can't, then set a static address so that you can
access it in future. Connect this router to your existing network
using the LAN port. This should make things work the way you want.
I find this also perplexing. I think you're advising me that the best
thing is to use the secondary router (Trend) as a hub and let all name
resolution etc. be done by the main router (Gateway). This is
certainly desirable; but I don't think it's possible. Also, I think
you mean that the "static address" you refer to is a the address of
Trend as set by Gateway. In fact, Gateway has an infinite lease time,
so this should happen by default.