[FIRMWARE] Itus Shield v2

Next Topic
 
classic Classic list List threaded Threaded
115 messages Options
1234 ... 6
Reply | Threaded
Open this post in threaded view
|

[FIRMWARE] Itus Shield v2

Grommish
Administrator
This post was updated on .
Below are the instruction for flashing the firmware on your Itus Networks Shield.

*** Disclaimer: I am not affliated, endorsed, or recognized by anyone who was associated with Itus Networks.  This is a derived work of OpenWrt and released under GNU GPL 2.0.  While I will always do my utmost to ensure the safety of the device, any liability risk of damage is yours, and yours alone.

That being said, most of the Shield users probably aren't actually using it.

Requirements:
A working Itus Networks Shield, with at least the ability and knowledge of how to ssh/scp
A USB console rollover cable would be ideal. (8N1 115200 8N1 Hardware/Software Flow Control OFF)

If your shield isn't working at all, follow How to unbrick your Shield and get it at least working at that level, then come back.

Background:
The Shield was originally shipped with 3 modes and 4 eMMC partitions.  Bridge, Router, Gateway modes available via front-position GPIO selector.  This image will alter the Gateway mode, image, and partition.  I used this slot because the original Shield Gateway image was reportedly non-functional anyway.  This will NOT alter your BRIDGE/ROUTER images or settings.

Flashing:
Boot the Shield into any mode that you can access it via ssh/scp (Router mode, by default, is the easiest, and I am going to make the assumption it is being used)
Download the ItusgatewayImage

Now, we need to mount the storage partition on the Shield.

On the device:

umount /overlay
mount /dev/mmcblk0p1 /overlay
cp /overlay/ItusgatewayImage /overlay/ItusgatewayImage-bak

Note: The umount /overlay SHOULD return "umount: can't unmount /overlay: Invalid argument".  This is a sanity check to make sure /overlay isn't pointing elsewhere
This will make a backup copy of your existing (stock) Gateway image..

For Linux shell users, you can just cut/paste the following:
ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.10.10.10 "umount /overlay; mount /dev/mmcblk0p1 /overlay && cp /overlay/ItusgatewayImage /overlay/ItusgatewayImage-bak"

Copying the new image:
Now we need to copy the ItusgatewayImage to the device.  Go to the directory you downloaded ItusgatewayImage and scp the file to the device in the /overlay directory.

Shell users:
scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.10.10.10 ItusgatewayImage root@10.10.10.10:/overlay

Yay! Your done.  Make sure your Front Panel Switch is in the RIGHT (G) selection and reboot.

If you have a console cable, you can watch the actual installation on boot.

Boot is complete when the (M) light on the front of the Shield turns ORANGE.

Tech Notes:  The Image looks for a keystone file ( /.norwits) on init.  If it doesn't find it, it deletes everything in the partition and copies the internals of the image file over.  On a side note, this allows us to make use of the internal wear-leveling for the eMMC chips, so "flashing" like most routers shouldn't degrade the storage as fast.  This also means you can always remove /.norwits from the partition and "reset" the device.. More of this later.

At this point, eth0 is the WAN interface, eth1/eth2 are the LAN interfaces.  Connect eth0 to you internal router, and your PC to eth1/2, and your PC should be assigned a 10.10.10.x IP address and you should be online.
enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.10.10.201  netmask 255.255.255.0  broadcast 10.10.10.255
        inet6 fd18:640:804c:0:9ce:f97e:dc6f:753d  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::5ac2:4118:9a97:7ccb  prefixlen 64  scopeid 0x20<link>
        inet6 fd18:640:804c:0:5f9d:bd6b:93fe:db02  prefixlen 64  scopeid 0x0<global>

You should be able to browse to http://10.10.10.10 and log into luCi.

luCi console
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Shield v2

Grommish
Administrator
Now that the Firmware is installed...

Packages:

The Shield is a mips64 device on a CPU that isn't widely supported, but it doesn't mean it is BAD.  However, it does mean we do not enjoy the same level of updates as everyone else.

Currently, I am optimizing the build for Octeon3 devices, because that is what we have.  I don't know the interoperability of the base mips64 packages OpenWrt does build (the core files are build-bot'ed).  I'm still playing with it, but it's a software configuration rather than firmware.

Until we figure it out, if you need/want/desire a OpenWrt package (official or not) built for the Shield, let me know and I will post the .ipk for it.

Here is a listing of the Pre-Installed packages:

adblock - 4.0.4-4
base-files - 220-r13274-da14e2f478
block-mount - 2020-05-06-eec16e2f-1
blockd - 2020-05-06-eec16e2f-1
bridge - 1.6-3
busybox - 1.31.1-1
ca-bundle - 20190110-2
cgi-io - 19
coreutils - 8.32-1
coreutils-sort - 8.32-1
dnsmasq - 2.81-2
dropbear - 2019.78-4
e2fsprogs - 1.45.6-1
ethtool - 5.4-1
firewall - 2019-11-22-8174814a-1
fstools - 2020-05-06-eec16e2f-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2019-12-31-0e34af14-3
ip6tables - 1.8.4-1
iperf3 - 3.7-1
iptables - 1.8.4-1
jshn - 2020-02-27-7da66430-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 4.19.115-1-6087114890842128ae6a54e7b90dbc7e
kmod-fs-autofs4 - 4.19.115-1
kmod-ip6tables - 4.19.115-1
kmod-ipt-conntrack - 4.19.115-1
kmod-ipt-core - 4.19.115-1
kmod-ipt-nat - 4.19.115-1
kmod-ipt-offload - 4.19.115-1
kmod-ledtrig-default-on - 4.19.115-1
kmod-ledtrig-heartbeat - 4.19.115-1
kmod-ledtrig-netdev - 4.19.115-1
kmod-ledtrig-timer - 4.19.115-1
kmod-lib-crc-ccitt - 4.19.115-1
kmod-nf-conntrack - 4.19.115-1
kmod-nf-conntrack6 - 4.19.115-1
kmod-nf-flow - 4.19.115-1
kmod-nf-ipt - 4.19.115-1
kmod-nf-ipt6 - 4.19.115-1
kmod-nf-nat - 4.19.115-1
kmod-nf-reject - 4.19.115-1
kmod-nf-reject6 - 4.19.115-1
kmod-ppp - 4.19.115-1
kmod-pppoe - 4.19.115-1
kmod-pppox - 4.19.115-1
kmod-slhc - 4.19.115-1
libblkid1 - 2.35.1-1
libblobmsg-json - 2020-02-27-7da66430-1
libc - 1.1.24-2
libcomerr0 - 1.45.6-1
libdaq - 2.2.2-1
libdnet - 1.12-1
libext2fs2 - 1.45.6-1
libf2fs6 - 1.13.0-1
libgcc1 - 8.4.0-2
libhwloc - 2.2.0-1
libip4tc2 - 1.8.4-1
libip6tc2 - 1.8.4-1
libiwinfo-lua - 2020-03-22-9f5a7c4f-1
libiwinfo20200105 - 2020-03-22-9f5a7c4f-1
libjson-c4 - 0.13.1-1
libjson-script - 2020-02-27-7da66430-1
liblua5.1.5 - 5.1.5-7
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
libmbedtls12 - 2.16.6-1
libnghttp2-14 - 1.40.0-1
libnl-tiny - 2019-10-29-0219008c-1
libopenssl1.1 - 1.1.1g-1
libpcap1 - 1.9.1-2
libpciaccess - 0.16-1
libpcre - 8.43-2
libpthread - 1.1.24-2
librt - 1.1.24-2
libss2 - 1.45.6-1
libstdcpp6 - 8.4.0-2
libtirpc - 1.2.6-1
libubox20191228 - 2020-02-27-7da66430-1
libubus-lua - 2020-02-05-171469e3-1
libubus20191227 - 2020-02-05-171469e3-1
libuci20130104 - 2020-04-24-ec8d3233-3
libuclient20160123 - 2020-02-15-af585dbd-1
libustream-mbedtls20200215 - 2020-03-13-5e1bc342-1
libuuid1 - 2.35.1-1
libxtables12 - 1.8.4-1
logd - 2019-12-31-0e34af14-3
lua - 5.1.5-7
luajit - 2.1.0-beta3-3
luci - git-20.111.65731-398b198
luci-app-adblock - git-20.111.65731-398b198
luci-app-firewall - git-20.111.65731-398b198
luci-app-opkg - git-20.111.65731-398b198
luci-base - git-20.130.24305-e5fe16c
luci-lib-ip - git-20.111.65731-398b198
luci-lib-jsonc - git-20.111.65731-398b198
luci-lib-nixio - git-20.111.65731-398b198
luci-mod-admin-full - git-20.111.65731-398b198
luci-mod-network - git-20.111.65731-398b198
luci-mod-status - git-20.111.65731-398b198
luci-mod-system - git-20.125.36156-d6dba39
luci-proto-ipv6 - git-20.111.65731-398b198
luci-proto-ppp - git-20.111.65731-398b198
luci-ssl - git-20.111.65731-398b198
luci-theme-bootstrap - git-20.111.65731-398b198
luci-theme-openwrt-2020 - git-20.123.78783-97bd192
mkf2fs - 1.13.0-1
mtd - 25
netifd - 2020-04-14-cfccdc22-3
odhcp6c - 2020-03-28-f575351c-16
odhcpd-ipv6only - 2020-05-04-5ce07702-3
openwrt-keyring - 2019-07-25-8080ef34-1
opkg - 2020-05-07-f2166a89-1
perl - 5.28.1-5
ppp - 2.4.8.git-2020-03-21-2
ppp-mod-pppoe - 2.4.8.git-2020-03-21-2
procd - 2020-04-25-17e7ae76-1
px5g-mbedtls - 9
rpcd - 2020-01-05-efe51f41-2
rpcd-mod-file - 2020-01-05-efe51f41-2
rpcd-mod-iwinfo - 2020-01-05-efe51f41-2
rpcd-mod-luci - 20191114
rpcd-mod-rrdns - 20170710
snort3 - 3.0.0-beta-4
tcpdump - 4.9.3-1
ubox - 2019-12-31-0e34af14-3
ubus - 2020-02-05-171469e3-1
ubusd - 2020-02-05-171469e3-1
uci - 2020-04-24-ec8d3233-3
uclient-fetch - 2020-02-15-af585dbd-1
uhttpd - 2020-03-13-5e9c23c6-1
uhttpd-mod-ubus - 2020-03-13-5e9c23c6-1
urandom-seed - 1.0-1
urngd - 2020-01-21-c7f7b6b6-1
usign - 2019-09-21-f34a383e-1
zlib - 1.2.11-3
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Shield v2

Grommish
Administrator
Going Forward....

The Shield has tech specs that are higher-end consumer router devices.  The Shield has a Dual-core 1Ghz CPU, just like my Netgear Nighthawk X6.. So, it probably will perform similarly, at least.

Snort3 was my primary focus, since it is what the device was created for.  It is loading a LOT of rules for testing.  These might be trimmed down later.

Anyone with LUA or Javascript experience who wants to work with me on creating a control interface for luCi, give me a shout..

Adblock is installed and enabled by default.

General configurations are the best I know.  If you have something better, test it and then share it with me..  I can bake it into future updates.

Above all, have fun.  I wouldn't think many people who didn't enjoy this sort of thing bought the Shield, so go have some fun with it.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Update to /etc/init.d/snort

Grommish
Administrator
This is an updated init.d script for snort.  Snort+ in inline-mode (-Q) screws with DHCP/DNS, so we'll remove it for now and reserve it for Bridge/Gateway mode.

Drop this file in /etc/init.d/snort:
/etc/init.d/snort

Then you can do a

service snort restart

Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Wisiwyg
Got your email blast just now....

Cool! My Shield has been shelved since everything went belly up. I'll pull it out, power up and give this a try.

Thanks for doing this.

Wisi
Shield Pro v1, Chaos Calmer, FW 1.51 SP1, v8.3.2, Bridge Mode
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
Welcome.. If you run into any issues, hit me up.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

LTLeg
Wanted to come into the last thread for this, but see it's been closed.

I wanted to recommend a fan for the Shield.

It works in consoles for modding the cooling (Dreamcast, specifically, I'm sure others), and it much quieter than stock, and cools better.
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
Good posting..

Cooling was a concern when I first started playing with the Shield.  The temps never get excessive, but the "passive case cooling" model never gave me thrills..

I ended up trying to find a 5vDC fan that was actually 5vDC (and not 12vDC) so I could use the internal header, but never found one.  I did throw a copper heatsink on there from a RaspPi and it seemed to help mitigate the heat

You can see the post I made about it here.

So, it's been a few days, whose gotten it to work and who is having issues?


Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Turrican
Mine works, except I still need to do a reboot command after each boot (from cold) to get an IP but aside from that , brilliant! Thanks grommish
Running v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
I've not had that since getting the network driver reworked.. Hmm

Do me a favor and check your /etc/init.d/snort and see what the command string it.

It should be

 procd_set_param command $PROG -v -c $config_dir/snort.lua -i $interface --daq-dir $daq_dir --daq $daq -l $log_dir -A $alert_module --create-pidfile -D

If you have the -Q in it, it'll act as a transparent bridge.  But, again, I've not had those types of issues in a few builds.  I'll test it here after I post this.. I'll power it off and let it sit, then bring it back up and see what happens.

Turrican wrote
Mine works, except I still need to do a reboot command after each boot (from cold) to get an IP but aside from that , brilliant! Thanks grommish
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
Actually..  In addition to checking the snort init.d, if you have shell access Turrican..

Grab this script (itus-custom-setup), put it on your Shield and run it..
This is the initial config script in the image, but deletes itself after first run.

scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null itus-custom-setup root@10.10.10.10:/tmp
ssh -q -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.10.10.10 "sh /tmp/itus-custom-setup"

Same goes for anyone else who is on v2 and wants to make double sure the settings are where they should be.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
Here is a video of the boot process from a cold, unplugged state..

https://youtu.be/XB-tjcb2Nio

https://youtu.be/XB-tjcb2Nio
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Turrican
In reply to this post by Grommish
still the same Grommish,  The script didnt help and the snort config is exactly the same as yours.  From power on cold I must do a reboot command otherwise Eth0 does not get an ip. Totally consistent and repeatable.

Anyone else having this issue on the new V2 FW?  or is it just me?  strange as I have 2 shields and they both do this.

Last thing I'm going to try later on is plugging the Shield DIRECTLY into my Cable Modem... see how that goes. I'll let you know

Right now my set up is:

Cable Modem -> Synology Router -> Switch -> Intra-house CAT6 cabling -> switch -> long cat6 cable ->switch ->shield Eth0

Sounds like a nightmare but everything always works on my workstation which is at the end of this chain also (desktop PC, work laptop, Synology NAS) but I'll cut all this connectivity out and connect to my modem just to test.

Running v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Grommish
Administrator
My network is just as convoluted :)

I go

Cable Modem -> Nighthawk X6 R8000.  From the Nighthawk (192.168.1.0/24), I go to a 48-port switch off one port for the main network and a drop to a really old DLink DIR655 (192.168.5.0/24) that has a Server 2016 machine providing the DHCP/DNS/BOOTP.  The Shield then comes off the DLink (10.10.10.0/24) and then goes to my laptop.

Do me a favor..

On the Shield, unplug eth0 and then type:

tcpdump -i eth0 -vvv -s 1500 '((port 67 or port 68) and (udp[8:1] = 0x1))' | tee /tmp/dhcplog

Then plug eth0 back in.

Give it a few seconds (or when it starts repeating), Cntl-c to stop it and then email me the /tmp/dhcplog file or post it.

Also, can you also do:
uci show > /tmp/configs

and send that as well.

This is what you SHOULD be seeing from the tcpdump
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 1500 bytes
[151542.815599] eth0: Link down
[151551.008458] eth0: 1000 Mbps Full duplex, port 0, queue 0
18:39:48.881198 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.nextyourcontent.com.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 2c:26:5f:00:00:00 (oui Unknown), lengt)
          Client-Ethernet-Address 2c:26:5f:00:00:00 (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            MSZ Option 57, length 2: 576
            Parameter-Request Option 55, length 8:
              Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
              Domain-Name, BR, NTP, Classless-Static-Route
            Vendor-Class Option 60, length 12: "udhcp 1.31.1"
            Hostname Option 12, length 6: "Shield"
            END Option 255, length 0
            PAD Option 0, length 0, occurs 20
18:39:48.897050 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.nextyourcontent.com.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 2c:26:5f:00:00:00 (oui Unknown), lengt)
          Client-Ethernet-Address 2c:26:5f:00:00:00 (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Request
            Requested-IP Option 50, length 4: 192.168.5.110
            Server-ID Option 54, length 4: 192.168.5.2
            MSZ Option 57, length 2: 576
            Parameter-Request Option 55, length 8:
              Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
              Domain-Name, BR, NTP, Classless-Static-Route
            Vendor-Class Option 60, length 12: "udhcp 1.31.1"
            Hostname Option 12, length 6: "Shield"
            END Option 255, length 0
            PAD Option 0, length 0, occurs 8
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Update to /etc/init.d/snort

Turrican
Will do when I get a chance 

Cheers


From: Grommish [via Itus Networks Owners Forum] <ml+[hidden email]>
Sent: Tuesday, May 19, 2020 7:54:02 PM
To: Turrican <[hidden email]>
Subject: Re: Update to /etc/init.d/snort
 
My network is just as convoluted :)

I go

Cable Modem -> Nighthawk X6 R8000.  From the Nighthawk (192.168.1.0/24), I go to a 48-port switch off one port for the main network and a drop to a really old DLink DIR655 (192.168.5.0/24) that has a Server 2016 machine providing the DHCP/DNS/BOOTP.  The Shield then comes off the DLink (10.10.10.0/24) and then goes to my laptop.

Do me a favor..

On the Shield, unplug eth0 and then type:

tcpdump -i eth0 -vvv -s 1500 '((port 67 or port 68) and (udp[8:1] = 0x1))' | tee /tmp/dhcplog

Then plug eth0 back in.

Give it a few seconds (or when it starts repeating), Cntl-c to stop it and then email me the /tmp/dhcplog file or post it.

Also, can you also do:
uci show > /tmp/configs

and send that as well.

This is what you SHOULD be seeing from the tcpdump
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 1500 bytes
[151542.815599] eth0: Link down
[151551.008458] eth0: 1000 Mbps Full duplex, port 0, queue 0
18:39:48.881198 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.nextyourcontent.com.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 2c:26:5f:00:00:00 (oui Unknown), lengt)
          Client-Ethernet-Address 2c:26:5f:00:00:00 (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Discover
            MSZ Option 57, length 2: 576
            Parameter-Request Option 55, length 8:
              Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
              Domain-Name, BR, NTP, Classless-Static-Route
            Vendor-Class Option 60, length 12: "udhcp 1.31.1"
            Hostname Option 12, length 6: "Shield"
            END Option 255, length 0
            PAD Option 0, length 0, occurs 20
18:39:48.897050 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 328)
    0.nextyourcontent.com.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 2c:26:5f:00:00:00 (oui Unknown), lengt)
          Client-Ethernet-Address 2c:26:5f:00:00:00 (oui Unknown)
          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Request
            Requested-IP Option 50, length 4: 192.168.5.110
            Server-ID Option 54, length 4: 192.168.5.2
            MSZ Option 57, length 2: 576
            Parameter-Request Option 55, length 8:
              Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
              Domain-Name, BR, NTP, Classless-Static-Route
            Vendor-Class Option 60, length 12: "udhcp 1.31.1"
            Hostname Option 12, length 6: "Shield"
            END Option 255, length 0
            PAD Option 0, length 0, occurs 8
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-tp2014p2028.html
To start a new topic under Technical Discussion, email ml+[hidden email]
To unsubscribe from Itus Networks Owners Forum, click here.
NAML
Running v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Potential thermal issues on Shield

Grommish
Administrator
Massive thanks to @Turrican for putting up with me during this testing! :D

Has anyone else experienced possible heat-related issues regarding the Shield?  Turrican's shield refused to pull an IP address for no apparent reason - in fact, it was almost like the Network controller was simply not working at all.

We worked on it for a bit before he had to go, and nothing..  After we gave up, I asked him to unplug it while he did what he had to do and revisit it once it cooled down (I had suspicions of thermal issues from almost day 1 with the Shield).  He came back and it fired right up without issues..

My personal box has lived without the lid or "thermal pad" since the first week until yesterday, but even then, I have the copper block on the CPU (swapped for the foam pad) and it's under an AC vent.  So, if during testing you seem to have network issues, try letting it sit for 5-10 minutes and trying again.. If it works, maybe we can figure out how to mediate the thermals most effectively.




Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Potential thermal issues on Shield

Grommish
Administrator
How to deal with heat?

I've added the collectd subsystem to the latest image to see what sensor data we can collect.  Thermals doesn't seem to be working and the sensor package is completely erroring out.  I've got a post up on OpenWrt to see if it can be fixed or what I missed.

In the mean time?  It's what I had laying around, but it'll certainly show if heat-soak is an issue...

Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Potential thermal issues on Shield

Turrican
Bought the exact fan which ltleg recommended (thanks for that) but I can’t get it working. I plugged it into what I assumed was the fan header (white socket  on left under reset switch  pictured below) but it doesn’t move. Not sure if it’s maybe thermally controlled? Any ideas? Thanks
61228BFD-EFC8-497A-823F-37CF77A2FE0D.jpeg
Running v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: Potential thermal issues on Shield

Roadrunnere42
Hi
I have a Nvidia Jetson nano and I bought the except same fan as you, placed it on the 3 pins on the white socket and nothing happened I found out later that you have to run a script to set the fan speed this link below
it's what I use on the nano and works fine, but it needs python, not sure is the Shield has got python installed by default

Roadrunneruk

On Mon, 25 May 2020 at 12:27, Turrican [via Itus Networks Owners Forum] <[hidden email]> wrote:
Bought the exact fan which ltleg recommended (thanks for that) but I can’t get it working. I plugged it into what I assumed was the fan header (white socket  on left under reset switch  pictured below) but it doesn’t move. Not sure if it’s maybe thermally controlled? Any ideas? Thanks
61228BFD-EFC8-497A-823F-37CF77A2FE0D.jpeg
Running 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-tp2014p2032.html
To start a new topic under Technical Discussion, email [hidden email]
To unsubscribe from Itus Networks Owners Forum, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Potential thermal issues on Shield

Grommish
Administrator
I could never get that fan header to do anything. I went thru 3 fans I bought and nothing.

I'll look at that script, Road! I don't know if I put python 3 back in or not. It usually isn't in OpenWrt because of its size.  We don't have that issue, so I built it in at one point. 

Thanks for all the help all! 


On Mon, May 25, 2020, 10:05 AM Roadrunnere42 [via Itus Networks Owners Forum] <[hidden email]> wrote:
Hi
I have a Nvidia Jetson nano and I bought the except same fan as you, placed it on the 3 pins on the white socket and nothing happened I found out later that you have to run a script to set the fan speed this link below
it's what I use on the nano and works fine, but it needs python, not sure is the Shield has got python installed by default

Roadrunneruk

On Mon, 25 May 2020 at 12:27, Turrican [via Itus Networks Owners Forum] <[hidden email]> wrote:
Bought the exact fan which ltleg recommended (thanks for that) but I can’t get it working. I plugged it into what I assumed was the fan header (white socket  on left under reset switch  pictured below) but it doesn’t move. Not sure if it’s maybe thermally controlled? Any ideas? Thanks
61228BFD-EFC8-497A-823F-37CF77A2FE0D.jpeg
Running 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-tp2014p2032.html
To start a new topic under Technical Discussion, email [hidden email]
To unsubscribe from Itus Networks Owners Forum, click here.
NAML



If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Shield-v2-tp2014p2033.html
To unsubscribe from [FIRMWARE] Itus Shield v2, click here.
NAML
Running Itus Shield v2 Firmware
1234 ... 6