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

Re: need recommendation for a realtime kernel to build for an armhf



On Saturday 15 June 2019 06:00:10 pm grumpy@mailfence.com wrote:

> On Sat, 15 Jun 2019, Gene Heskett wrote:
> > Greetings;
> >
> > I am about to install a stretch on an r-pi-3b. Then let it update to
> > the latest, with an eye toward a buster update when its released.
> >
> > But this will be driving a lathe, so it needs the best latency
> > figures that can be obtained by later linux-rt kernels, prefereably
> > in the 4.19.whatever category.  I have some debs already built that
> > once installed, should handle that.
> >
> > Some later:
> >
> > armhf Stretch is now installed but host file style networking is not
> > making the transition from local domain to outside network because
> > any ping to an outside address such as yahoo.com IS NOT coming from
> > the local domain address, but the avahi-daemon returned address. I
> > my networking scheme there is no such machine defined anyplace. Only
> > "localhost" defined anyplace is 127.0.0.1 in the /etc/hosts file
> >
> > A sudo grep -R 169. * returns only those lines I commented out. and
> > restarted networking each time.
> >
> > Where the heck is machinename.local, defined as 169.254.x.x coming
> > from, and more importantly how do I get rid of it once and forever?
> >
> > ip a shows duplicate inet lines for eth0 and I can't get rid of this
> > one:
> >
> >   inet 169.254.163.253/16 brd 169.254.255.255 scope global eth0
> >       valid_lft forever preferred_lft forever
> >
> > ip r returns this:
> >
> > default dev eth0 proto kernel scope link src 169.254.163.253 metric
> > 202 169.254.0.0/16 dev eth0 proto kernel scope link src
> > 169.254.163.253 metric 202
> > 192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12
> >
> > And obviously I need to make the 3rd line the default.
> >
> > How do I fix this?
>
> systemctl stop avahi-daemon
> systemctl disable avahi-daemon
+ a systemctl restart networking.  Had no effect.

ip a:
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 eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::7e94:f0c7:8cec:ce84/64 scope link
       valid_lft forever preferred_lft forever
ip r:
pi@picnc:~ $ ip r
default dev eth0 proto kernel scope link src 169.254.163.253 metric 202
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.163.253 
metric 202
192.168.71.0/24 dev eth0 proto kernel scope link src 192.168.71.12

So I'm still confused.

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: