On Thursday 12 July 2018 18:04:54 Christian Knoke wrote: > Du schriebst am 12. Jul um 16:57 Uhr: > > On Thursday 12 July 2018 14:16:43 Christian Knoke wrote: > > > Gene Heskett schrieb am 12. Jul um 10:07 Uhr: > > > > > > hth > > > > Not yet. If I can't fix this tomorrow, I'll write another sd card > > with the original files. It worked until an update 2 or 3 weeks > > ago. > > Sorry that I ask again, but can you please check whether your > (static,ipv4) config is typed in correctly? Esp. no other config > interferes like in /e/n/i AND in /e/n/i.d/* ? I usually put everything > in interfaces and remove the source ... line in that file. > > RTNETLINK answers: No such process can mean, you're trying to set up a > *wrong* gateway address. > But the gateway IS the router. By way of 8 port switches, all these machines are 1 or 2 switches away from the router. A route -n from this machine, running wheezy yet: root@coyote:/etc# 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 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
And every other machine on this network will answer the same. Even a pi 3b running jessie: pi@picnc:~ $ sudo 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 except avahi has been disabled on that install. another machine: gene@GO704:~$ sudo route -n [sudo] password for gene: 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 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1 192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 I've already posted /e/n/i.d/eth0, but here it is again: root@rock64:~# cd /etc/network/interfaces.d root@rock64:/etc/network/interfaces.d# cat eth0 auto eth0 iface eth0 inet static address 192.168.71.11 netmask 255.255.255.0 gateway 192.168.71.1 Thats a direct copy/paste, so whats wrong with that. Other than the fact that its been rebooted twice since the address was changed from 192.168.71.2 to the 11 you see above, but ifconfig still says its on 71.2 right now. So where the heck is it getting the .2 address. Something in a recent (3-4 weeks past) update broke it, is the only conclusion I can come to. The only clue I might have is /var/cache/apt/archives/partial, which is empty but carry's a Jun 11 date when it was last touched. So presumably something was updated then that didn't effect it till it was rebooted again, at which point I lost access to the outside world. > https://serverfault.com/questions/437598/what-can-cause-rtnetlink-answ >ers-no-such-process-when-adding-a-route This doesn't actually describe what I am seeing. > > > > Christian -- 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>
