[FIRMWARE] Itus Shield v2
Locked
1234567
1234567
 
|
Personally I didn’t chop and change at all, so not important.
From: Grommish [via Itus Networks Owners Forum] <ml+[hidden email]>
Sent: Wednesday, July 22, 2020 2:20:43 PM To: Turrican <[hidden email]> Subject: Re: Need Your Input... You could do anything you wanted, yes. Nothing on the switch enables or disables anything hardware wise..
The question is, how important was the multi-mode ability when you purchased the Shield? Just to be clear, I'm not talking about abandoning the project, just not getting it included in the openwrt mainline
Running Itus Shield v2 Firmware
If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Shield-v2-tp2014p2117.html
To start a new topic under Technical Discussion, email ml+[hidden email]
To unsubscribe from [FIRMWARE] Itus Shield v2, click here. NAML
Running v2 Firmware
|
Administrator
|
If it's a lot of work then I would lean towards not worth it. Additionally, being able to switch to another partition is a pretty handy fail-safe if something goes wrong.
Running the latest OpenWrt stable release
|
|
I'd suggest get router mode included, later apply mods to make (or build out) a bridge variant via Github Actions. Having packages available from the official Openwrt repo would benefit both. On Wed, 22 Jul 2020, 10:46 pm user8446 [via Itus Networks Owners Forum], <[hidden email]> wrote: If it's a lot of work then I would lean towards not worth it. Additionally, being able to switch to another partition is a pretty handy fail-safe if something goes wrong.
OpenWrt SNAPSHOT, r10391-3d8d528939
|
|
|
In reply to this post by Grommish
I'm not quite following why it would kill the mode switch.. Aren't we talking just getting them to build 1 the initram image 2 upgrade image 3 packages? So, even if they will only build for one mode, can't we still supplement? If that's not a goer, I reckon just try Github Actions to automate it unofficially.. On Wed, 22 Jul 2020, 9:06 pm Grommish [via Itus Networks Owners Forum], <[hidden email]> wrote: Well.. in talking with some of the OpenWrt dev team, they want to concat three images into one in order to be considered for inclusion into the mainline.
OpenWrt SNAPSHOT, r10391-3d8d528939
|
|
In reply to this post by Grommish
Well i've added the recovery image in gateway all ok formatted to f2fs all ok installed bridge and router to 4.19. all ok on the bridge switch I ran the system upgrade file, now boots into version 5.4 then freezes, so I want to reload the kernel bin file, but am unsure which one to use now I have f2fs Also when I upgrade the router mode 4.19 to the latest 5.4 which file do I use as i'm getting confused with the different emails I have. On Tue, 21 Jul 2020 at 00:26, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: Nope, was not aware, but I am now :) |
|
Administrator
|
In reply to this post by Gnomad
The way the Shield is setup, it should be treated as there separate devices in one shell, because of the way you have to pass kernel cmdline arguments to mount the storage. Their contention is, the shield is a single device and only needs a single image. They point to other "dual boot" routers, which are dual boot, but not in the same way the Shield is.. They have a single NAND flash kernel and are able to select which gets booted storage wise. By the time the shield boots, it's to late.
The initramfs image would work in any slot, because it's not reliant on the eMMC device for storage.. The sysupgrade images contain the target'ed kernel (I pass on root=/dev/mmcblk1pX rootfs=squashfs,f2fs,ext4 rootwait to the kernel at compile, one for each mode so I can change the mmcblk1p2,3,4 etc). So, a single image would technically work in any slot depending on what you named the file (ItusrouterImage, ItusgatewayImage, ItusbridgeImage), but it would ONLY USE /dev/mmcblk1p2 for storage, because that's what hardcoded into the kernel cmdline. That's fine, but you no longer have any use of the front-panel switch. You also lose out on the 1.7Gb of storage left from /dev/mmcblk1p3 and /dev/mmcblk1p4. You could re-partition it, but there is no way I'm automating it or hand-holding here for it. Bad things can happen when you monkey with partition tables.. What I've done is put in a PR for the single device image that only uses the Router slot. This will get the device mainlined at least, and for those who don't care, it'll give them an legit official device. This way, at least something is offered. For the rest, like me, who don't like this solution, I'll also continue with my own repo that'll support the other modes. I think that really would be the best way to ensure everyone gets at least some support.
Running Itus Shield v2 Firmware
|
|
Administrator
|
In reply to this post by Roadrunnere42
The use the Initramfs first. Boot to it, do the mkf2.f2fs /dev/mmcblk1p4, then flash the sysupgrade
Running Itus Shield v2 Firmware
|
|
|
In reply to this post by Grommish
I see. Sounds reasonable! Hopefully the GitHub images should be able to pull from official package sources then too, save you building those out at least. (unless we get similar kernel mismatch errors as recently seen with 5.4? ..) On Thu, 23 Jul 2020 at 09:31, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: The way the Shield is setup, it should be treated as there separate devices in one shell, because of the way you have to pass kernel cmdline arguments to mount the storage. Their contention is, the shield is a single device and only needs a single image. They point to other "dual boot" routers, which are dual boot, but not in the same way the Shield is.. They have a single NAND flash kernel and are able to select which gets booted storage wise. By the time the shield boots, it's to late.
OpenWrt SNAPSHOT, r10391-3d8d528939
|
|
Administrator
|
Honestly, i think that kernel mismatch is an error with banip or a library it relies on.. I'm not sure why anyone would need anything other than Major/Minor/Mini kernel revision level.. That is pulling to the COMMIT that was at the HEAD when it was compiled.. It's nuts..
I've been playing with that Github Activites..and I got it to work, but I'm not real happy with what it actually does. https://github.com/Grommish/Itus_Shield_v2/actions/runs/179383951 It creates files to download and extract. It also bundles all of the bin/ directory you can download.. But, it seems its designed for an enduser rather than as a development tool. For example, there is no way to use the output for opkg purposes.. I'll have to look at what the code is (I just changed enough to get it working) and see if I can do anythng else with it :)
Running Itus Shield v2 Firmware
|
|
|
Will keep fingers crossed re: the mismatches then! You'll probably need to modify your workflow from the default provided by that repo - and can definitely add files back to the repo, manipulate Releases, etc. e.g. take a look at https://github.com/marketplace/actions/add-commit - perhaps run that afterwards to commit the built files as needed. On Thu, 23 Jul 2020 at 14:57, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: Honestly, i think that kernel mismatch is an error with banip or a library it relies on.. I'm not sure why anyone would need anything other than Major/Minor/Mini kernel revision level.. That is pulling to the COMMIT that was at the HEAD when it was compiled.. It's nuts..
OpenWrt SNAPSHOT, r10391-3d8d528939
|
|
|
In reply to this post by Grommish
The system is not remembering any settings each time I reboot says the password is not set and ssh is unspecified, although I have changed saved and applied. Heres what I've done Booted into router mode ( it's running ver 4.19) ssh [hidden email] "mount /dev/mmcblk1p4 /overlay" scp openwrt-octeon-itusbridge-initramfs-kernel.bin root@10.10.10.10:/overlay/ItusbridgeImage ssh [hidden email] "umount /overlay" rebooted version 5.4.51, set password and ssh mkfs.f2fs /dev/mmcblk1p4 Flashed Firmware (all seems to go ok the auto reboot) with openwrt-octeon-itusbridge-squashfs-sysupgrade.tar Now at version 5.4.51 but nothing is saved, done several times just in case i've messed up but no saving. On Thu, 23 Jul 2020 at 02:33, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: The use the Initramfs first. Boot to it, do the mkf2.f2fs /dev/mmcblk1p4, then flash the sysupgrade |
|
Administrator
|
You are close, but the order is out of sequence.
Install the initramfs.kernel.bin to your ItusbridgeImage Reboot Flash the sysupgrade.tar, reboot Then set your password and IP. When the system is booted to the intiramfs image, nothing is saved over reboots, and the sysupgrade system can't backup anything while it's running from the ramdisk. It'll be persistent then, however, you may want to wait for a day or so before you start customizing, as I've just recently got the sysupgrade system working (and they fixed the bug with luCi insisting we have MTD block devices and giving the error), so I'll put a new version out here when it's done building
Running Itus Shield v2 Firmware
|
|
|
Right followed your orders, but still no saved password or ssh access or new ip address The files i'm using came from Installed the initramfs.kernel.bin to ItusbridgeImage Rebooted Flashed the sysupgrade.tar via luci, checksum passed ok Rebooted Used ip 192.168.1.1, set password and ssh, rebooted Screen says no password set and i can access by leaving blank. On Fri, 24 Jul 2020 at 21:55, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: You are close, but the order is out of sequence. |
|
Administrator
|
I've created an Github Org to hold the repos, so that it can be more centrally maintained.
https://github.com/Itus-Shield Grab the gateway files from https://github.com/Itus-Shield/opkgs/tree/kernel-5.4/targets/octeon/generic and try them. Ironically, I had delayed announcing and releasing originally because I was still trying to get things worked out. Once I did, things have moved very, very quickly. I'll need to go update the other thread, but for now, everything will be going thru that repo. The distfeeds.conf is already configured for it and it'll continue to be pointed there, so updates will be easier. This is the 5.4 kernel, musl 1.2.0, gcc 10.x build, and has the working sysupgrade system (it'll save settings over upgrades) Anyone else who wants to upgrade can, just grade the correct slot. FYI, I have submitted, corrected, and am waiting to see if i can get the device mainlined into OpenWrt. if I do, ONLY the router images are created, but my repo will continue to generate all three.
Running Itus Shield v2 Firmware
|
|
Administrator
|
Not really an update, but a surprise..
I am looking at u-boot because I'm bored.. and I found this:
|
|
Administrator
|
Ha, would probably make the shield a nice frying pan...
On another note have you seen anything on your work about the hardware acceleration that out CN7020 chip has but was never used in our build from Itus?
Running the latest OpenWrt stable release
|
|
Administrator
|
Yes. Actually, you can enable it in the Firewall settings under Hardware and Software Offloading. This gives me about 150MiBps of additional throughput on a speedtest. Of course, this is before snort or anything gets to touch it :) Also, now enabled (at least in the 5.4 version) are the crypto() octeon-optimized code. OCTEON has specific crypto() acceleration for MD5, SHA1, SHA256 and SHA512 (I believe 512 is on the list, I'd have to check) that is enabled in the kernel. There are other things I'm still looking at, like why the Error Detection and Correction (EDAC) schemas aren't available, but I dunno if that's a priority right now.
Running Itus Shield v2 Firmware
|
|
Administrator
|
Update available: Update to the sysupgrade system, update to luci and general package changes.
https://github.com/Itus-Shield/opkgs You will need to install the initramfs first, then upgrade (like an initial install). Hopefully, this will be the last time we will need to do this. Some thoughts on updating: sysupgrade will not re-install the opks automatically, but it will know it was previously installed when you reinstall it. With the fix to luci, you can successfully select additional paths to save during backups (like i save /etc/adblock so my backups of the blocklists are immediately available without having to go redownload and process them). When you reinstall adblock, it'll see the existing config file and give you a warning that it's putting the config that is in the opkg (the default one) as adblock.opkg and using the backup one. Also, for anyone who is interested, I have enabled kernel debugging for this build. It'll make ti easier to track down issues. it makes the size bigger, but that isn't an issue we really have to deal with.
Running Itus Shield v2 Firmware
|
|
|
Still having trouble when rebooting with not saving passwords or settings, I must be doing something wrong? Are these switches correct using version 2 ROUTER: dev/mmcblk1p2 BRIDGE: /dev/mmcblk1p4 Gateway: /dev/mmcblk1p3 Should I be using mount /dev/mmcblk1p? /overlay or mount /dev/mmcblk1p? /mnt Do I need to mkfs.f2fs /dev/mmcblk1p? after each time I copy over a new initramfs-kernel.bin file or is it a one time format? When doing a system upgrade via flash firmware I get the below message, even when Ive downloaded both initramfs and system upgrade files from the web site at the same. On Mon, 27 Jul 2020 at 20:06, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote: Update available: Update to the sysupgrade system, update to luci and general package changes. |
flash iamge failes.png (135K) |
Administrator
|
Correct. mount /dev/mmcblk1p? /mnt This is because under the new filesystem, /overlay actually is used (unlike before) No. I'm not entirely sure it's even needed, but if you do, it would only need to be one once.. OpenWrt had issues with the way I had the naming convention (of all things) for the device. When that changes, the sysupgrade system changes and the previous versions can't read the file (or rather, the directory names change and make it unable to FIND it). Download the Gateway Initramfs file: https://github.com/Itus-Shield/opkgs/raw/kernel-5.4/targets/octeon/generic/openwrt-octeon-itus_shield-gateway-initramfs-kernel.bin Install it to your ItusgatewayImage: mount /dev/mmcblk1p1 /mnt cp openwrt-octeon-itus_shield-gateway-initramfs-kernel.bin /mnt/ItusgatewayImage umount /mnt Because you aren't sure about it, setup the filesystem: mkfs.f2fs /dev/mmcblk1p3 reboot Download the Gateway sysupgrade: https://github.com/Itus-Shield/opkgs/raw/kernel-5.4/targets/octeon/generic/openwrt-octeon-itus_shield-gateway-squashfs-sysupgrade.tar Flash the sysupgrade via luCi or CLI: When running from the Initramfs image, nothing can be saved. You can leave the "Save Configuration" checked, it won't matter. It'll reboot and then come back up. Your mount should look something like this: root@Shield:/# mount /dev/root on /rom type squashfs (ro,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,noatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime) cgroup on /sys/fs/cgroup type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,net_cls,net_prio,pids) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime) /dev/loop0 on /overlay type f2fs (rw,lazytime,noatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active) overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work) tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000) debugfs on /sys/kernel/debug type debugfs (rw,noatime) Notice that overlayfs:/overlay is set.. You can then set your device password and set the SSH key.
Running Itus Shield v2 Firmware
|
«
Return to Technical Discussion
|
1 view|%1 views
| Free forum by Nabble | Edit this page |