Search the Community

Hi everybody, I would like to use the Nanopi NEO2 as firewall and therefore would like to support testing ethernet. I setup an iperf server on Nanopi NEO2 and I am running the client on my iMac to test stability of ethernet connections. After around 30-40 seconds the ethernet links goes down and is coming up back again. IPERF LOG imac:~ mobs$ iperf3 -p 5001 -c 192.168.1.100 -t 0 Connecting to host 192.168.1.100, port 5001 [ 5] local 192.168.1.109 port 53298 connected to 192.168.1.100 port 5001 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 111 MBytes 932 Mbits/sec [ 5] 1.00-2.00 sec 112 MBytes 939 Mbits/sec [ 5] 2.00-3.00 sec 112 MBytes 941 Mbits/sec [ 5] 3.00-4.00 sec 112 MBytes 940 Mbits/sec [ 5] 4.00-5.00 sec 112 MBytes 940 Mbits/sec [ 5] 5.00-6.00 sec 112 MBytes 940 Mbits/sec [ 5] 6.00-7.00 sec 112 MBytes 940 Mbits/sec [ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec [ 5] 8.00-9.00 sec 112 MBytes 940 Mbits/sec [ 5] 9.00-10.00 sec 112 MBytes 940 Mbits/sec [ 5] 10.00-11.00 sec 112 MBytes 940 Mbits/sec [ 5] 11.00-12.00 sec 112 MBytes 939 Mbits/sec [ 5] 12.00-13.00 sec 112 MBytes 941 Mbits/sec [ 5] 13.00-14.00 sec 112 MBytes 940 Mbits/sec [ 5] 14.00-15.00 sec 112 MBytes 939 Mbits/sec [ 5] 15.00-16.00 sec 112 MBytes 941 Mbits/sec [ 5] 16.00-17.00 sec 111 MBytes 929 Mbits/sec [ 5] 17.00-18.00 sec 112 MBytes 940 Mbits/sec [ 5] 18.00-19.00 sec 112 MBytes 940 Mbits/sec [ 5] 19.00-20.00 sec 112 MBytes 940 Mbits/sec [ 5] 20.00-21.00 sec 112 MBytes 940 Mbits/sec [ 5] 21.00-22.00 sec 112 MBytes 939 Mbits/sec [ 5] 22.00-23.00 sec 112 MBytes 941 Mbits/sec [ 5] 23.00-24.00 sec 112 MBytes 940 Mbits/sec [ 5] 24.00-25.00 sec 112 MBytes 939 Mbits/sec [ 5] 25.00-26.00 sec 112 MBytes 941 Mbits/sec [ 5] 26.00-27.00 sec 112 MBytes 940 Mbits/sec [ 5] 27.00-28.00 sec 112 MBytes 940 Mbits/sec [ 5] 28.00-29.00 sec 112 MBytes 940 Mbits/sec [ 5] 29.00-30.00 sec 112 MBytes 940 Mbits/sec [ 5] 30.00-31.00 sec 112 MBytes 940 Mbits/sec [ 5] 31.00-32.00 sec 112 MBytes 940 Mbits/sec [ 5] 32.00-33.00 sec 112 MBytes 940 Mbits/sec [ 5] 33.00-34.00 sec 112 MBytes 940 Mbits/sec [ 5] 34.00-35.00 sec 94.8 MBytes 794 Mbits/sec [ 5] 35.00-36.00 sec 0.00 Bytes 0.00 bits/sec [ 5] 36.00-37.00 sec 0.00 Bytes 0.00 bits/sec [ 5] 37.00-38.00 sec 0.00 Bytes 0.00 bits/sec [ 5] 38.00-39.00 sec 2.88 MBytes 24.2 Mbits/sec [ 5] 39.00-40.00 sec 112 MBytes 942 Mbits/sec [ 5] 40.00-41.00 sec 112 MBytes 940 Mbits/sec [ 5] 41.00-42.00 sec 112 MBytes 940 Mbits/sec [ 5] 42.00-43.00 sec 112 MBytes 941 Mbits/sec ^C[ 5] 43.00-43.46 sec 52.0 MBytes 940 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-43.46 sec 4.30 GBytes 850 Mbits/sec sender [ 5] 0.00-43.46 sec 0.00 Bytes 0.00 bits/sec receiver iperf3: interrupt - the client has terminated AND on the syslog I can see the following Nov 12 17:33:14 localhost NetworkManager[623]: <info> [1510504394.8756] device (eth0): link disconnected Nov 12 17:33:14 localhost NetworkManager[623]: <info> [1510504394.8759] device (eth0.10): link disconnected I would like to stabilize the Nanopi NEO2 build. How can I help? Need I address this issue to another mailing list? Kind regards, obermeim

I'm testing the nightly image: Armbian_5.32.170704_Nanopineo2_Ubuntu_xenial_dev_4.11.8.img I've soldered 2x female A USB ports to the NanoPi Neo2 as per the pinout http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO2#Diagram.2C_Layout_and_Dimension When I plugged in wifi dongles or USB flash drives, their light comes on, but I get nothing on lsusb and dmesg. Then I realized I had D+ and D- reversed, so I swapped them for each port, but there's still absolutely nothing when connecting devices to these ports. (I know that having D+ and D- swapped doesn't cause any damage) Do I need to somehow enable the USB ports in a fex file or in the kernel etc?

I'm testing the nightly image: Armbian_5.32.170704_Nanopineo2_Ubuntu_xenial_dev_4.11.8.img I've got it running nice and stable as a router and wifi AP, with 2 USB ports, one wifi adapter on each port. But when it's been off for a while and I power it on, it doesn't boot on the first powerup, only if I disconnect power and then wait a few seconds then power again. I've tried 2 different 2A 5v power supplies, one that I've successfully powered RbPi 2s and other Linux SBC's for months at a time, no problems. The voltage is good. I also tried a beast 10 port USB charger that has 6x 2A ports. Same behavior for all power supplies I've tried, and I've never experienced this problem with any other Linux SBC. Is anyone else experiencing this? I'm wondering if maybe it's a bug maybe with the watchdog or some special hardware registers, I'm theorizing that if it's not run recently it reads some value that causes an infinite loop of some kind. It happened with the image before I changed anything at all. I suppose I could also try different microSD cards.

TL;DR: The small H2+/H3 boards unlike their bigger siblings are all prone to overheating due to smaller PCB size (on the larger boards the PCB's groundplane acts somewhat as a large heatsink dissipating heat away from the SoC). Due to mainline kernel settings not being optimized currently all these boards are slower under constant load compared to legacy kernel. This should change but won't unless someone is looking into it and spends some time on this. Two areas that deal with this overheating tendency or are somewhat related are thermal protection / throttling: use the thermal sensor(s) inside the SoC to downclock various engines if specific tresholds are exceeded DVFS (dynamic voltage frequency scaling). All the small boards have either no voltage regulation (NanoPi NEO2) or a primitive one only switching between 1.1V and 1.3V With sun8i legacy kernel Armbian and linux-sunxi community members spent a lot of time and efforts on improving thermal/throttling performance. Read through the following as a reference please: https://github.com/armbian/build/issues/298 The result of our optimizations was a lot of better performance compared to Allwinner's defaults (that targeted only Android and preferred higher single thread performance over overall better performance, with Allwinner settings on an overheating system you could end up with just one or two active CPU cores pretty easily). Now with mainline kernel situation for the larger H3 boards is ok-ish (those boards have an I2C adjustable voltage regulator, voltage switching works fine grained, overheating isn't much of an issue anyway and performance is almost as good as with legacy kernel). But situation with the smaller boards needs some attention. If we run the cheapest boards currently with mainline kernel then we're talking about these settings: max cpufreq 1008 MHz (at 1.3V), next lower cpufreq 816 MHz at 1.1V, then 624/480/312/240/120 MHz defined 4 thermal trip points defined starting at 65"C with throttling, then using 75° and 90°C and shutting board down when 105°C are reached. With Armbian and using legacy kernel it's the following instead: max cpufreq is 1200 MHz, then 1008 MHz still at 1.3V, at 912 MHz we switch to 1.1V and below are a few other cpufreqs available between 816 MHz and 1344 MHz Armbian's legacy kernel provides cpufreq steps every 48 MHz (allowing for fine grained throttling) On the small boards we use twice as much thermal trip points as mainline settings and our strategy is to switch to 912MHz@1.1V pretty early once throttling occurs These differences result in both lower 'normal' performance (since mainline kernel limits also single threaded tasks to 1GHz instead of 1.2GHz) and also 'full load' performance since DVFS/THS/throttling settings are not optimal and once the board reaches the first thermal trip point throttling is not that efficient compared to legacy. It's easy to test: grab an OPi Zero, NanoPi Duo or any of the other H2+/H3 boards with primitive voltage regulation, then grab an Armbian OS image with legacy kernel (3.4.113 using fex settings) and one with mainline kernel. Execute on both sudo rpimonitor -r (installs RPi-Monitor so you can enjoy nice graphs when connecting with a web browser to port 8888 of your machine) sudo rpimonitor -p (installs cpuminer which is a great tool to heatup your board and also to measure 'thermal performance' since spitting out khash/s values in benchmark mode minerd --benchmark (this is the actual benchmark running) With mainline kernel performance is lower. Expected result: same performance. What to do? Improve mainline settings. BTW: Mainline settings currently are as they are since these were the values megi started with last year. Once numbers exist they're only dealt with copy&paste any more.

- Allwinner H5 - Gigabit Ethernet - 512MB (test subject) - made few tests with our testing H5 (4.10) kernel - nightly builds

I used the Armbian test image. I did apt-get upgrade I changed eth0 to static IP. But now, I started it up and eth0 green light won't stay on. Can't ping it or SSH. I connected a USB PL-2303HX from my PC to the NanoPi Neo2 (first time for me ever connecting to a Linux computer's serial console) With no configuration at all I got this output in minicom. U-Boot SPL 2017.09-armbian (Sep 17 2017 - 03:48:48) DRAM: 4096 MiB Trying to boot from MMC1 NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):aa75c8d NOTICE: BL3-1: Built : 02:45:22, Sep 17 2017 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 Looks like U-Boot can't find the kernel or whatever? Okay I removed the 5v wire from the USB serial adapter so I can rather power the board via microUSB 2A adapter than weak USB port power. I unplugged and replugged the 2A microUSB but it didn't help. With the microUSB unplugged the PCB's green LED still glowed faintly somehow powered from GND and tx/rx. rneese suggested I unplug and replug everything. I did and now it booted up and I can see it on the console. It's saying no ethernet found and it looks like a console so I'll give it a go. U-Boot 2017.09-armbian (Sep 17 2017 - 03:48:48 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: FriendlyARM NanoPi NEO 2 DRAM: 512 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 38518 bytes read in 134 ms (280.3 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3362 bytes read in 179 ms (17.6 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 116 bytes read in 149 ms (0 Bytes/s) ** File not found /boot/dtb/allwinner/allwinner/sun50i-h5-nanopi-neo2.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 4179 bytes read in 362 ms (10.7 KiB/s) Applying kernel provided DT fixup script (sun50i-h5-fixup.scr) ## Executing script at 44000000 5001834 bytes read in 452 ms (10.6 MiB/s) 12285960 bytes read in 868 ms (13.5 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 5001770 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... starting USB... No controllers found USB is stopped. Please issue 'usb start' first. starting USB... No controllers found No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found starting USB... No controllers found No ethernet found. No ethernet found. => => ls ls - list files in a directory (default /) Usage: ls <interface> [<dev[:part]> [directory]] - List files in directory 'directory' of partition 'part' on device type 'interface' instance 'dev'. => su Unknown command 'su' - try 'help' => help ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootefi - Boots an EFI payload from memory bootelf - Boot from an ELF image in memory booti - boot arm64 Linux Image image from memory bootm - boot application image from memory bootp - boot image via network using BOOTP/TFTP protocol bootvx - Boot vxWorks from an ELF image cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation dhcp - boot image via network using DHCP/TFTP protocol dm - Driver model low level access echo - echo args to console editenv - edit environment variable env - environment handling commands exit - exit script ext2load- load binary file from a Ext2 filesystem ext2ls - list files in a directory (default /) ext4load- load binary file from a Ext4 filesystem ext4ls - list files in a directory (default /) ext4size- determine a file's size false - do nothing, unsuccessfully fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) fatsize - determine a file's size fatwrite- write file into a dos filesystem fdt - flattened device tree utility commands fstype - Look up a filesystem type go - start application at address 'addr' gpio - query and control gpio pins help - print command description/usage iminfo - print header information for application image imxtract- extract a part of a multi-image itest - return true/false on integer compare lcdputs - print string on video framebuffer load - load binary file from a filesystem loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loadx - load binary file over serial line (xmodem mode) loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range ls - list files in a directory (default /) md - memory display mdio - MDIO utility commands mii - MII utility commands mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - display MMC info mw - memory write (fill) nfs - boot image via network using NFS protocol nm - memory modify (constant address) part - disk partition related commands ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables pxe - commands to get and boot from pxe files reset - Perform RESET of the CPU run - run commands in an environment variable save - save file to a filesystem saveenv - save environment variables to persistent storage setcurs - set cursor position within screen setenv - set environment variables setexpr - set environment variable as the result of eval expression showvar - print local hushshell variables size - determine a file's size sleep - delay execution for some time source - run script from memory sysboot - command to get and boot from syslinux files test - minimal test like /bin/sh tftpboot- boot image via network using TFTP protocol true - do nothing, successfully usb - USB sub-system usbboot - boot from USB device version - print monitor, compiler and linker version

I'm testing the nightly image: Armbian_5.32.170704_Nanopineo2_Ubuntu_xenial_dev_4.11.8.img I read somewhere that the NanoPi Neo2 has a shutdown issue where it reboots. This was my experience (serial console) `shutdown -h now` ends with [ OK ] Reached target Shutdown. [ 59.809788] reboot: Power down INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON Maybe there is a watchdog timer (that resets the CPU if some ticker stops or something) that needs to be disabled? I see there is no watchdog package installed in this image. As a workaround while connected via serial console, I hit enter when U-Boot got to this line "Hit any key to stop autoboot: 0", which only paused for a very brief moment.

FYI & FWIW: Howto find your NanoPi NEO2 Your NanoPi NEO2 is connected to your LAN, but how to find it? What is the IP address? Here are my methods: Via bonjour (Ubuntu to Ubuntu): ssh nanopineo2.local. Example: $ ssh nanopineo2.local. sander@nanopineo2.local.'s password: _ _ ____ _ _ _ ____ | \ | | __ _ _ __ ___ | _ \(_) | \ | | ___ ___ |___ \ | \| |/ _` | '_ \ / _ \| |_) | | | \| |/ _ \/ _ \ __) | | |\ | (_| | | | | (_) | __/| | | |\ | __/ (_) | / __/ |_| \_|\__,_|_| |_|\___/|_| |_| |_| \_|\___|\___/ |_____| Welcome to ARMBIAN 5.32.170704 nightly Ubuntu 16.04.3 LTS 4.11.8-sun50iw2 Scan all devices (IP + MAC): $ sudo arp-scan --localnet Interface: wlp2s0, datalink type: EN10MB (Ethernet) Starting arp-scan 1.9.5 with 256 hosts (https://github.com/royhills/arp-scan) 192.168.0.1 64:d1:a3:03:8a:01 Sitecom Europe BV 192.168.0.106 02:01:9c:45:40:2d (Unknown: locally administered) 192.168.0.110 00:13:77:fa:63:e3 Samsung Electronics Co.,Ltd 192.168.0.102 ec:1f:72:59:48:b2 SAMSUNG ELECTRO-MECHANICS(THAILAND) 4 packets received by filter, 0 packets dropped by kernel Ending arp-scan 1.9.5: 256 hosts scanned in 2.527 seconds (101.31 hosts/sec). 4 responded Compare with when the NanoPi is off / unconnected, and you know your device. In my case it's 192.168.0.106 Hope this helps.

Hi, When I put a heavy load on my NanoPi NEO2, it locks up. The ethernet light keeps flashing, so there is still something alive? After a power reset, the NEO2 works again. I've already put a CPU fan on my CPU. CPU temp is at 25 degrees Celsius in rest, and goes up to 37 degrees Celsius under the heavy load. The heavy load is a "make -j4" of a C source code project Tips how to solve this? sander@nanopineo2:~$ while true; do date ; uptime ; cat /etc/armbianmonitor/datasources/soctemp; sleep 2; done | tee mijn-log.txt Tue Aug 22 11:46:37 UTC 2017 11:46:37 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28342 Tue Aug 22 11:46:39 UTC 2017 11:46:39 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28584 Tue Aug 22 11:46:41 UTC 2017 11:46:41 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28463 Tue Aug 22 11:46:43 UTC 2017 11:46:43 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28705 Tue Aug 22 11:46:45 UTC 2017 11:46:45 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28827 Tue Aug 22 11:46:47 UTC 2017 11:46:47 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28463 Tue Aug 22 11:46:49 UTC 2017 11:46:49 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 30281 Tue Aug 22 11:46:51 UTC 2017 11:46:51 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28584 Tue Aug 22 11:46:53 UTC 2017 11:46:53 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 30402 Tue Aug 22 11:46:55 UTC 2017 11:46:55 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28827 Tue Aug 22 11:46:57 UTC 2017 11:46:57 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28705 Tue Aug 22 11:46:59 UTC 2017 11:46:59 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28705 Tue Aug 22 11:47:01 UTC 2017 11:47:01 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28463 Tue Aug 22 11:47:03 UTC 2017 11:47:03 up 5:24, 2 users, load average: 0.00, 0.00, 0.00 28342 Tue Aug 22 11:47:05 UTC 2017 11:47:05 up 5:25, 2 users, load average: 0.00, 0.00, 0.00 29917 Tue Aug 22 11:47:07 UTC 2017 11:47:07 up 5:25, 2 users, load average: 0.08, 0.02, 0.01 29069 Tue Aug 22 11:47:09 UTC 2017 11:47:09 up 5:25, 2 users, load average: 0.08, 0.02, 0.01 33431 Tue Aug 22 11:47:11 UTC 2017 11:47:11 up 5:25, 2 users, load average: 0.47, 0.10, 0.03 36945 Tue Aug 22 11:47:13 UTC 2017 11:47:14 up 5:25, 2 users, load average: 0.47, 0.10, 0.03 37187 Tue Aug 22 11:47:25 UTC 2017 ... and then nothing more

NanoPi NEO2 Debian jessie 4.11.1-sun50iw2 mount.cifs doesn't load if iocharset=utf8

Hello, I've been running the Ubuntu experimental version in my NanoPi NEO2 for months now without any issues, it has been running just fine. However today I tried to run apt-get update and got: N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'utils/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' N: Skipping acquire of configured file 'xenial-desktop/binary-arm64/Packages' as repository 'http://beta.armbian.com xenial InRelease' doesn't support architecture 'arm64' This wasn't showing up before, does this actually means I don't get updates anymore? Why? What's changed / how should I fix this? Board: NanoPi NEO2 Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial Thank you.

Hello, first of all many thanks to all the community that keeps this project alive. I recently bought a NanoPi NEO2 board and of course decided to drop the OS provided by Friendlyarm and give a try to Armbian's Ubuntu build for this board. Everything seems to work just fine, however I'm unable to get a reading on the CPU Frequency. I tried multiple tools and commands but somehow all end up with something like "cpuinfo_cur_freq: No such file or directory. For instance, here is the output of armbianmonitor: armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU/usr/bin/armbianmonitor: line 264: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: No such file or directory Any tips on how to fix this / get the reading? Thank you!

first off: I'm totally new in the Linux world, but it's really fun to play with *Pis! currently I'm on a OPILite but I have some RasPis lying around and just ordered a nanoPieNEO2. I'm trying to setup a filesystem that supports deduplication, as far as I can tell that's ZFS or BTRFS. After a lot of reading and learning I got BTRFS with bedup running, but bedup is only file-wise deduplication. The solution for block-wise would be duperemove, but I can't find/get/install/build it for armhf. Has somebody tried block-wise deduplication before and can point me in the right direction? I'm running armbian 5.31 on 4.11.5

I'm running what I believe is the latest experimental for the neo2 - 5.27.170601. This could well be a problem related to something that doesn't yet work in this build. I've built strongswan on the neo and everything built fine and installed. ipsec starts and I'm able to bring a tunnel up to a remote vpn server that I know is fine and is verified working from some other box with identical connection and key configuration that I'm using on the neo2. When the tunnel is brought up on the neo2 it seems I'm not able to get any traffic to flow i.e. curl api.ipify.org should return the public ip of the remote vpn server but it just hangs. When the tunnel is down the same curl command works fine. This feels routing / firewall / NAT related but to be honest I don't know where to start digging now. Does anyone have any suggestions? Anyone managed to get something similar working yet? Cheers Joe