On 7/4/19, Gene Heskett <ghesk...@shentel.net> wrote: > On Thursday 04 July 2019 03:16:31 andreimpope...@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). >> > I have restarted ssh, so now thats working and I'm logged in. I will use > copy/paste but I'll do word wrapping by hand. >> >> 1. content of /etc/network/interfaces and all files under >> /etc/network/interfaces.d/ > pi@picnc:~ $ cat /etc/network/interfaces.d/* > 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. > >> (I seem to recall you are using ifupdown) > What ever works. More often than not, a reboot. 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] > >> 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) > > >> 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 > 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
I'm guessing that 1. your machine is set up to request an ip address via dhcp 2. the dhcp client software isn't smart enough to realize you've configured a static address on the interface and tries to get an address via dhcp anyway, fails, and assigns a 169.254.x.x address to the interface Best bet would be to turn off dhcp on that interface. I don't remember if I couldn't figure out how to disable dhcp or if it was just that I _really_ don't want anything of mine doing mDNS; in any case, I nuked avahi: $ apt list --installed 'avahi*' Listing... Done Regards, Lee