[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: missing gw in route -n



On Thursday 12 July 2018 13:27:20 Mark Morgan Lloyd wrote:

> On 12/07/18 05:00, Gene Heskett wrote:
> > Greetings;
> >
> > I have been playing the 10k monkeys scene trying to figure out how
> > to add a gateway entry to the route -n report on a rock64 with a
> > stretch/xfce install on it.
> >
> > Where does this assignment belong in a static defined eth0
> > configuration?
> >
> > I know several places where it doesn't work, but what I need to know
> > is where do I put, in what file, the "gateway = www.xxx.yyy.zzz" and
> > make it just work for a stretch install on a rock64.  Thats an arm64
> > family card.
> >
> > All I have been able to get out of route is the gibberishy help when
> > there is a syntax error.
> >
> > The obvious (to me that is) place would be
> > in /etc/network/interfaces.d/eth0, which has this:
> >
> > auto eth0
> > allow-hotplug eth0
> > iface eth0 inet static
> > address 192.168.71.2
> > netmask 255.255.255.0
> > gateway 192.168.71.1
> > dns-nameserver 192.168.71.1
>
> Start off with ifconfig -a to check your interface names, if you've
> got eth1 rather than eth0 look in something like
> /etc/udev/rules.d/70*. Working in /etc/network/interfaces, simplify
> your config to something like
>
> allow-hotplug eth0
> iface eth0 inet static
> 	address 192.168.71.2/24
> 	gateway 192.168.71.1
> 	dns-nameserver 192.168.71.1
> 	post-up echo ifup > /tmp/eth0
>
> Note that for the dns-nameserver to work you'll need the resolvconf
> package.
>
Its there, but resolv.conf is a real file because resolvconf has yet to 
make a link that is not empty except for these comments.

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN


> Look for /tmp/eth0 which should contain a message telling you that the
> "post-up" ran. If it's not there find what's going wrong, there's a
> file which in principle tells NetworkManager to never under any
> circumstances touch an interface but TBH I've yet to find a
> circumstance in which NM is less trouble than it's worth and very
> often I just tell systemd not to run it.
No such file(s) exist
root@rock64:~# ls -lR /var/tmp
/var/tmp:
total 20
drwx------ 3 root root 4096 Jul 12 13:12 systemd-private-08e8615f9c6645b3b603d3ddb01a1edb-rtkit-daemon.service-oGu62f
drwx------ 3 root root 4096 Jul 11 19:53 systemd-private-312cad7b6dbe429fa65c3602cf7c0a1d-rtkit-daemon.service-IpLjBC
drwx------ 3 root root 4096 Jul 11 19:50 systemd-private-6d2e2648c6174d879be768dd8f6946b6-rtkit-daemon.service-uSndig
drwx------ 3 root root 4096 Jun  7 21:48 systemd-private-8c0cc04acec746c59f974b045b7dd8ae-rtkit-daemon.service-AarJXq
drwx------ 3 root root 4096 Jun 23 13:17 systemd-private-951aa0a1a04f458fa51724cd9e218136-rtkit-daemon.service-K9V3BQ

/var/tmp/systemd-private-08e8615f9c6645b3b603d3ddb01a1edb-rtkit-daemon.service-oGu62f:
total 4
drwxrwxrwt 2 root root 4096 Jul 12 13:12 tmp

/var/tmp/systemd-private-08e8615f9c6645b3b603d3ddb01a1edb-rtkit-daemon.service-oGu62f/tmp:
total 0

/var/tmp/systemd-private-312cad7b6dbe429fa65c3602cf7c0a1d-rtkit-daemon.service-IpLjBC:
total 4
drwxrwxrwt 2 root root 4096 Jul 11 19:53 tmp

/var/tmp/systemd-private-312cad7b6dbe429fa65c3602cf7c0a1d-rtkit-daemon.service-IpLjBC/tmp:
total 0

/var/tmp/systemd-private-6d2e2648c6174d879be768dd8f6946b6-rtkit-daemon.service-uSndig:
total 4
drwxrwxrwt 2 root root 4096 Jul 11 19:50 tmp

/var/tmp/systemd-private-6d2e2648c6174d879be768dd8f6946b6-rtkit-daemon.service-uSndig/tmp:
total 0

/var/tmp/systemd-private-8c0cc04acec746c59f974b045b7dd8ae-rtkit-daemon.service-AarJXq:
total 4
drwxrwxrwt 2 root root 4096 Jun  7 21:48 tmp

/var/tmp/systemd-private-8c0cc04acec746c59f974b045b7dd8ae-rtkit-daemon.service-AarJXq/tmp:
total 0

/var/tmp/systemd-private-951aa0a1a04f458fa51724cd9e218136-rtkit-daemon.service-K9V3BQ:
total 4
drwxrwxrwt 2 root root 4096 Jun 23 13:17 tmp

/var/tmp/systemd-private-951aa0a1a04f458fa51724cd9e218136-rtkit-daemon.service-K9V3BQ/tmp:
total 0
root@rock64:~#  IOW, the */tmp's are all empty.

But ntpd is burning up the sd card, logging an attempt to access a 
timeserver about every 2 seconds.

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>


Reply to: