Re: Assorted arm-buster problems - network configuration
On Thursday 04 July 2019 03:16:31 andreimpopescu@gmail.com wrote:
> On Mi, 03 iul 19, 21:03:19, Gene Heskett wrote:
> > On Wednesday 03 July 2019 16:12:31 Reco wrote:
> >
> > And Gene moved. Question unanswered yet.
> >
> > > Hi.
> > >
> > > On Wed, Jul 03, 2019 at 02:57:35PM -0400, Gene Heskett wrote:
> > > > Regardless of what I do, I cannot get rid of the avahi junk in
> > > > an ip a report, so my local 192.168.xx.nn/24 net is the only
> > > > thing that works. pinging a net name like yahoo.com gets me a
> > > > successful address. But no response from yahoo because its
> > > > sending the ping from an avahi based address, which since thats
> > > > outside of my /24 netmask, doesn't get thru the router.
> > > >
> > > > So, how do I get rid of the avahi stuff?
> > > >
> > > > I've a nominally 10 machine 192.168.nn.xx that is 100% static
> > > > based on host files so I want avahi absolutely and totally
> > > > neutered, emasculated, gone Forever plus 100 years at least.
> > > >
> > > > How can I do that?
>
> It's not necessarily avahi doing that. A DHCP client might also
> configure a 169.254.*.* address for you if it doesn't receive a reply.
>
> In order to have the slightest chance of helping you it is necessary
> for you to provide the information as per below.
>
> Files should preferably be attached, to avoid issues with copy-paste.
>
> Please do not edit anything except to obscure private information
> (e.g. passwords or a public IP you don't want to post).
>
>
> 1. content of /etc/network/interfaces and all files under
> /etc/network/interfaces.d/
>
> (I seem to recall you are using ifupdown)
>
> 2. Full output of:
> apt list --installed 'network-manager*' # might be empty
> apt list --installed 'avahi*' # might be empty
> systemctl status systemd-networkd
> ip a # short for 'ip address'
> ip r # short for 'ip route'
>
> 3. Information on anything (and I do mean anything) else you might
> have done to your network configuration after installing buster,
> including but not limited to:
> * installing stuff, especially if from source
First, on a u-booting raspi you don't "install". You either download an
image and put it on a u-sd card with dd, or you generate your own image.
Which is what I have done by using a utility from guysoft called
RealtimePi, which takes the June 20th version of raspian buster lite
apart, and supposedly puts it back together with a realtime patched
version of a compatible kernel, which should have been a 4.19.50-rt-v7
kernel, but when put on a u-sd, and the u-sd booted, turns out to have
the unpatched kernel in it. Why I watched it spend an hour building the
older 4.4.114-rt-v7 kernel and then it didn't use it is something I have
not found yet in the build.log. Which I can't get to ATM because ssh
isn't working either.
I can't get any of that until I can make ssh work, which it is not at the
moment. ISTR if I restart it from its own console, it might work.
Depends on the phase of the moon because it might decide to use the 169
addresses for everything. these two lines at the top of /e/n/i.d/eth0
auto eth0
iface eth0 inet static
is supposed to tell n-m and company to keep their hands off that
interface, and plainly it is not. It is totally ignoreing the rest of
that file, so while I may get a valid address, but not one fixed
gateway|route. Sitting here. playing with ip on this machine, I finally
figured out how to get rid of the 169.254.xx.yy trash in the eth0 setup,
and its possible I might be able to put a postup command or two to clean
house and make it work, like I did with stretch on a rock64.
> * removing stuff (especially if not 'purged', dpkg -l would tell)
> * manual changes to files (deletions/permissions/etc.
> (especially those unnecessary "fixes" you call "neutering")
I will do whatever it takes to make it "Just Work". But so much has been
changed with buster that I don't really know where to start. Jessie ran
good, but realtime wasn't as real as needed, stretch runs a much better
realtime, but each "upgrade" has been harder and harder to make the
networking Just Work.
> For the record/archives: other users are not seeing your problems.
Am I the only holdout on the whole English speaking planet still useing
static networking configs? I really, seriously, doubt that. But I will
state that every release newer than wheezy has made it progressively
more difficult to make a staticly defined network work. Way too many
chefs stirring in the same pot is how I see it.
> Buster is - at least for me - the best Debian release yet.
It may well be, but its worthless to me running in a Faraday cage because
I cannot control the networking. And its worthless to me until I can get
a realtime kernel built into the u-sd. I build this stuff to do a job,
and if it can't do the job, I've got 1500 lbs of cast iron I can't
control to make it move.
> The problems you are seeing are, at least partially, of your own
> doing, most likely due to wrong configuration and an approach of using
> the equivalent of a shotgun to kill a fly and then complaining your
> walls are full of holes.
Sorry, I don't see it that way, I see a concentrated effort to make me
use dhcpd, instead of static, every machine in the system knows the
address of ALL the other machines on my local 192.168.xx.nn/24 network.
Using dhcp means I'd have to setup a 2nd this side of my router. I will
try to make ssh work later today, and I will reanswer this message if I
can do that.
> Kind regards,
> Andrei
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: