Read the statement by Michael Teeuw here.
Can't clone from GitHub
-
and I assume you can ping the router
route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 100 0 0 enp5s0so in my case 192.168.2.1
-
@sdetweil yes I can ping the router
-
@MMRPi1 I assume you can ping router from windows (
ipconfig /all, Default Gateway . . . . . . . . . : 192.168.2.1)but can’t ping the pi.
is there a firewall on the pi? open a terminal window and do
sudo iptables -L -
@sdetweil Don’t think so, it says ‘policy accept’ on all three entrys
-
@MMRPi1 weird… didn’t expect it… but u couldn’t access from ios…
-
@sdetweil I used to be able to about a week ago (both on the PC and iOS). It’s only very recently that it doesn’t let me in
-
Have you tried bouncing your router? If it thinks your devices are on different subnets it may be what’s keeping your network devices from connecting.
-
@bhepler but their addresses are 192.168.0.x so shouldn’t be different subnets, but worth a try I suppose
-
@sdetweil - Yeah, shouldn’t. The router should manage it all through DHCP but something is really weird here. Especially if it all worked before and suddenly the routing stopped to the point where the two devices can’t even ping each other.
-
Hrm. Okay, basic connectivity check. From the pi, please try the following two commands and tell us the results of each:
ifconfig | grep inet
and
curl www.abc.com
