gene1934

And the email system for is emailing with me erroneos info about bedno report 2x a day, so call off the quard dogs, it been solved without any help from this forum. you've been yelling about dhcp w/out once offering me a single clue as to how I should configure it even when I showed you the results. FYI I have been doing odd things with little machines for a lot longer that most of you have been breathing on your own starting with an rca 1802 in 1978. Do any of you have a track record that long? That bit of production tooling for a medium market tv station was still in use 20+ times a day when the station burned to the ground in the late 90's. I prefer to call it efficiency since most production equipment at a tv station is so heavily used & long since worn out before the IRS lets them amortize the cost. I am also a CET, a test 95% of the EE's out there cannot pass. I call a backup server that draws 19 watts at full song in the middle of backing up 8 machines here, efficient. Took me a while to figure it out the hardware and around $1500 in hardware. But it works as fast as my cat6 wired local net can run.

I've wasted 2 days now, screwing around trying to make netplan work and not getting anywhere. So I've taken a screenshot of what works on my e5p. I will nuke the 25-04 image I have and dl a fresh one but to test that idea, I'll first get the card from the e5p and see if it works in this one. But first I'll dl an image of the e5p card. And I may have a clue dd died w/o an error at 64G of a 128G card. So now that image is being written to another 128G u-card to see if it becomes an e5p when booted and the network works in which case i'll edit the hostname and see if it is amanda when repowered again. It was pings yahoo.com like it has a license. At 192.168.71.122 at which point I edit the netplan to put it back at amanda's address of 192.168.71.2. If that works, and it did, install gfs2 & 57 deps and mdadm & see if the /raid6 appears on a pd reboot. It did as /dev/vg0/myraid so while this has been a looooong slog, it all works even if its not an approved method. That img has quite a pile of gcode as it been a 3d printer for over a year. burned up a hot end and 20+ kg of filament. All that can go. And its gone quite nicely so far, got the /raid6 stuff installed and its been making a new 6.18 initramdisk img for about 20 minutes. Assuming its found the raid6 and has to fsck 11.2 Tb it might take a while. The busy circle is still rotating. But its still rotating with a new msg, something about permissions despite me being root to run synaptic. But that did NOT prevent it from rebooting from a powerdown. Or preventing me from mounting the /raid6 after creating its mount point. And recovering from that raid6, the rsync based backup driver script that fills it. I'm logged into it from here and here is a df report: gene@amanda:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 385288 6424 378864 2% /run /dev/mmcblk0p1 60102260 12713940 46688204 22% / tmpfs 1926424 0 1926424 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 1926424 68 1926356 1% /tmp /dev/zram1 47960 1524 42852 4% /var/log tmpfs 385284 92 385192 1% /run/user/1000 /dev/mapper/vg0-myraid 11272913680 533576604 10739337076 5% /raid6 So it even thinks /dev/mmcblk01 is a 60G drive, apparently because the one I copied was a 64G, not a 128G like its label says. problem solved but I still haven't the foggiest what the real problem was, only that I burned up two weeks of my remaining life at 91 years old already. Now I need the fstab line that automounts it during the bootup.

which of course fails as nmtui it will not accept the dot separators in an ipv4 address needed to be entered in an ipv4 only situation. I'll repeat as I have said quite a few times already, that I, in weston wv, am at least 100 miles from ANY ipv6 enabled net access. There surely are some ipv6 in pittsburg pa., 150 miles north, maybe in Charleston, 100 miles south. I have battled this using armbian-config and in using that microscopecly tiny moving radiation symbol at the top right of the xfce4 screen. If that is a defense to prevent ipv4 addresses where ipv6 is expected, change the box color so we know it can be skipped in real estate not yet blessed with ipv6 addresses. We are NOT mind readers any more than you are, but this particular group off us is about a 3/4 million in the whole state where flat ground to build a house on is measured in the gallons of diesel fuel to make it flat enough to build on. Fix nmtui so its actually usable and do a respin. while at it, fix whatever prevents our mounting it to edit such stuff before 1st boot. That restriction is a huge pain in the ass too. fdisk tells us its dos partition for sdc with an ext4 sdc1, but when we attempt to mount it, the ext4 cannot be found. That restriction is also present in the 25-5 release. Yet it boots & almost runs. next try?

You mix up 2 things: - 'msdos filesystem' which usually means 'FAT' - 'msdos table' which usually means 'MBR partition table' agreed Both can be up to 2 TeraBytes when sector or cluster size is 512 bytes. So no reason to change to GPT. Changing to GPT (with standard 128 entries), will use the same space as where the U-Boot bootloader is located on SD-card for older Arm chips, like Allwinner A20 (original bananapi). So risk is un-bootable. which seems to be the case. but it sure as hell blocks mounting and working on the card b4 network is enabled. Why? the error reported is can't find ext4 filesystem. I'll rewrite it just to be sure its pristine. Because it did mount but only lost+found is there. next?

what is installed to be similar to tcpdump since tcpdump is not installed? the date is off about 11 months in the past which disables net resolution in dd-wrt. Apparently ARP is in play here, as I am seeing lots of this in a tcpdump =ieno1|grep amanda here on this machine but I see no answers: 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell 0.0.0.0, length 46 16:42:20.926695 ARP, Request who-has amanda.coyote.den tell amanda.coyote.den, length 46 16:42:21.470873 ARP, Request who-has amanda.coyote.den tell amanda.coyote.den, length 46 16:42:23.288701 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:24.320147 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:25.344176 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:26.370963 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:27.392224 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:28.416249 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:29.445598 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:30.468289 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:31.488315 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:32.513828 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 16:42:33.536356 ARP, Request who-has router.coyote.den tell amanda.coyote.den, length 46 So the protocol is at least transmitting from amanda. This is evidence of dd-wrt ignoring the wrong timestamp because amanda's date is about 11 months out of sync. there is no settime installed so there's no way for be to manually fix that. I got this bit of info by commenting out the "pool" lines forcing chrony to use the "server 192.168.71.3 iburst" in the chrony subdir servers.d/ file. So I wrote another copy of the latest Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img to another new 128G card, and fdisk then id's it as having an msdos partition table, skipping 8k and having a 6.4G ext4 as /dev/sdc1 and undefined for the remainder of the card. So I quit fdisk and ran gparted on /dev/sdc/ and selected data recovery. Which warned that it would take a long time, 6.5 hours later its still scanning. blue bar slowly marching back and forth in the progress line at the bottom of the gparted screen. Hopefully recovering enough data to write a valid ext4 partition table & see if /dev/sdc1 is mountable AND bootable. I have since found a cli reboot won't, but a powerdown will if the card was written with a bs=4096. That is where I am with backups of the whole houses still sitting in a /raid6 I can't rebuild w/o net access to install both gfs2 and mdadm from the repo's. So this is a trail report, not a success story. if this fails. I get a 6 pack of 32Giggers which I know WILL work with an msdos table. But that doesn't give the cards adequate room to do housekeeping meaning they will fail in less then a year. Once working I have not had a failure of a 64G card or a 128G card.

