On 24/01/2022 12:00, dorset-requ...@mailman.lug.org.uk wrote:
Send dorset mailing list submissions to
dorset@mailman.lug.org.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/dorset
or, via email, send a message with subject or body 'help' to
dorset-requ...@mailman.lug.org.uk
You can reach the person managing the list at
dorset-ow...@mailman.lug.org.uk
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dorset digest..."
Today's Topics:
1. LAN connectivity problem (Graeme Gemmill)
2. Re: LAN connectivity problem (Tim)
----------------------------------------------------------------------
Message: 1
Date: Sun, 23 Jan 2022 15:21:11 +0000
From: Graeme Gemmill <gra...@gemmill.name>
To: dorset@mailman.lug.org.uk
Subject: [Dorset] LAN connectivity problem
Message-ID: <1f39da2a-df73-7f82-fd63-d17e4dc05...@gemmill.name>
Content-Type: text/plain; charset=UTF-8; format=flowed
I would be grateful for suggestions to solve the following connection
problem.
In the following description, D stands for 192.168.1
My router, D.1, has a control panel that identifies the following
ethernet connected devices:
192.168.1.10?? ? f0:2f:74:1f:d0:99??? ?? y
192.168.1.16???? b8:27:eb:50:44:91??? y
192.168.1.3??? ?? f4:30:b9:83:84:1c???? y
192.168.1.6??? ?? 74:03:bd:0c:b0:38??? y
192.168.1.9??? ?? 40:16:7e:b4:09:e2??? y
y indicates that the device passes traffic to the WAN
My laptop, D.3 shown the following devices by ip neigh:
192.168.1.1??? enp1s0??? c4:ea:1d:e4:27:a2??? REACHABLE??? ? Y
192.168.1.10? enp1s0??? f0:2f:74:1f:d0:99?????? STALE ??? N
192.168.1.6??? enp1s0??? 74:03:bd:0c:b0:38??? STALE N
192.168.1.9??? enp1s0??? 40:16:7e:b4:09:e2??? STALE N
Y/N indicates ping success.
D.3 "knows about" D.6, D.9 and D.10 because they are in /etc/fstab as a
result of previously successful connections.
D.9 acts as a server and shows the following by ip neigh:
192.168.1.1??? ??? enp2s0??? c4:ea:1d:e4:27:a2?? REACHABLE??? Y
192.168.1.10 ?? ? enp2s0??? f0:2f:74:1f:d0:99????? REACHABLE??? Y
192.168.1.16??? ? enp2s0??? b8:27:eb:50:44:91 STALE?????????????? Y
192.168.1.6??? ??? enp2s0??? 74:03:bd:0c:b0:38 STALE?????????????? Y
D.10 is my main work PC, and shows the following via ip neigh:
192.168.1.1??? ??? enp5s0??? c4:ea:1d:e4:27:a2??? REACHABLE??? Y
192.168.1.16??? ? enp5s0??? b8:27:eb:50:44:91??? REACHABLE??? Y
192.168.1.6 ??? ?? enp5s0??? 74:03:bd:0c:b0:38??? STALE ??? Y
192.168.1.9??? ??? enp5s0??? 40:16:7e:b4:09:e2??? REACHABLE??? Y
D.6 ia a NAS box that both D.9 and D.10 can and do write to.
D.6, D.9, D.10 and D.16 are connected to D.1 via an 8-way Netgear hub
My problem: D.3 cannot reach D.9 or D.10, and neither D.9 nor D.10 can
reach D.3, despite all being connected to D.1
(I hope the attempt at tabulating this data survives the translation to
other mail clients)
Hi Tim. All IP addresses are static. Connection is ethernet in all
cases, transport by powerline adaptors.
ifconfig outputs for D.3, D.9 and D.10 are consistent. Firewall is off
on all three until this is resolved.
nmap reports:
#nmap -O 192.168.1.3
Starting Nmap 7.91 ( https://nmap.org ) at 2022-01-24 12:56 GMT
Note: Host seems down. If it is really up, but blocking our ping probes,
try -Pn
Looked up ping blocking, but /proc/sys/net/ipv4/icmp_echo_ignore_all is
0, so something else is blocking pings.
Reset of router and switch performed to no avail.
Running Wireshark on D.10, capturing packets to/from D.3
All frames say "Who has 192.168.1.3? Tell 192.168.1.10" (mostly)
So looking forward to further enlightenment!
Regards,
Graeme
--
Next meeting: Online, Jitsi, Tuesday, 2022-02-01 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
