Traceroute after pinging mac from target: traceroute targetġ target.domain (192.168.1.126) 5.718 ms 3.204 ms 3.538 ms Tracepath from otherhost (wired, but linux): tracepath target Traceroute: wrote target.domain 52 chars, ret=-1Ģ traceroute: wrote target.domain 52 chars, ret=-1 Traceroute to target.domain (192.168.1.126), 64 hops max, 52 byte packetsġ * *traceroute: sendto: No route to host (The flags also differ a bit, but there are other entries with the same flags that do include a MAC address and expiry, so I'm not sure that's relevant.) For otherhost (.7), there is a MAC address and expiry time, but for target there is only link#5 and an ! in expiry. It looks like something is weird in the routing table. PING target.domain (192.168.1.126): 56 data bytesĨ packets transmitted, 0 packets received, 100.0% packet loss main switch is the only LAN device connected to the router (the other device is the WAN cable modem).otherhost is connected to the main switch.mac is connected to a switch which is connected to the main switch.targets are connected to a wireless AP which is connected to the main switch.However other-device in the instance above is also hardwired. Mac is plugged in to ethernet, targets are wirelessly connected to the same network (no guest mode, vlan, etc., but there might be other options I haven't considered). Not a sleeping NIC problem on the targets because other devices can communicate with the targets just fine (on all the same protocols). Targets do not respond to any connections from the mac (ping, ssh, http).
In one case, I could even use ssh -L 2222:target:22 other-device -N ssh localhost -p 2222 ping mac, and was then able to ssh to the target from the mac directly. Other devices on the network can ping the target just fine.
Mtu switch to phd d1 form android#
My network looks like this and I have all sorts of devices: android phones, tablets, raspberry pis, some of which my Mac can’t ping over WiFi.
0 kommentar(er)
