On Jo, 16 sep 21, 11:19:11, David Christensen wrote: > On 9/16/21 12:40 AM, Andrei POPESCU wrote: > > On Mi, 15 sep 21, 17:48:39, Hans wrote: > > > Am Mittwoch, 15. September 2021, 16:41:21 CEST schrieb nimrod: > > > Hi, > > > > > > got the same problem, when the ethernet interface is up, too and I am on wifi. > > > This a problem with the gateway settings. > > > > Unless my understanding of local networks is wrong, the gateway is not > > involved in communication between hosts in the same subnet. > > > Many residential/ SOHO Internet gateways a combination devices -- firewall, > router, DHCP server, DNS caching proxy, switch, Wi-Fi access point, etc.. > > > When LAN and/or Wi-Fi clients whose network interfaces are configured with > DHCP want to communicate with each other, the gateway provides the > information required to initiate that communication (e.g. DNS lookup, IP > addresses, MAC addresses, etc.), in addition to switching/ sending/ > receiving packets. Everything should "just work". > > > But, a client with a manually configured network interface (e.g. "static > IP") will be unknown to the gateway, and therefore unknown to DHCP clients. > The details of the manual configuration determine failure modes, which may > be asymmetric. I understood Hans's "gateway" to refer to the default gateway setting of each computer. Contacting other computers by their IP address should still work in most common setups, provided the addresses are in the same subnet. Admittedly, the OP didn't explicitly specify if pinging was done by IP address or DNS name, and indeed, DNS is more likely to depend on the residential gateway (instead of /etc/hosts or mDNS). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature