Re: Assorted arm-buster problems - network configuration
On Thursday 04 July 2019 16:48:56 andreimpopescu@gmail.com wrote:
> On Jo, 04 iul 19, 11:40:30, Gene Heskett wrote:
> > > 1. content of /etc/network/interfaces and all files under
> > > /etc/network/interfaces.d/
> >
> > pi@picnc:~ $ cat /etc/network/interfaces.d/*
>
> Is below the literal output of the cat above?
>
> Please post also /etc/network/interfaces.
>
> > auto eth0
> >
> > iface eth0 inet static
> > address 192.168.71.12/24
> > gateway 192.168.71.1
> > post-up echo 1 > /proc/sysy/ipv6/conf/$IFACE/disable_ipv6
> >
> > Which the last line disables ipv6 on this machines mostly stretch
> > install.
>
> It doesn't, but IPv6 is not your problem anyway.
>
> > > (I seem to recall you are using ifupdown)
> >
> > What ever works. More often than not, a reboot.
>
> 'ifupdown' is the name of the package providing
> /etc/network/interfaces.
>
> > But if I reboot it from
> > here, I'll have to go to that machine and restart ssh, so lets start
> > with fixing that.
> >
> > > 2. Full output of:
> > > apt list --installed 'network-manager*' # might be empty
> >
> > pi@picnc:~ $ sudo apt list --installed 'network-manager*'
> > Listing... Done
> >
> > > apt list --installed 'avahi*' # might be empty
> >
> > pi@picnc:~ $ sudo apt list --installed 'avahi*'
> > Listing... Done
> > avahi-daemon/testing,now 0.7-4+b1 armhf [installed]
>
> In my understanding 169.254.*.* addresses are configured by
> avahi-autoipd, not avahi-daemon, so this is also not your problem.
I don't recall seeing it. In any event avahi-* has been purged.
> > > systemctl status systemd-networkd
> >
> > pi@picnc:~ $ sudo systemctl status systemd-networkd
> > ● systemd-networkd.service - Network Service
> > Loaded: loaded (/lib/systemd/system/systemd-networkd.service;
> > disabled; vendor preset: enabled) Active: inactive (dead)
> > Docs: man:systemd-networkd.service(8)
>
> systemd-networkd is also not running, so you can stop blaming systemd.
No, I won't as it created my no ssh problem. Editing some of the wants
files fixed that.
> > > ip a # short for 'ip address'
> >
> > pi@picnc:~ $ ip a
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> > group default qlen 1000 link/loopback 00:00:00:00:00:00 brd
> > 00:00:00:00:00:00
> > inet 127.0.0.1/8 scope host lo
> > valid_lft forever preferred_lft forever
> > inet6 ::1/128 scope host
> > valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> > state UP group default qlen 1000 link/ether b8:27:eb:d3:47:2d brd
> > ff:ff:ff:ff:ff:ff
> > inet 192.168.71.12/24 brd 192.168.71.255 scope global eth0
> > valid_lft forever preferred_lft forever
> > inet 169.254.163.253/16 brd 169.254.255.255 scope global
> > noprefixroute eth0 valid_lft forever preferred_lft forever
>
> This is not a problem.
It isn't? Then pray tell, why does it ping yahoo.com from a 169 address?
> > inet6 fe80::1445:918c:cf73:6a79/64 scope link
> > valid_lft forever preferred_lft forever
> > 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
> > pfifo_fast state DOWN group default qlen 1000 link/ether
> > b8:27:eb:86:12:78 brd ff:ff:ff:ff:ff:ff
> >
> > > ip r # short for 'ip route'
> >
> > pi@picnc:~ $ ip r
> > default dev eth0 scope link src 169.254.163.253 metric 202
>
> But this is...
>
> In addition to the full /etc/network/interfaces please post also the
> output of
Its unmodified, and contains only the line to source whatever may be in
the interfaces.d directory.
> pgrep -a dhcp
no longer exists. apt --purge dhcp made no detectable difference.
Its working correctly now with the killing of the dhcpd5 module and its
purging.
So I now know what will make it just work. Next is to figure out how to
get this kernel installed to that image so that 4.19.50-rt-v7 is booted.
Then I can build linuxcnc for it, I hope, but that mailing list tells me
that some linuxcnc dependencies have been removed from buster, so the
build will no doubt _not_ be fun.
There are folks here who will violently disapprove of my sledgehammer or
shotgun approach to this, and I would remind people that I bought these
things to USE, and whatever makes them usable is what I will do. As
shipped, the armhf images are NOT usable. Make them usable as shipped,
and I will use them as shipped. It really is that simple.
> Kind regards,
> Andrei
Thank you very much for trying to help Andrei, it in fact was quite
helpfull, as was a comment some else made about dhcp making up stuff
when there was no available server. Thats BS that will with the right
amount of rain, grow 200+ bushels an acre, it should return NOTHING AT
ALL except a no server found error if there is not a server.
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)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: