back at trying to make network, network

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

back at trying to make network, network

Gene Heskett-4
Greetings;
My home network is all hosts based, but has a gateway and uses the router
as a relay to my ISP's nameservers for addresses not in the hosts file.

But I'll be switched if I can make it work that way on a pi-3b running
stretch.

When it needs to use a dns lookup, it sends the dns request from
picnc.local, which is of course the ahahi address, 169.254.etc.etc

Somehow, I need to convince this thing it only has one address!!!
My current /e/n/i.d/eth0 file:
-------------
auto eth0

iface eth0 inet static
address 192.168.71.12/24
gatewasy 192.168.71.1
dns-nameserver 192.168.71.1
search hosts dns-nameserver
hwadress  192.168.71.12
--------------
adding the hwaddress just now, and restarting networking did get rid of
the ahahi supplied lines in an ip a report so it looks like this but now
a second request shows they are back.

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

And I have those 2 lines in /e/sysctl.conf that are supposed to shut off
the ipv6 stuff since I'm at least 100 miles from ANY ipv6 service.

/e/resolv.conf
nameserver 192.168.71.1
search  hosts nameserver

But if I ping yahoo.com, this is what I get so of course it fails:
pi@picnc:/etc $ ping yahoo.com
PING yahoo.com (72.30.35.9) 56(84) bytes of data.
From picnc.local (169.254.163.253) icmp_seq=1 Destination Host
Unreachable
From picnc.local (169.254.163.253) icmp_seq=2 Destination Host
Unreachable
From picnc.local (169.254.163.253) icmp_seq=3 Destination Host
Unreachable

I has as much of avahi killed as systemd will let me but I can't kill it
all. That dns resolution for yahoo.com is correct, so that working fine
but it being sent from a wrong address the rest of this system knows
nothing about.

There is still an avahi (chroot helper) running. So how do I get rid of
the from  hostname.local bs?


I can plug a raspian jessie u-sd card back into that pi, and it works
perfectly.

Thanks all.

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 | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

grumpy-2
On Sun, 16 Jun 2019, Gene Heskett wrote:

> Greetings;
> My home network is all hosts based, but has a gateway and uses the router
> as a relay to my ISP's nameservers for addresses not in the hosts file.
>
> But I'll be switched if I can make it work that way on a pi-3b running
> stretch.
>
> When it needs to use a dns lookup, it sends the dns request from
> picnc.local, which is of course the ahahi address, 169.254.etc.etc
>
> Somehow, I need to convince this thing it only has one address!!!
> My current /e/n/i.d/eth0 file:
> -------------
> auto eth0
>
> iface eth0 inet static
> address 192.168.71.12/24
> gatewasy 192.168.71.1
> dns-nameserver 192.168.71.1
> search hosts dns-nameserver
> hwadress  192.168.71.12
> --------------
> adding the hwaddress just now, and restarting networking did get rid of
> the ahahi supplied lines in an ip a report so it looks like this but now
> a second request shows they are back.
>
> 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
>
> And I have those 2 lines in /e/sysctl.conf that are supposed to shut off
> the ipv6 stuff since I'm at least 100 miles from ANY ipv6 service.
>
> /e/resolv.conf
> nameserver 192.168.71.1
> search  hosts nameserver
>
> But if I ping yahoo.com, this is what I get so of course it fails:
> pi@picnc:/etc $ ping yahoo.com
> PING yahoo.com (72.30.35.9) 56(84) bytes of data.
>> From picnc.local (169.254.163.253) icmp_seq=1 Destination Host
> Unreachable
>> From picnc.local (169.254.163.253) icmp_seq=2 Destination Host
> Unreachable
>> From picnc.local (169.254.163.253) icmp_seq=3 Destination Host
> Unreachable
>
> I has as much of avahi killed as systemd will let me but I can't kill it
> all. That dns resolution for yahoo.com is correct, so that working fine
> but it being sent from a wrong address the rest of this system knows
> nothing about.
>
> There is still an avahi (chroot helper) running. So how do I get rid of
> the from  hostname.local bs?
>
>
> I can plug a raspian jessie u-sd card back into that pi, and it works
> perfectly.
>
> Thanks all.
>

i have always disabled avahi
never had a use for it
double check
systemctl status avahi-daemon.service
systemctl status avahi-daemon.socket

i have 6 pi's running various things around the house
this is one

$ cat /etc/debian_version
9.8

