On Sunday 24 September 2017 04:34:50 Mark Morgan Lloyd wrote: > On 23/09/17 20:00, Gene Heskett wrote:
> I'd suggest checking using traceroute -I and then looking at route > -n and/or ip route ls which should give you a bit more of an > indication of what's going on. IME this sort of thing is usually > because the router isn't NATting the entire 192.168.x.x range. As said before, traceroute is not installed. But I may have found a buglet. In the route -n output, no gateway has been assigned: root@rock64Sheldon:/etc/network/interfaces.d# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 202 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 202 0 0 eth0 192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 yet in /etc/network/interfaces.d/eth0 it is: allow-hotplug eth0 auto eth0 iface eth0 inet static address 192.168.71.2/24 gateway 192.168.71.1 ============================= Same stuff from the pi running jessie auto eth0 # regular network for coyote.den iface eth0 inet static address 192.168.71.12 netmask 255.255.255.0 gateway 192.168.71.1 And pi@picnc:~ $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.71.1 0.0.0.0 UG 0 0 0 eth0 192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 end of jessie version Of course its not going to work w/o a gateway, but wth? Need a coffee IV. Thanks Mark. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
