On Sunday 28 October 2018 08:43:33 Reco wrote: > Hi. > > On Sun, Oct 28, 2018 at 07:04:02AM -0400, Gene Heskett wrote: > > > Ever consider you're doing it the wrong way? > > > This will work: > > > > > > iface eth0 inet static > > > address 192.168.NN.12 > > > netmask 24 > > > gateway 192.168.NN.1 > > > > in 20 years, I have never seen that syntax used. What man page do I > > find that format in. > > interfaces(5), the usual place.
I just checked that man page on wheezy, jessie and stretch, and no examples are found using "netmask 24" address 192.168.##.##/24 is supposed to be understood as netmask 255.255.255.0, and has worked here forever. And remains in the man 5 interfaces page. And has Just Worked, until now with stretch. > > > -vvv is not documented, and I'm too lazy to dig into the source to > > > see if it does something at all. Normally used to expand the verbosity. Not all of these utility's understand multiples means noisier. And it does not cause the called functions to inherit the -v, so you get no feedback from them. IMO thats wrong, and the -vv SHOULD cause the listed subcalls to get a -v invocation. But I'm not steering this ship called Linux, so my voice is carried away by the wind. Also, I haven't ever seen an official definition of "CIDR", so its possible I need tutoring on that. IMO any man page that uses an acronym, needs to include its definition. > > > ifdown eth0 > > > ifup -v eth0 Will have to be done from its own keyboard unless a ; to separate them. That gets me: =========== root@rock64:~# ifdown eth0;ifup -v eth0 ifup: parsing file /etc/network/interfaces.d/eth0 ifup: configuring interface eth0=eth0 (inet) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/bridge run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/hostapd run-parts: executing /etc/network/if-pre-up.d/ifenslave + [ inet = meta ] + IF_BOND_SLAVES= + [ ] + [ ] + [ -z ] + exit run-parts: executing /etc/network/if-pre-up.d/vlan run-parts: executing /etc/network/if-pre-up.d/wireless-tools run-parts: executing /etc/network/if-pre-up.d/wpasupplicant /bin/ip addr add 192.168.##.2/255.255.255.0 broadcast 192.168.##.255 dev eth0 label eth0 /bin/ip link set dev eth0 up /bin/ip route add default via 192.168.##.1 dev eth0 onlink /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/000resolvconf run-parts: executing /etc/network/if-up.d/avahi-autoipd run-parts: executing /etc/network/if-up.d/avahi-daemon run-parts: executing /etc/network/if-up.d/ethtool run-parts: executing /etc/network/if-up.d/ifenslave + [ inet = meta ] + [ ] run-parts: executing /etc/network/if-up.d/ip run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/openvpn run-parts: executing /etc/network/if-up.d/upstart run-parts: executing /etc/network/if-up.d/wpasupplicant ======== and it all works again, with: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.##.1 0.0.0.0 UG 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.##.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 Thats from stretch on arm64/rock64. While booting to the armbian image only, debian-arm fails to set a gateway, and so does raspian. I half expected it not to boot raspian since the architecture was so different from the raspi 3b. > > > > What log file, on stretch, would I find that trace data in? > > > > > > Stdout/stderr, as documented by ifup(8). > > > > Too volatile, scrolled off screen by the remainder of the boot. I > > want a log file I can insert into an email. Then we'll all see whats > > happening. > > Er, Gene, -v is there for user invocations, not for init scripts. > /etc/init.d/networking uses ordinary ifup, as nobody will want seeing > all those gory implementation details at each boot. And they do seem to be gory, almost looks as if its looping, but not quite. > > > > Theres not anything in /v/l/syslog w/o the -v. > > > > > > And there should not be anything about ifupdown, unless someone > > > redirects stdout/stderr of /etc/init.d/networking to syslog. > > > > Howto? > > Don't. Simply don't. It requires wrapping with '| logger' every > ifup/ifdown at /etc/init.d/networking. > > Reco Maybe its time we let this thread die, it is working now, as I have other hardware problems to deal with ATM. With shipping delays delays from the Chinglish writers, till around thanksgiving here in the yuuh ess aye. Needless to say I've ordered spares. Thanks Reco. -- 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