$ ip addr
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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
     link/ether b8:27:eb:8d:37:e2 brd ff:ff:ff:ff:ff:ff
     inet 192.168.2.17/24 brd 192.168.2.255 scope global eth0
        valid_lft forever preferred_lft forever

$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 192.168.2.17  netmask 255.255.255.0  broadcast 192.168.2.255
         ether b8:27:eb:8d:37:e2  txqueuelen 1000  (Ethernet)
         RX packets 499797608  bytes 651308643127 (606.5 GiB)
         RX errors 0  dropped 1  overruns 0  frame 0
         TX packets 486196512  bytes 38063306645 (35.4 GiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
         inet 127.0.0.1  netmask 255.0.0.0
         loop  txqueuelen 1000  (Local Loopback)
         RX packets 1112  bytes 278979 (272.4 KiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 1112  bytes 278979 (272.4 KiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
0.0.0.0         192.168.2.1     0.0.0.0         UG        0 0          0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0

$ ps -ef | grep avahi
grumpy     22488 22395  0 10:50 pts/2    00:00:00 grep --color=auto avahi

Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4

On 6/16/19 11:58 AM, [hidden email] wrote:

> On Sun, 16 Jun 2019, Gene Heskett wrote:
>
>> Greetings;
>> My home network is all hosts based, but has a gateway and uses the
>> router
>> as a relay to my ISP's nameservers for addresses not in the hosts file.
>>
>> But I'll be switched if I can make it work that way on a pi-3b running
>> stretch.
>>
>> When it needs to use a dns lookup, it sends the dns request from
>> picnc.local, which is of course the ahahi address, 169.254.etc.etc
>>
>> Somehow, I need to convince this thing it only has one address!!!
>> My current /e/n/i.d/eth0 file:
>> -------------
>> auto eth0
>>
>> iface eth0 inet static
>> address 192.168.71.12/24
>> gatewasy 192.168.71.1
>> dns-nameserver 192.168.71.1
>> search hosts dns-nameserver
>> hwadress  192.168.71.12
>> --------------
>> adding the hwaddress just now, and restarting networking did get rid of
>> the ahahi supplied lines in an ip a report so it looks like this but now
>> a second request shows they are back.
>>
>> 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
>>
>> And I have those 2 lines in /e/sysctl.conf that are supposed to shut off
>> the ipv6 stuff since I'm at least 100 miles from ANY ipv6 service.
>>
>> /e/resolv.conf
>> nameserver 192.168.71.1
>> search  hosts nameserver
>>
>> But if I ping yahoo.com, this is what I get so of course it fails:
>> pi@picnc:/etc $ ping yahoo.com
>> PING yahoo.com (72.30.35.9) 56(84) bytes of data.
>>> From picnc.local (169.254.163.253) icmp_seq=1 Destination Host
>> Unreachable
>>> From picnc.local (169.254.163.253) icmp_seq=2 Destination Host
>> Unreachable
>>> From picnc.local (169.254.163.253) icmp_seq=3 Destination Host
>> Unreachable
>>
>> I has as much of avahi killed as systemd will let me but I can't kill it
>> all. That dns resolution for yahoo.com is correct, so that working fine
>> but it being sent from a wrong address the rest of this system knows
>> nothing about.
>>
>> There is still an avahi (chroot helper) running. So how do I get rid of
>> the from  hostname.local bs?
>>
>>
>> I can plug a raspian jessie u-sd card back into that pi, and it works
>> perfectly.
>>
>> Thanks all.
>>
>
> i have always disabled avahi
> never had a use for it
> double check
> systemctl status avahi-daemon.service
pi@picnc:~ $ sudo systemctl status avahi-daemon.service
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
    Loaded: loaded (/lib/systemd/system/avahi-daemon.service; disabled;
vendor preset: enabled)
    Active: active (running) since Wed 2017-11-29 17:59:27 +05; 1 years
6 months ago
  Main PID: 3734 (avahi-daemon)
    Status: "avahi-daemon 0.6.32 starting up."
    CGroup: /system.slice/avahi-daemon.service
            └─3734 avahi-daemon: running [picnc.local]

Jun 16 00:26:31 picnc avahi-daemon[3734]: Leaving mDNS multicast group
on interface eth0.IPv4 with address 169.254.163.253.
Jun 16 00:26:31 picnc avahi-daemon[3734]: Withdrawing address record for
fe80::7e94:f0c7:8cec:ce84 on eth0.
Jun 16 00:26:31 picnc avahi-daemon[3734]: Withdrawing address record for
169.254.163.253 on eth0.
Jun 16 00:26:31 picnc avahi-daemon[3734]: Joining mDNS multicast group
on interface eth0.IPv4 with address 192.168.71.12.
Jun 16 00:26:31 picnc avahi-daemon[3734]: New relevant interface
eth0.IPv4 for mDNS.
Jun 16 00:26:31 picnc avahi-daemon[3734]: Registering new address record
for 192.168.71.12 on eth0.IPv4.
Jun 16 00:26:34 picnc avahi-daemon[3734]: Joining mDNS multicast group
on interface eth0.IPv6 with address fe80::7e94:f0c7:8cec:ce84.
Jun 16 00:26:34 picnc avahi-daemon[3734]: New relevant interface
eth0.IPv6 for mDNS.
Jun 16 00:26:34 picnc avahi-daemon[3734]: Registering new address record
for fe80::7e94:f0c7:8cec:ce84 on eth0.*.
Jun 16 00:26:42 picnc avahi-daemon[3734]: Registering new address record
for 169.254.163.253 on eth0.IPv4.

> systemctl status avahi-daemon.socket
pi@picnc:~ $ sudo systemctl status avahi-daemon.socket
● avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket
    Loaded: loaded (/lib/systemd/system/avahi-daemon.socket; disabled;
vendor preset: enabled)
    Active: active (running) since Wed 2017-11-29 09:50:34 +05; 1 years
6 months ago
    Listen: /var/run/avahi-daemon/socket (Stream)

Nov 29 09:50:34 picnc systemd[1]: Listening on Avahi mDNS/DNS-SD Stack
Activation Socket.


So its running. Stopped and disabled both, restarted networking. No
169.254 bs left, but:pi@picnc:~ $ ping yahoo.com

PING yahoo.com (98.138.219.231) 56(84) bytes of data.

 From 169.254.163.253 (169.254.163.253) icmp_seq=1 Destination Host
Unreachable

 From 169.254.163.253 (169.254.163.253) icmp_seq=2 Destination Host
Unreachable

 From 169.254.163.253 (169.254.163.253) icmp_seq=3 Destination Host
Unreachable

 From 169.254.163.253 (169.254.163.253) icmp_seq=4 Destination Host
Unreachable

 From 169.254.163.253 (169.254.163.253) icmp_seq=5 Destination Host
Unreachable

 From 169.254.163.253 (169.254.163.253) icmp_seq=6 Destination Host
Unreachable

And I obviously need to tell t-bird this ain't a winderz boix so quit
using a crlf for EOL.

i have 6 pi's running various things around the house

> this is one
>
> $ cat /etc/debian_version
> 9.8
>
> $ ip addr
> 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
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>     link/ether b8:27:eb:8d:37:e2 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.2.17/24 brd 192.168.2.255 scope global eth0
>        valid_lft forever preferred_lft forever
>
> $ ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.2.17  netmask 255.255.255.0  broadcast 192.168.2.255
>         ether b8:27:eb:8d:37:e2  txqueuelen 1000  (Ethernet)
>         RX packets 499797608  bytes 651308643127 (606.5 GiB)
>         RX errors 0  dropped 1  overruns 0  frame 0
>         TX packets 486196512  bytes 38063306645 (35.4 GiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>         inet 127.0.0.1  netmask 255.0.0.0
>         loop  txqueuelen 1000  (Local Loopback)
>         RX packets 1112  bytes 278979 (272.4 KiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 1112  bytes 278979 (272.4 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> $ netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window 
> irtt Iface
> 0.0.0.0         192.168.2.1     0.0.0.0         UG        0 0         
> 0 eth0
> 192.168.2.0     0.0.0.0         255.255.255.0   U         0 0         
> 0 eth0
>
> $ ps -ef | grep avahi
> grumpy     22488 22395  0 10:50 pts/2    00:00:00 grep --color=auto avahi
> pi@picnc:~ $ ps -ef | grep avahi
> pi        5395  5088  0 03:02 pts/2    00:00:00 grep --color=auto avahi
>
Thanks Nik.

Cheers, Gene



Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Andrei POPESCU-2
On Du, 16 iun 19, 12:28:40, Gene Heskett wrote:
>
> So its running. Stopped and disabled both,

Please do recheck the output of

    systemctl status avahi-daemon.service
    systemctl status avahi-daemon.socket

> restarted networking.

Restarting networking might not have the effect you are hoping for.

> No 169.254
> bs left, but:pi@picnc:~ $ ping yahoo.com
>
> PING yahoo.com (98.138.219.231) 56(84) bytes of data.
>
> From 169.254.163.253 (169.254.163.253) icmp_seq=1 Destination Host
> Unreachable

Obviously there is some "169.254.xx.xx" left. Assuming you are using
ifupdown (/etc/network/interfaces) to configure your network please run

    ifdown eth0
    ifup eth0


or just reboot the system if possible.
 
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Cindy Sue Causey
In reply to this post by Gene Heskett-4
On 6/16/19, Gene Heskett <[hidden email]> wrote:

> Greetings;
> My home network is all hosts based, but has a gateway and uses the router
> as a relay to my ISP's nameservers for addresses not in the hosts file.
>
> But I'll be switched if I can make it work that way on a pi-3b running
> stretch.
>
> When it needs to use a dns lookup, it sends the dns request from
> picnc.local, which is of course the ahahi address, 169.254.etc.etc
>
> Somehow, I need to convince this thing it only has one address!!!
> My current /e/n/i.d/eth0 file:
> -------------
> auto eth0
>
> iface eth0 inet static
> address 192.168.71.12/24
> gatewasy 192.168.71.1
> dns-nameserver 192.168.71.1
> search hosts dns-nameserver
> hwadress  192.168.71.12
> --------------
> adding the hwaddress just now, and restarting networking did get rid of
> the ahahi supplied lines in an ip a report so it looks like this but now
> a second request shows they are back.


Hi, Gene.. Did you copy-and-paste that entry, or did you manually type
it up? The "gatewasy" line is why I ask.

You said you just now added "hwadress" so it wouldn't be the previous
problem, but it also looks like it might need another "d"? That's
again unless you manually typed that block up that way, but in
reality, it's all correctly spelled in the original file..

Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Andrei POPESCU-2
On Du, 16 iun 19, 15:15:08, Cindy Sue Causey wrote:

> >
> > Somehow, I need to convince this thing it only has one address!!!
> > My current /e/n/i.d/eth0 file:
> > -------------
> > auto eth0
> >
> > iface eth0 inet static
> > address 192.168.71.12/24
> > gatewasy 192.168.71.1
> > dns-nameserver 192.168.71.1
> > search hosts dns-nameserver
> > hwadress  192.168.71.12
> > --------------
> > adding the hwaddress just now, and restarting networking did get rid of
> > the ahahi supplied lines in an ip a report so it looks like this but now
> > a second request shows they are back.
>
>
> Hi, Gene.. Did you copy-and-paste that entry, or did you manually type
> it up? The "gatewasy" line is why I ask.
>
> You said you just now added "hwadress" so it wouldn't be the previous
> problem, but it also looks like it might need another "d"? That's
> again unless you manually typed that block up that way, but in
> reality, it's all correctly spelled in the original file..
Now that you mention it "gatewasy" is likely to create some problems as
well.

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4
In reply to this post by grumpy-2
On Sunday 16 June 2019 11:58:33 am [hidden email] wrote:

> On Sun, 16 Jun 2019, Gene Heskett wrote:
> > Greetings;
> > My home network is all hosts based, but has a gateway and uses the
> > router as a relay to my ISP's nameservers for addresses not in the
> > hosts file.
> >
> > But I'll be switched if I can make it work that way on a pi-3b
> > running stretch.
> >
> > When it needs to use a dns lookup, it sends the dns request from
> > picnc.local, which is of course the ahahi address, 169.254.etc.etc
> >
> > Somehow, I need to convince this thing it only has one address!!!
> > My current /e/n/i.d/eth0 file:
> > -------------
> > auto eth0
> >
> > iface eth0 inet static
> > address 192.168.71.12/24
> > gatewasy 192.168.71.1
> > dns-nameserver 192.168.71.1
> > search hosts dns-nameserver
> > hwadress  192.168.71.12
> > --------------
> > adding the hwaddress just now, and restarting networking did get rid
> > of the ahahi supplied lines in an ip a report so it looks like this
> > but now a second request shows they are back.
> >
> > 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
> >
> > And I have those 2 lines in /e/sysctl.conf that are supposed to shut
> > off the ipv6 stuff since I'm at least 100 miles from ANY ipv6
> > service.
> >
> > /e/resolv.conf
> > nameserver 192.168.71.1
> > search  hosts nameserver
> >
> > But if I ping yahoo.com, this is what I get so of course it fails:
> > pi@picnc:/etc $ ping yahoo.com
> > PING yahoo.com (72.30.35.9) 56(84) bytes of data.
> >
> >> From picnc.local (169.254.163.253) icmp_seq=1 Destination Host
> >
> > Unreachable
> >
> >> From picnc.local (169.254.163.253) icmp_seq=2 Destination Host
> >
> > Unreachable
> >
> >> From picnc.local (169.254.163.253) icmp_seq=3 Destination Host
> >
> > Unreachable
> >
> > I has as much of avahi killed as systemd will let me but I can't
> > kill it all. That dns resolution for yahoo.com is correct, so that
> > working fine but it being sent from a wrong address the rest of this
> > system knows nothing about.
> >
> > There is still an avahi (chroot helper) running. So how do I get rid
> > of the from  hostname.local bs?
> >
> >
> > I can plug a raspian jessie u-sd card back into that pi, and it
> > works perfectly.
> >
> > Thanks all.
>
> i have always disabled avahi
> never had a use for it
> double check
> systemctl status avahi-daemon.service
> systemctl status avahi-daemon.socket
>
> i have 6 pi's running various things around the house
> this is one
>
> $ cat /etc/debian_version
> 9.8
>
> $ ip addr
> 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
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
>      link/ether b8:27:eb:8d:37:e2 brd ff:ff:ff:ff:ff:ff
>      inet 192.168.2.17/24 brd 192.168.2.255 scope global eth0
>         valid_lft forever preferred_lft forever
>
> $ ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>          inet 192.168.2.17  netmask 255.255.255.0  broadcast
> 192.168.2.255 ether b8:27:eb:8d:37:e2  txqueuelen 1000  (Ethernet) RX
> packets 499797608  bytes 651308643127 (606.5 GiB) RX errors 0  dropped
> 1  overruns 0  frame 0
>          TX packets 486196512  bytes 38063306645 (35.4 GiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
>          inet 127.0.0.1  netmask 255.0.0.0
>          loop  txqueuelen 1000  (Local Loopback)
>          RX packets 1112  bytes 278979 (272.4 KiB)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 1112  bytes 278979 (272.4 KiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> $ netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window
> irtt Iface
> 0.0.0.0         192.168.2.1     0.0.0.0         UG        0 0        
> 0 eth0 192.168.2.0     0.0.0.0         255.255.255.0   U         0 0  
>        0 eth0
>
> $ ps -ef | grep avahi
> grumpy     22488 22395  0 10:50 pts/2    00:00:00 grep --color=auto
> avahi

All that is nice Grumpy,IF nettools were installed, but I've a chicken vs
egg here, I can't install nettools until I can make the network work.  
And its the only armhf on the local net. There is an arm64 or 2 I'm
trying to figure out what to do with them, but no more armhf's.

Thanks.

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 | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4
In reply to this post by Andrei POPESCU-2
On Sunday 16 June 2019 02:43:45 pm [hidden email] wrote:

> On Du, 16 iun 19, 12:28:40, Gene Heskett wrote:
> > So its running. Stopped and disabled both,
>
> Please do recheck the output of
>
>     systemctl status avahi-daemon.service
>     systemctl status avahi-daemon.socket
>
> > restarted networking.
>
> Restarting networking might not have the effect you are hoping for.
>
> > No 169.254
> > bs left, but:pi@picnc:~ $ ping yahoo.com
> >
> > PING yahoo.com (98.138.219.231) 56(84) bytes of data.
> >
> > From 169.254.163.253 (169.254.163.253) icmp_seq=1 Destination Host
> > Unreachable
>
> Obviously there is some "169.254.xx.xx" left. Assuming you are using
> ifupdown (/etc/network/interfaces) to configure your network please
> run
>
>     ifdown eth0
>     ifup eth0
>
>
> or just reboot the system if possible.
>
Did the reboot,   lost the unwanted ipv6 stuffs, but the 169.254.etc
stuff is still there.

pi@picnc>cd /etc
pi@picnc>sudo grep -R 169.254 *
pi@picnc>

So where else might it be hiding?

I have grep -R doing the whole thing, but theres 100+ gigabytes of ssd's
that will search.

> 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 | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

John Paul Adrian Glaubitz
In reply to this post by Gene Heskett-4


> On Jun 17, 2019, at 2:44 AM, Gene Heskett <[hidden email]> wrote:
>
> All that is nice Grumpy,IF nettools were installed, but I've a chicken vs
> egg here, I can't install nettools until I can make the network work.

What’s wrong with the tools from the iproute2 package? Those should be installed by default.

Adrian
Reply | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4
In reply to this post by Cindy Sue Causey
On Sunday 16 June 2019 03:15:08 pm Cindy Sue Causey wrote:

> On 6/16/19, Gene Heskett <[hidden email]> wrote:
> > Greetings;
> > My home network is all hosts based, but has a gateway and uses the
> > router as a relay to my ISP's nameservers for addresses not in the
> > hosts file.
> >
> > But I'll be switched if I can make it work that way on a pi-3b
> > running stretch.
> >
> > When it needs to use a dns lookup, it sends the dns request from
> > picnc.local, which is of course the ahahi address, 169.254.etc.etc
> >
> > Somehow, I need to convince this thing it only has one address!!!
> > My current /e/n/i.d/eth0 file:
> > -------------
> > auto eth0
> >
> > iface eth0 inet static
> > address 192.168.71.12/24
> > gatewasy 192.168.71.1
> > dns-nameserver 192.168.71.1
> > search hosts dns-nameserver
> > hwadress  192.168.71.12
> > --------------
> > adding the hwaddress just now, and restarting networking did get rid
> > of the ahahi supplied lines in an ip a report so it looks like this
> > but now a second request shows they are back.
>
> Hi, Gene.. Did you copy-and-paste that entry, or did you manually type
> it up? The "gatewasy" line is why I ask.
>
DarnedifIknow, but lemme look again. Damn, I'm blind...  And with plastic
eyes yet.

> You said you just now added "hwadress" so it wouldn't be the previous
> problem, but it also looks like it might need another "d"? That's
> again unless you manually typed that block up that way, but in
> reality, it's all correctly spelled in the original file..
>

No, that error was there too. Fixed, rebooted, didn't help.

> Cindy :)


Cheers Cindy, 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 | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4
In reply to this post by Andrei POPESCU-2
On Sunday 16 June 2019 04:35:51 pm [hidden email] wrote:

> On Du, 16 iun 19, 15:15:08, Cindy Sue Causey wrote:
> > > Somehow, I need to convince this thing it only has one address!!!
> > > My current /e/n/i.d/eth0 file:
> > > -------------
> > > auto eth0
> > >
> > > iface eth0 inet static
> > > address 192.168.71.12/24
> > > gatewasy 192.168.71.1
> > > dns-nameserver 192.168.71.1
> > > search hosts dns-nameserver
> > > hwadress  192.168.71.12
> > > --------------
> > > adding the hwaddress just now, and restarting networking did get
> > > rid of the ahahi supplied lines in an ip a report so it looks like
> > > this but now a second request shows they are back.
> >
> > Hi, Gene.. Did you copy-and-paste that entry, or did you manually
> > type it up? The "gatewasy" line is why I ask.
> >
> > You said you just now added "hwadress" so it wouldn't be the
> > previous problem, but it also looks like it might need another "d"?
> > That's again unless you manually typed that block up that way, but
> > in reality, it's all correctly spelled in the original file..
>
> Now that you mention it "gatewasy" is likely to create some problems
> as well.
>
So could hdadress, missing d, both fixed, rebooted, didn't help.

> Kind regards,
> Andrei

Thanks 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 | Threaded
Open this post in threaded view
|

Re: back at trying to make network, network

Gene Heskett-4
In reply to this post by John Paul Adrian Glaubitz
On Sunday 16 June 2019 09:05:54 pm John Paul Adrian Glaubitz wrote:

> > On Jun 17, 2019, at 2:44 AM, Gene Heskett <[hidden email]>
> > wrote:
> >
> > All that is nice Grumpy,IF nettools were installed, but I've a
> > chicken vs egg here, I can't install nettools until I can make the
> > network work.
>
> What’s wrong with the tools from the iproute2 package? Those should be
> installed by default.
>
> Adrian

Man pages with examples that don't work, or answer the question, are
worthless. Or in this case are NOT installed by default.

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>