I just "unwatched" the att/ast repo (the repository for the ksh93 shell, which is currently seeing active development) because a couple of users have taken issues with the way the shell is being developed. It would be all well and good if they kept to the technicalities, but the comments on issues are mostly name-calling. I can't really handle that sort of stuff. It's childish and unprofessional.
hi everyone! having a bit of a weird issue, laptop1 can ssh to pc1 and pc1 can ssh to laptop2, but laptop1 cant ssh to laptop2 ("no route to host"), I used to be able to ssh from laptop1 to laptop2 until like 2 weeks ago, nothing has changed afaik
Checked that /etc/hosts doesnt interfere, checked IPTables... look good
This is what I got: > traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets > 1 Stephen (192.168.1.2) 3077.053 ms !H 3076.841 ms !H 3076.747 ms !H
pretty much the same: traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets 1 192.168.1.10 (192.168.1.10) 427.970 ms 428.055 ms 428.036 ms
I'm guessing pc1 is just using layer2 to find laptop2 where laptop1 is hitting a layer3 hop for some reason. Maybe you just need to flush dns on laptop1
It seems unlikely to be physical since pc1 can reach both but it probably wouldn't hurt to reconnect to the wifi on both and ensure you can still connect back and forth
thanks for the help Jesse :) at least now I know the problem is in laptop1. I need to go for a while, will probably come back next weekend if I dont manage to fix it