I'm sorry but, lmao, this is entertaining to read. The sd card is OBVIOUSLY corrupt, it even TELLS YOU THAT in what you posted. But you think what I am seeing should tell me it fubar. That fact that this configuration works perfectly for 6 or 7 other machines in this house long string of cat5 or cat6 cable seems to be blowing right on by. This can't be true for all 4 u-sd cards I''ve tried. The last 2 were brand new, even faster rated cards, but all are 128gig sandisk's 1: the image itself has a dos table, which doesn't work above 32gigs acc what I have read and this prevents mounting the written images for installation in a card reader, but the used partition is ext4, so it boots ok but takes a long time because the net failure blocks the boot for many minutes 2: so I back up to a 25_05 image, and at one time had it booting the 6_18 kernal, but still no net which is the original problem. ATM I am wasting my time on a 25_05 build image which is running just fine on another bpi-m5 driving a 3d printer about 10x faster than OOTB. So I'd suggest you pass this one off to someone who knows how to make a 50 line /etc/hosts file work without a dhcp because I'm doing it on 2 other wintel boxes, an rpi4b running bookworm and 3 bpi-m5's running noble on 3d printers. The best I can do is post a pix of the 'netplan status --all" screen and somebody tell me whats wrong instead of berating me for not running a dhcp server properly.

Ambian-imager requires a glibc 3 versions newer that this bookworm amd64 has, won't run at all. restricting dd to bs=512 gets only 2something megabytes a second, glacially slow. The more usual bs=4096 is 50x faster, niether of which reports any write errors. And its booted and configured. time about a month off. I run ntpsec on this machine so I'll follow the /etc/chrony/README and assign a source address by number. but ip a shows only an active ipv6 address while ip r returns nothing. hostname is bananapi-m5 which is unk on the local net. IOW its booted but network is only ipv6 & no route of either flavor is assigned. Is this exactly how it was spun to be? I've brought the card back to my reader, and will edit the /etc/hostname to match its ID for 192,168,71,2 in the /etc/hosts file I'll install. And reboot it. but the card won't mount despite the fact that it boots. from this bash xfc4 terminal: root@coyote:/etc# mount -t ext4 /dev/sdc1 /mnt/sdc1 mount: /mnt/sdc1: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. dmesg however has no additional info. only this: [1618874.568139] sd 37:0:0:0: [sdc] 249737216 512-byte logical blocks: (128 GB/119 GiB) [1618874.568944] sdc: detected capacity change from 0 to 249737216 [1618874.569933] sdc: sdc1 [1619402.494452] loop0: detected capacity change from 0 to 12943360 [1619402.494871] EXT4-fs (loop0): VFS: Can't find ext4 filesystem [1619458.923461] loop0: detected capacity change from 0 to 12943360 [1619458.923910] EXT4-fs (loop0): VFS: Can't find ext4 filesystem as I made two attempts to mount it. it loads and boots normally when installed in the bpi-m5. So other than the extra server line I just put in /etc/chrony/sources.d/ which doesn't work because no ipv4 net is even available AND the nearest ipv6 enabled anything is a minimum of 125 miles from me, its about as useful as the teats on a bore hog. Neither is the thought of editing on that tiny screen, the 40 or so lines of /etc/hosts that make up my /etc/hosts file. Doubly frustrating is the fact that the mouse speed is measurable fraction of C speed and totally disappears when inside the xfce4 terminal borders. But installed in the bpi-m5 it boots normally. back in my reader: root@coyote:/etc# e2fsck /dev/sdc e2fsck 1.47.0 (5-Feb-2023) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/sdc The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> Found a dos partition table in /dev/sdc ???????????? wtf??????????? And I get the same result for /dev/sdc1 obviously something is screwed. So I unpackedca new 200mb writeable sandisk u-sd & wrote the new image to it. fdisk then says its a dos partition table. Can a "dos" table be used at all on a 128gb card? I've heard not but don't know where the failure is. ipa shows only ipv6, ip r shows nothing. The only thing that could be used for net config is armbian.config which I think is NetworkManager . but that's by now known not to work. So whats left????? IOW what the hell is being used to configure network NOW with a 6.18 kernel ???? And how do I use the new tools if any, to set it up for a network address on 192.168.71.2, an ipv4 address THAT WORKS FOR EVERYTHING??????? Or do I go back to the soon to expire Armbian_25.5.1_Bananapim5_noble_current_6.12.28_xfce_desktop.img which I am using 2 more times here in front of klipper driven 3d printers. And which if asked to apt update, now want around 430 new files to do the update but failing in the make a new initrd stage. Start by putting a gpt partition table in the xz with a respin. And stop assuming that the whole planet has ipv6 connectivity, central WV is not the only ipv4 island on this planet so blessed.

So I'm still doing s-thing wrong with dd. What is correct for this later spin? using 128GB cards.

your card imager needs a CLIBC_2_38, 3 versions newer than my bookworms 2-35, so I'm stuck at dd.

Because I know little to nothing about systemd, I have not touched it. If it is enabled, and IDK how to fix it if it was enabled in the .img. if so that is a bug & is a reason for a respin. Its finally done but probably won't mount as dmesg says it cannot find the ext4 file system. So another ugly thought crosses my curious mind, what is the DEFAULT file system, btrfs?

Please forget I ever mentioned dnsmasq, it exists only in the router where its working perfectly for 7 of the 8 machines here. w/o any man pages I haven't a clue how to run any of the systemd stuff so any config changes that need to be done after 1st boot in order to enable /etc/hosts for local lookups is equ to asking 10k monkeys to retype all of Shakespear's work w/o a single typo. We both know that aint gonna happen b4 the universe runs down in another 500 billion years, So, I am going to rewrite that img to a fresh 128G u-sd, change the /etc/hostname to amanda and rewrite the the /etc/hosts file with mine. Then you tell ME what to do via systemd to make a user "ping -c1 yahoo.com translate" to its dns address in <1.5 milliseconds. That rewrite will take at least an hour. maybe into 2 because the only wat to get a boot able image out of that respin is with dd if=/dev/zero bs=512 count=20 of=/dev/sdc to wipe the u-sd card. then dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc option bs=4096 is much much faster, only about 12 minutes to write but will NOT boot nor will it mount as /dev/sdc1 to /mnt/sdc1 So ATM its being written at bs=512, hoping it will work. That takes well over an hour. You have an image writer, "Armbian.Imager_1.2.5_amd64.AppImage" which has no manpage, a useless help screen and has never written a bootable .img file to any sd card since I dl'd it in jan 25. I haven't even bothered to try it as it this time as apparently burns up any u-sd card I've tempted it with so good but cantankerous old dd to the rescue. That, and 45 years a DM-II is slowly taking my eyesight because of macular-degeneration, not your problem of coarse, but mine at 91 yrs old. But saying dd is slow is an understatement, glacial is a better description. from the shell doing the writing: root@coyote:/home/gene/Downloads/armbian# dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc status=progress 6230856192 bytes (6.2 GB, 5.8 GiB) copied, 2939 s, 2.1 MB/s

In this local network, there is only one name to address configured in dd-wrt. dnsmasq The only true dns server is at my ISP and its been that way here since RH5.0 in 1998. I have NO M$ experience in my personal history, coming into modern computing by way of a TRS-80 Color computer running os-9, to amigados, about 10 of them as I drug WDTV-5 into the computer age when I became the Chief Engineer in 1984, but I started computing in 1978 at KRCR-12 in Redding Kalipornia. Writing a utility to prepare an automatic station break machines tapes for air that ran on an RCA-1802 and 4k os static ram that cost $400 back then. But lets get back on topic. What I want for outside names NOT in /etc/hosts: the query gets passed to the router at 192.168.71,1:53 where dnsmasq checks to see if its in its cache, and failing that, fwds the query to the dns server at my ISP for resolution. That address is not known on my side of the router. This typically adds about 1.5ms to the ping time. And nowhere in that chain fails this sequence EXCEPT this new install on a bananapi-m5. And I don't have to screw around maintaining a separate dns server of any kind. That is several times the amount of monkey business of cp-ing a common hosts file around is. But you want to insist on a dns server behind every RJ-45 jack in the house. I don't understand the Why? This is simple, quick and bulletproof until somebody decides to fix a perceived security hole, WHICH DOES NOT EXIST IF the router is reflashed with dd-wrt. I have not been touched since finding out about it in yr 1999-2000. Including a decade of running my own web page right here on this machine, stopped only because the spiders refused to honor my robots.txt. So I was paying bandwidth penalties of $150 or more a month on an SS income with my upload bandwidth filled by the robots from mj12. Whoever the hell they are. M$ spiders were in there too. People interested in my stuff couldn't get a word in edgewise. So please tell me where in the resolv.conf area what to edit to make it work, cuz I'll do it and a chattr +i on it to make it permanent. But the fix for debian bookworm, didn't fix this.

the xfce4 desktop version, specficallly: Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img after unpacking the xz version. The previous version that needed 430 some updates also had the mdadm stuff preloaded and had no trouble recovering the /raid6 once I had created the mount point with a mkdir /raid6. this one fails on all counts so, no entries other than control in /dev/mapper. So I'm assuming the first thing I need to install once networking is working is mdadm. But without an external network I'm locked out of everything else. Very frustrating. gene@amanda:~$ ls /dev/sd* /dev/sda /dev/sdb /dev/sdc /dev/sdd /dev/sdd2 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde /dev/sdf /dev/sdg So all the drives are there but not recognized as the raid6. The odd /dev/sdd is probably the 1T 2.5" lappy drive I put in for a faster /swap and had plans for its use as a scratchpad drive for amanda's use but is essentially just 50G of swap now. So what do I edit to fix the network ???

NetworkManager is how I have been trying of configure end0 but it won't run by itself, ONLY when armbian-config runs it as a client. IDK if I can copy/paste its show me output.

gene@amanda:~$ resolvectl status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 2 (end0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 192.168.71.0 DNS Servers: 192.168.71.0

untouched and wrong as can be: # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search . Damn, doesn't anyone use /etc/hosts for small home networks anymore? Toss in that you don't install ANY manpages so us users are running blind 99% of the time. Thanks bedna.

the router reflashed with a recent dd-wrt runs dnsmasq, which caches the ISP. If that fails it query's the ISP's server, which works fine for the other 7 machines here.

no wireless is configured except the BT mouse, which works fine.

This system has been running for several months months as a backup server with a nobel release about a year old, maybe some older, using two usb3 7 port hubs because 1 hub could not handle the current draw of 5 TSMC 4T SSD's using startech usb3.1 cables to connect 5 if them in a /raid6 configuration for an 11.1 Tb drive. But I decided to do an as sudo -i, "apt update" and was advised that would update about 430 files so I figured I'd do an apt update -y, then and apt --purge autoremove". Unforch it went into lala land while making a new initrd. After about 20 minutes I did a powerdown to be greeted by a repeating loop indicating there was no network. So I dl'd & wrote the month old 26.03 release. Which after getting chrony to work using my own local ntpsec, finally got the correct time and I'm able to login both directions using ssh me@machine assigned address, but no outside my local net addresses are found, dhcp isn't working. It is supposed to first query /etc/hosts wich does work, but if that doesn't resolve the name in dnsmasq, the router then query's the dns server at my ISP, which works for the rest of my 8 machines here, but does Not work for the 26.03 just released a month ago. ip a reports: 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 noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether be:63:9c:35:dd:4f brd ff:ff:ff:ff:ff:ff inet 192.168.71.2/24 brd 192.168.71.255 scope global noprefixroute end0 valid_lft forever preferred_lft forever inet6 fe80::bc63:9cff:fe35:dd4f/64 scope link valid_lft forever preferred_lft forever ip r reports: 192.168.71.0/24 dev end0 proto kernel scope link src 192.168.71.2 metric 100 gene@amanda:~$ A ping -c1 yahoo.com kills enough time its several seconds before it reports "network is unreachable" Can you see whats wrong, or give me the newer tracing tools to find the error? Thank you.

thank you. I'l give that a try when I wake again.

How best to do that? I've been treating systemd like a rattlesnake which I've seen in record breaking size, 7 feet long and the size of my calf. I was about 6, my stepfather was farming, had come in for lunch, opened the door to go back out and plow, slammed the door, reached over it for a cheap busted shotgun and a shell. reopened the door and took the head off it. 85 years ago. I haven't had a whole lot of use for a rattlesnake since although I've seen hundreds. Blacksnakes OTOH are goodfellows. They keep the rodents away by eating them.

The puzzle seems to have resolved itself. I gave up and shut the printer off about 04:00 this morning and went to bed. Got back up, powered it on about 08:30, and its all working, updating 304 pkgs right now. It was rebooted at least 15 times as I worked last night w/o any affect. What the hell is the diff between a reboot and a full powerdown of 4+ hours??? Did dd-wrt flush its cache of MAC addresses? IDK. But w/o a global net, I was trapped, I could not DL the tools needed to troubleshoot. A very frustrating state of affairs. I do not see anyplace where I could mark this as solved.

Now I have restarted the install with a 64G u-card, and it is totally different. it only took 1 pass at networkmanager to make all the local network work in that I can ssh gene@any-local-machine and bavk again. But now I cannot get thru the router for its dnsmasq server. All addresses in the network setup are checked and correct. The hostname has been reset to its normal, e5p, has been used for 3 or 4 years but the Network is unreachable because the router isn't functioning as a dns lookup. Its even been rebooted a couple times. New faster router about 4 months back with dd-wrt in it. ip a: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 2a:b6:6c:1a:3a:1f brd ff:ff:ff:ff:ff:ff inet 192.168.71.122/24 brd 192.168.71.255 scope global noprefixroute end0 valid_lft forever preferred_lft forever inet6 fe80::28b6:6cff:fe1a:3a1f/64 scope link valid_lft forever preferred_lft forever ip r: 192.168.71.0/24 dev end0 proto kernel scope link src 192.168.71.122 metric 100 192.168.71.0/24 via 192.168.71.1 dev end0 proto static metric 200 /etc/netplan/armbian.yaml: root@e5p:/etc/netplan# cat armbian.yaml network: version: 2 renderer: NetworkManager ethernets: end0: addresses: - "192.168.71.122/24" nameservers: addresses: - 192.168.71.1 dhcp4: false dhcp6: false macaddress: "2a:b6:6c:1a:3a:1f" routes: - metric: 200 to: "192.168.71.1/24" via: "192.168.71.1" Can anyone see what is wrong with that? Thanks.

To clarify that last line htop say's ssh_config is in the cmd listing. put a tail on /var/log/syslog since it has the newest "access time" of any file in e5p's /var/log Further: "ssh gene@coyote" successfully logged into coyote, so assuming that ssh is running set e5p's /etc/apparmor verbose on with nano. from that login "ssh gene@e5p" gets "connection reset by peer", and NO update to syslog. The rejection is not even making it to ANY of the logs. So what's next? Switch back to a 64G u-sd? Is a 128G u-sd too big? I am out of ideas. And a $3000 3d printer is Dead In The Water, no way to restore its klipper /home/gene/printer_data directory after a forced upgrade from jammy to noble. Thanks.

You might not have been looking at the newest dmesg, I had a hard time convincing NetworkManager to stop calling for dhcp and just use the static settings I gave it. Everytime I looked it was re-enabled. Once I had convinced it to skip the dhcp BS, network is fine, apt works, ping -c1 yahoo.com works and FF can browse the whole planet. Everything works except /incoming ssh/. I can goto that printer and log into this machine, but I can't ssh into that machine. I can't "ssh-copy-id gene@e5p" which aliases in the hosts file to 192.168.71.122, it's refusing the incoming connection that worked with 6 other machines. Is there some other tool to trace this? htop says it is ATM. Thank you.