INTL 3:770/1 3:770/3
REPLYADDR bp@www.zefox.net
REPLYTO 3:770/3.0 UUCP
MSGID: 55aecefe
REPLY: <20240625192405.f104a800a1e06c299866c7a4@eircom.net> e44347eb
PID: SoupGate-Win32 v1.05
Ahem A Rivet's Shot wrote:
> On Mon, 24 Jun 2024 22:28:01 -0000 (UTC)
> wrote:
>
>> At this point both machines are on the same 192.168.1.y network, but
>> they don't seem able to communicate at all, simply reporting
>> "no route to host" from either end. Ping fails, losing all packets.
>> It looks like sshd is running, based on ps output.
>
> Is the WAP configured to block traffic between clients ? That seems
> to be the default with many consumer WAPs.
I think the answer is "no". There is an "advanced" tab in the router
config mentioning IP filters, but explains "Use IP Filters to deny
LAN IP addresses access to the Internet" which isn't my problem.
Both firewalls and DMZ are disabled. There's also a "block WAN Ping"
option, but that's to "Discard PING from WAN side" and disabled.
The Pi4 and Pi5 hosts can ping the printer, but the two Pi's can't
ping each other, nor will they answer ping from a Mac. Both Pi's
can self-ping on their assigned LAN address.
Thanks for writing!
bob prohaska
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 1/19 16/0 19/37 80/1 90/1 105/81 106/201 123/130 128/260
SEEN-BY: 129/305 142/104 153/757 7715 203/0 218/700 840 220/70 221/1
SEEN-BY: 221/6 242 360 226/17 30 100 227/114 229/110 111 112 113 200
SEEN-BY: 229/206 300 317 400 426 428 470 550 616 664 700 230/0 240/5832
SEEN-BY: 266/512 267/800 280/5003 282/1038 291/111 292/854 301/1 310/31
SEEN-BY: 320/119 219 319 2119 322/757 762 325/304 335/364 341/66 342/200
SEEN-BY: 396/45 423/81 460/58 633/280 712/848 770/1 3 100 330 340
SEEN-BY: 772/210 220 230 5020/400 5053/58 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 1 320/219 229/426
|
