Re: missing gw in route -n
On Friday 13 July 2018 10:09:30 Mark Morgan Lloyd wrote:
> On 13/07/18 13:45, Gene Heskett wrote:
> > On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
> >> On 13/07/18 02:00, Gene Heskett wrote:
> >>> 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.
> >>
> >> Possibly from an initrd file that needs to be rebuilt.
> >
> > That is not a grub using boot scheme, and I have not the knowledge
> > to do that. The booting of these things is as yet a mystery to me.
> > An ls -l of /boot might disclose the boot method to trained eyes:
> >
> > root@rock64:/etc/network# ls -l /boot
> > total 27048
> > -rw-r--r-- 1 root root 4660138 May 27 18:39
> > System.map-4.4.126-rockchip-ayufan-239 -rw-r--r-- 1 root root
> > 148020 May 27 18:39 config-4.4.126-rockchip-ayufan-239 lrwxrwxrwx 1
> > root root 59 Jun 7 21:32 dtb ->
> > dtbs/4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb
> > lrwxrwxrwx 1 root root 59 Jun 7 21:32
> > dtb-4.4.126-rockchip-ayufan-239 ->
> > dtbs/4.4.126-rockchip-ayufan-239/rockchip/rk3328-rock64.dtb
> > drwxr-xr-x 3 root root 4096 May 27 19:15 dtbs
> > drwxr-xr-x 3 root root 16384 Jan 1 1970 efi
> > -rw-r--r-- 1 root root 7940 Apr 27 11:26 filesystem.packages
> > -rw-r--r-- 1 root root 1 Apr 27 11:26
> > filesystem.packages-remove -rw-r--r-- 1 root root 3119706 Jun 7
> > 21:32 initrd.img-4.4.126-rockchip-ayufan-239 -rwxr-xr-x 1 root root
> > 19726344 May 27 18:39 vmlinuz-4.4.126-rockchip-ayufan-239
>
> And the last automatic updates were done on the 7th June- correct?
> Much stuff that I do these days is based on RPIs which don't use an
> initrd, but I had to go through this on a PC a few weeks ago after I'd
> moved some discs around: the old configuration was still stuck in the
> fstab file loaded from the initrd file.
>
> I think it was a simple update-initramfs -u that got me going, but
> (a) check your manpages etc. and (b) if EFI really is involved check
> whether the boot loader requires any file signing etc... I'm afraid
> I've only used EFI on Itanium and there only superficially.
The EFI directory is empty. These arm semi-clones have virtually no
identifiable bios.
But I did just now get it fixed, my syntax for route add was fubar, it
should have been:
root@rock64:/etc/network# cat make-missing-gateway.sh
route add default gw 192.168.71.1 dev eth0
I was missing the default and dev options. routes manpage sucks.
This was the answer to the question I asked several times in this thread
and which was universally ignored by 99% of the responders.
Thanks Mark. Perhaps this fix will be usefull to others.
--
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: