Curiosity in these privacy times made me wonder how Pogoplug-Pro-V1 (with latest kernel 5.4.179) could be made to change MAC-address to a random hardware address under Debian. Curiosity made me see that this already seems to be built into the rootfs, or am I mistaken? This has been observed by chance: arp-scan -l 192.168.0.4 00:11:22:33:44:55 Cloud Engines, Inc. a minute later... arpby chaos - Debian
Quotebodhi I could create a tutorial post for this rsync backup job if requested. There are many tutorials on the Web about this subject so I did not tthink it is needed here. For my part (I take the liberty to assume that others might benefit from such a guide as well), I personally would greatly appreciate a guide (a script.sh file maybe to avoid errors by typing it in manually) that automatby chaos - Debian
Thank you for your feedback. I am editing the top post with your comments as they come in. After testing a bit with min server protocol = SMB2 I discovered in other post about older versions of Kodi (prior to v.18) which cannot connect to a server using SMB v2/v3. So if you happen to have an old box running Kodi v1-17 that you cannot upgrade to v18 for some technical reason (hardware limitaby chaos - Debian
Samba server project on Pogo v4 using SATA harddisk instead of USB for rootfs I write this post a little bit as a help for other newbies who may find same or similar issues to make a SATA HDD boot linux as I did at first. It was not so easy to figure out how to set up a rootfs on a SATA harddisk, instead of on a regular USB-stick. There was no post for the Pogo v4 about this. Some otheby chaos - Debian
I'll try to answer all questions from the above posts here. First... Every new Ubuntu release is quite buggy at first. Ubuntu 20.04 has so far not shown any bugs to me, except for this openssh authentication issue with original rootfs 5.2.9 and an upgraded rootfs 4.12.1. I did suspect that the Ubuntu 20.04 could be the culprit, but the linux forums on internet all pointed to the history oby chaos - Debian
I now tested the rootfs 5.2.9 with the keys removed and edited rc.local to generate new keys. Now it works using rootfs 5.2.9 from scratch, like rootfs 4.12.1. Seems the issue with rootfs 5.2.9 was that the authentication keys were wrong somehow. I can also notice that openssh may have been upgraded since then, from 1:7.9p1-10 to 1:7.9p1-10+deb10u2 Still, it could be useful to cby chaos - Debian
Please note, that since I have reinstalled openssh-server and upgraded everything to latest Debian 10 Buster, I can't output the old values before I succeeded to upgrade it. Here comes the values that the current update Debian 10 system outputs. I have also been very disobedient when it comes to not obeying your rule to use just one ext3 partition on the usb-stick. I tried formating the pby chaos - Debian
I have a uEnv.txt with one line only: custom_params=init=/bin/systemd How do I modify it so that there are two commands: custom_params=initramfs.runsize=23M init=/bin/systemd Tried all kinds of ways, but don't manage to increase the size of tmpfs this way. Also tried the solution by @rayknight here. Edit the /usr/share/initramfs-tools/init file and modify line with 'mouby chaos - Debian
Well, what can I say... I also assumed that it would just be ok to run rootfs 5.2.9 and at least be able to ssh into the POGO v4. But ... it doesn't ... probably because openssh-server has done some major changes which require the keys to be done again from scratch. There are several threads about this error (some of them dating 7 years back so it's not first time this happens) on the iby chaos - Debian
After hours of investigation this issue, it seems absolutely clear that there has been significant changes/updates to openssh-server, ssh-keygen and openssh-client that basically require a complete uninstall of those packages "apt-get --purge remove openssh-server openssh-client", "apt autoremove" and "apt clean" the system. Then one need to reinstall openssh-serverby chaos - Debian
I tried all of the above. I also made very sure I was root (learned that the hard way a while ago). I did, once again, try to update the working 4.12.1 rootfs from scratch to latest version on Debian Stretch. Now, the ssh login problem begins once Debian is updated with apt-get update && apt-get upgrade even on Debian Stretch. I don't even have to upgrade to Debian 10 toby chaos - Debian
I have searched the forum if someone else has had difficulty to access Pogoplug v4 (POGO-V4-A3-01) via ssh as root. I keep getting connection refused from Debian and I have run out of ideas on how to enable ssh root access. Hence this post. user@desktop:~$ ssh root@<POGO-V4-A3-01 ip address> ssh: connect to host <POGO-V4-A3-01 ip address> port 22: Connection refused I am using tby chaos - Debian
This is how installation of kernel 5.2.9 was done. Also installed systemd and locales. user@desktop:~$ scp linux-5.2.9-kirkwood-tld-1-bodhi.tar.bz2* root@<POGO-V4-A3-01 ip address>:/boot linux-5.2.9-kirkwood-tld-1-bodhi.tar.bz2 100% 34MB 5.0MB/s 00:06 linux-5.2.9-kirkwood-tld-1-bodhi.tar.bz2.md5 100% 75 52.7KB/s 00:00 linux-5.2.9-kirkwood-tld-1-bodhi.tar.by chaos - uBoot
I now see what I did wrong: I used the two USB3.0 ports on the back and didn't know and didn't suspect that there was something hidden under the top plastic, which by the way is not just design, but actually hides something crucial... the one and only USB2.0 port that is to be used for booting. This is exactly what I meant that a newbie may not anticipate something so trivial to expertsby chaos - uBoot
Whatever USB I put, whatever format on the file system I use (ext3/ext2/ext4), whatever the partition table type (msdos/GPT/MAC/BSD), I even tried to do all this on another older PogoPlugPro, the result is always the same: Pogov4> usb start usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0by chaos - uBoot
Test: interrupt autobooting + printenv U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 9 0 Pogov4> printenv printenv arcNumber=3960 bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe)by chaos - uBoot
I've been trying for some days to set up POGO-V4-A3-01 + 2017.07 U-Boot Kirkwood + Debian 4.12.1 rootfs + Kernel 5.2.9 without success. The steps I followed: Executing automatic shell script which installs uboot.2014.07-tld-1.pogo_v4.bodhi and uboot.2014.07-tld-1.environment.img. Extracting the corresponding rootfs to a 1GB Sandisk SD-card formated as ext3 with 128MB linux-swap partitiby chaos - uBoot