[FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

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

[FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
Hey All,

For the past few days, I've been playing around in an attempt to update/upgrade my Shield.  The hotfixes are fantastic patches, but they are only patches.

To that end, I've been working to get a new OpenWRT image built for the Shield.  Sadly, the source went down with Itus, but we can rebuild it - faster, stronger, etc.

Anyone with OpenWRT knowledge want to help with this project?  I would rather stay *here* and play nice with you all rather than try and deal with OpenWRT general forums (because there isn't a Shield specific section for a reason).

Installing the test image:
*** Note: At this time, this is a non-destructive process.  However, as testing continues, at some point I will need to over-write the Itus Networks OEM information.  At this time, I am set to use the Gateway Image slot ONLY


Download the ItusgatewayImage file (links below)

(Shield) SSH (in any mode) to the Shield


root@Openwrt:/# mount /dev/mmcblk0p1 /overlay


Please note that the Itus OEM image uses /dev/mmcblk0pX and OpenWrt uses /dev/mmcblk1pX.  If you are on an Itus OEM Image, use mmcblk0p1 but remember that in the OpenWrt, it will be mmcblk1p1.

(PC) Secure Copy the ItusgatewayImage to the Shield:


scp ItusgatewayImage root@10.10.10.10:/overlay


(Shield) Then unmount the /overlay mount point:


root@OpenWrt:/# umount /overlay


Put the front-panel switch into Gateway (Right) mode and reboot the Shied


root@OpenWrt:/# reboot -f


You can watch via Console cable the boot process (if you have one) OR wait for the Orange light to come on - this will signify Boot Complete.

Defaults:
By default, the Shield uses eth0 as WAN, eth1 and eth2 as LAN, with an IP address of 10.10.10.10 and DHCP (client on the WAN, server on the LAN)

There is no root password.

Troubleshooting:
If for some reason you boot the Shield and are unable to connect to the network (Network registration failed on Linux, or the Exclamation Mark in Windows), boot back to your working Shield mode, ssh into the shield, and do the following:


root@OpenWrt:/# mount /dev/mmcblk1p1 /overlay
root@OpenWrt:/# touch /overlay/ItusgatewayImage
root@OpenWrt:/# umount /overlay
root@OpenWrt:/# reboot -f


Make sure you flip the front panel back to Gateway before rebooting.  This happens sometimes and I'm not sure why, this seems to fix it 99% of the time.

Links:

ItusgatewayImage
ItusgatewayImage MD5

***************************

Updated: May 27, 2019

-- Fresh Build --

*[Build] - Base Package/DefConfig Used
*[Build] - Started working on rc.d/init.d script for boot (S11extroot)
*[Kernel] - Updated to 4.14.119
*[Kernel] - Added Cavium Octeon III network driver
*[Kernel] - Enable Octeon III software fpa by default
*[Kernel] - Enable .config and /proc/config.gz support
*[Kernel] - Enable gzip and xz kernel compression
*[Kernel] - Set Kernel Interrupt to 1000Hz (1ms)
*[Kernel] - Add f2fs (Flash Friendly File System) support
*[Packages] - Added ca-bundle/ca-certificate (base)
*[Packages] - Added Python2.7 (languages)
*[Packages] - Added curl (network/file transfer)
*[Packages] - Added dosfstools (utilities/filesystem)
*[Packages] - Added wget (network/file transfer)
*[Packages] - Added nano (Utilities/Editors)
*[Packages] - Add bash (Utilities/Shells)
*[Packages] - Busybox - Add verbose mode for Applets (Settings)
*[Packages] - Busybox - Add fdisk (Linux System Utilities)
*[Packages] - Busybox - Add 'more' (Linux System Utilities)

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

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
Hardware Update:

I was testing the chassis layout and became concerned with heat soak of the CPU.  The sponge-foam that was on the chip didn't look or feel like thermal-conductive foam and the box was getting *very* warm.

I went out and purchased a heatsink kit for a Raspberry Pi.  The kit came with 3 heatsinks, but I only needed the one.  I might be able to use the other two on the bottom of the PCB board, but for now, the flat copper heatsink is perfect for what I wanted to do.  The heatsinks comes with thermal pads/double stick tape already installed, so you just peal and stick.

I probed the copper after installing and letting it "heat up" and recorded 123 degrees F (50.5 degrees C) at idle on the surface.  I don't even want to think about what it ramps up to when it's actually working under load.  Heat is the enemy of both the board and the chipset.  I'm working on finding a true 5vDC 3-pin fan to hook to the pin-header on the board, but it's not easy.  I've gone through 3 fans and each was labelled as 5vDC but actually at 12vDC.  Tsk.  If I can externally mount a fan over the vent holes to drag air out of the case (pull), it'll cool the temps even further.

Just an idea for those who feel like messing with it!

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

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Roadrunnere42
Hi
im doing it now but will need a place to put files as they are about 40mb each, they come from a fresh factory reset with v1.51sp1

Andrew

On Fri, 10 May 2019 at 04:02, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
I need someone who can pull the extroot files for each of the images.  It needs to be unmolested (updates and hotfixes are fine).

Here is what needs to be done:
SSH to the Shield

cd /
mkdir extra
mkdir tmpback
mount /dev/mmcblk0p2 /extra
cp -a /extra/* /tmpback/
cd tmpback
tar c -zvf router-extroot.tgz *


scp the file to your machine.  Then, clean up:

cd /tmpback
rm -rf *
cd /
umount /extra


 This need to be done 3 times, one for router, gateway, bridge.

mmcblk0p2 = router
mmcblk0p3 = gateway
mmcblk0p4 = bridge

Just make sure you change the tar filename :D


If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1729.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: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Roadrunnere42
Looks like you have been working hard, not sure i can help with suggestion but a look over the logs nothing jumps out but i do agree that the ports should stay the way itus had them set up (wan = eth0, lan = eth1 eth2, default to 10.10.10.10).
Keep up the great work and look forward to tring it out.

Roadrunnere42

On Tue, 14 May 2019 at 00:17, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
Below are the Kernel and System logs from the latest build.  Aside from the /extroot and init.d support, does anyone see anything that needs to be addressed before moving on to other things?

One thing I did do was reset the network config to match the Shield Router specs (wan = eth0, lan = eth1 eth2, default to 10.10.10.10).  Made it easier to deal with the swapping from mode to mode without having to swap wires.


Kernel Log:
[    0.000000] Linux version 4.14.115 (grommish@gribbits) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9948-290a7dc0c7)) #0 SMP Thu May 9 16:33:39 2019
[    0.000000] Skipping L2 locking due to reduced L2 cache size
[    0.000000] CVMSEG size: 5 cache lines (640 bytes)
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 000d9602 (Cavium Octeon III)
[    0.000000] FPU revision is: 00739600
[    0.000000] Checking for the multiply/shift bug... no.
[    0.000000] Checking for the daddiu bug... no.
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 000000000c000000 @ 0000000003100000 (usable)
[    0.000000]  memory: 0000000000c00000 @ 000000000f200000 (usable)
[    0.000000]  memory: 000000002f000000 @ 0000000020000000 (usable)
[    0.000000]  memory: 0000000001f66d70 @ 0000000001100000 (usable)
[    0.000000] Wasting 243712 bytes for tracking 4352 unused pages
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Using passed Device Tree.
[    0.000000] software IO TLB: mapped [mem 0x03115000-0x03155000] (0MB)
[    0.000000] Primary instruction cache 78kB, virtually tagged, 39 way, 16 sets, linesize 128 bytes.
[    0.000000] Primary data cache 32kB, 32-way, 8 sets, linesize 128 bytes.
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000000000000-0x00000000efffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003065fff]
[    0.000000]   node   0: [mem 0x0000000003100000-0x000000000f0fffff]
[    0.000000]   node   0: [mem 0x000000000f200000-0x000000000fdfffff]
[    0.000000]   node   0: [mem 0x0000000020000000-0x000000004effffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000004effffff]
[    0.000000] On node 0 totalpages: 257126
[    0.000000]   DMA32 zone: 3516 pages used for memmap
[    0.000000]   DMA32 zone: 0 pages reserved
[    0.000000]   DMA32 zone: 257126 pages, LIFO batch:31
[    0.000000] random: get_random_bytes called from start_kernel+0x90/0x4fc with crng_init=0
[    0.000000] percpu: Embedded 19 pages/cpu s39472 r8192 d30160 u77824
[    0.000000] pcpu-alloc: s39472 r8192 d30160 u77824 alloc=19*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 253610
[    0.000000] Kernel command line:  bootoctlinux 0x20000000 numcores=2 serial#=752011191521-36409 console=ttyS0,115200
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.000000] Memory: 962520K/1028504K available (5182K kernel code, 330K rwdata, 1272K rodata, 8684K init, 16667K bss, 65984K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000] 	RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 127
[    0.000000] CIB interrupt controller probed: 800107000000e000 23
[    0.000000] CIB interrupt controller probed: 800107000000e200 12
[    0.000000] CIB interrupt controller probed: 800107000000e400 6
[    0.000000] CIB interrupt controller probed: 800107000000ec00 15
[    0.000000] CIB interrupt controller probed: 800107000000e600 4
[    0.000000] CIB interrupt controller probed: 800107000000e800 11
[    0.000000] CIB interrupt controller probed: 800107000000e900 11
[   21.052361] clocksource: OCTEON_CVMCOUNT: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[   21.063418] Calibrating delay loop (skipped) preset value.. 2000.00 BogoMIPS (lpj=4000000)
[   21.071666] pid_max: default: 32768 minimum: 301
[   21.076329] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[   21.082950] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[   21.090493] Checking for the daddi bug... no.
[   21.095125] Hierarchical SRCU implementation.
[   21.099671] smp: Bringing up secondary CPUs ...
[   21.104302] SMP: Booting CPU01 (CoreId  1)...
[   21.108609] CPU1 revision is: 000d9602 (Cavium Octeon III)
[   21.108613] FPU revision is: 00739600
[   21.108723] smp: Brought up 1 node, 2 CPUs
[   21.124126] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[   21.133747] futex hash table entries: 512 (order: 4, 65536 bytes)
[   21.140113] NET: Registered protocol family 16
[   21.149047] PCIe: Initializing port 0
[   21.155785] PCIe: BIST2 FAILED for port 0 (0x0000000000000003)
[   21.589901] random: fast init done
[   23.161477] PCIe: Link timeout on port 0, probably the slot is empty
[   23.167779] PCIe: Initializing port 1
[   23.174645] PCIe: BIST FAILED for port 1 (0xffffffffffffffff)
[   25.185217] PCIe: Link timeout on port 1, probably the slot is empty
[   25.197177] SCSI subsystem initialized
[   25.201073] usbcore: registered new interface driver usbfs
[   25.206471] usbcore: registered new interface driver hub
[   25.211754] usbcore: registered new device driver usb
[   25.216901] PCI host bridge to bus 0000:00
[   25.220842] pci_bus 0000:00: root bus resource [mem 0x1000000000000]
[   25.227176] pci_bus 0000:00: root bus resource [io  0x0000]
[   25.232744] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
[   25.239522] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[   25.247469] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[   25.248161] clocksource: Switched to clocksource OCTEON_CVMCOUNT
[   25.254570] NET: Registered protocol family 2
[   25.259169] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[   25.266155] TCP bind hash table entries: 8192 (order: 6, 262144 bytes)
[   25.272741] TCP: Hash tables configured (established 8192 bind 8192)
[   25.279008] UDP hash table entries: 512 (order: 3, 49152 bytes)
[   25.284883] UDP-Lite hash table entries: 512 (order: 3, 49152 bytes)
[   25.291340] NET: Registered protocol family 1
[   25.295566] PCI: CLS 0 bytes, default 128
[   25.360626] Crashlog allocated RAM at address 0x3f00000
[   25.365976] workingset: timestamp_bits=62 max_order=18 bucket_order=0
[   25.376262] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   25.382079] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[   25.393387] io scheduler noop registered
[   25.397177] io scheduler deadline registered (default)
[   25.402685] octeon_gpio 1070000000800.gpio-controller: OCTEON GPIO driver probed.
[   25.410197] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   25.416889] console [ttyS0] disabled
[   25.420343] 1180000000800.serial: ttyS0 at MMIO 0x1180000000800 (irq = 44, base_baud = 37500000) is a OCTEON
[   25.430147] console [ttyS0] enabled
[   25.437092] bootconsole [early0] disabled
[   25.445365] 1180000000c00.serial: ttyS1 at MMIO 0x1180000000c00 (irq = 45, base_baud = 37500000) is a OCTEON
[   25.455482] octeon_rng octeon_rng: Octeon Random Number Generator
[   25.461806] cacheinfo: Failed to find cpu0 device node
[   25.466971] cacheinfo: Unable to detect cache hierarchy for CPU 0
[   25.475568] loop: module loaded
[   25.479227] libphy: mdio_octeon: probed
[   25.483119] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@0: Whitelisted compatible string. Please remove
[   25.498674] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
[   25.508158] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@1: Whitelisted compatible string. Please remove
[   25.523280] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
[   25.532738] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@2: Whitelisted compatible string. Please remove
[   25.547851] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
[   25.557304] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@3: Whitelisted compatible string. Please remove
[   25.572433] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
[   25.581865] mdio_octeon 1180000001800.mdio: Probed
[   25.586881] libphy: Fixed MDIO Bus: probed
[   25.591083] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   25.597633] ehci-platform: EHCI generic platform driver
[   25.602952] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   25.609165] ohci-platform: OHCI generic platform driver
[   25.614542] usbcore: registered new interface driver usb-storage
[   25.620603] octeon_wdt: Initial granularity 5 Sec
[   26.533763] Interface 0 has 4 ports (SGMII)
[   26.538025] Interface 1 has 4 ports (SGMII)
[   26.542776] Interface 3 has 4 ports (LOOP)
[   26.552841] NET: Registered protocol family 10
[   26.559178] Segment Routing with IPv6
[   26.562942] NET: Registered protocol family 17
[   26.567436] 8021q: 802.1Q VLAN Support v1.8
[   26.572382] OF: fdt: not creating '/sys/firmware/fdt': CRC check failed
[   26.582767] Freeing unused kernel memory: 8684K
[   26.587325] This architecture does not have kernel memory protection.
[   26.599313] init: Console is alive
[   26.602926] init: - watchdog -
[   26.610875] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[   26.617875] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[   26.626577] init: - preinit -
[   26.707364] random: jshn: uninitialized urandom read (4 bytes read)
[   26.733182] random: jshn: uninitialized urandom read (4 bytes read)
[   26.752869] random: jshn: uninitialized urandom read (4 bytes read)
[   26.771818] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   29.843525] procd: - early -
[   29.846503] procd: - watchdog -
[   30.395626] procd: - watchdog -
[   30.398978] procd: - ubus -
[   30.404457] urandom_read: 1 callbacks suppressed
[   30.404462] random: ubusd: uninitialized urandom read (4 bytes read)
[   30.451557] random: ubusd: uninitialized urandom read (4 bytes read)
[   30.458100] random: ubusd: uninitialized urandom read (4 bytes read)
[   30.464880] procd: - init -
[   30.537801] kmodloader: loading kernel modules from /etc/modules.d/*
[   30.546877] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   30.555212] ip_tables: (C) 2000-2006 Netfilter Core Team
[   30.563393] nf_conntrack version 0.5.0 (7680 buckets, 30720 max)
[   30.585430] xt_time: kernel timezone is -0000
[   30.593065] PPP generic driver version 2.4.2
[   30.598126] NET: Registered protocol family 24
[   30.603840] kmodloader: done loading kernel modules from /etc/modules.d/*
[   36.618012] br-lan: port 1(eth1) entered blocking state
[   36.623299] br-lan: port 1(eth1) entered disabled state
[   36.628753] device eth1 entered promiscuous mode
[   36.643406] br-lan: port 1(eth1) entered blocking state
[   36.648675] br-lan: port 1(eth1) entered forwarding state
[   36.654237] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   36.665342] br-lan: port 2(eth2) entered blocking state
[   36.670628] br-lan: port 2(eth2) entered disabled state
[   36.676099] device eth2 entered promiscuous mode
[   36.680845] br-lan: port 2(eth2) entered blocking state
[   36.686115] br-lan: port 2(eth2) entered forwarding state
[   36.697040] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   37.628477] br-lan: port 1(eth1) entered disabled state
[   37.633974] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   37.640998] br-lan: port 2(eth2) entered disabled state
[   40.196176] random: crng init done
[   40.199595] random: 3 urandom warning(s) missed due to ratelimiting
[   45.297164] mmc1: new DDR MMC card at address 0001
[   45.302359] mmcblk1: mmc1:0001 P1XXXX 3.60 GiB 
[   45.307042] mmcblk1boot0: mmc1:0001 P1XXXX partition 1 2.00 MiB
[   45.313095] mmcblk1boot1: mmc1:0001 P1XXXX partition 2 2.00 MiB
[   45.319145] mmcblk1rpmb: mmc1:0001 P1XXXX partition 3 128 KiB
[   45.325700]  mmcblk1: p1 p2 p3 p4
[   86.890333] eth0: 1000 Mbps Full duplex, port 0, queue 0
[   86.895683] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  105.290553] eth2: 1000 Mbps Full duplex, port 2, queue 2
[  105.295907] br-lan: port 2(eth2) entered blocking state
[  105.301157] br-lan: port 2(eth2) entered forwarding state


System Log:

Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] Linux version 4.14.115 (grommish@gribbits) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9948-290a7dc0c7)) #0 SMP Thu May 9 16:33:39 2019
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Skipping L2 locking due to reduced L2 cache size
Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] CVMSEG size: 5 cache lines (640 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] bootconsole [early0] enabled
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CPU0 revision is: 000d9602 (Cavium Octeon III)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] FPU revision is: 00739600
Mon May 13 22:00:01 2019 kern.warn kernel: [    0.000000] Checking for the multiply/shift bug... no.
Mon May 13 22:00:01 2019 kern.warn kernel: [    0.000000] Checking for the daddiu bug... no.
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Determined physical RAM map:
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]  memory: 000000000c000000 @ 0000000003100000 (usable)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]  memory: 0000000000c00000 @ 000000000f200000 (usable)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]  memory: 000000002f000000 @ 0000000020000000 (usable)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]  memory: 0000000001f66d70 @ 0000000001100000 (usable)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Wasting 243712 bytes for tracking 4352 unused pages
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Initrd not found or empty - disabling initrd
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Using passed Device Tree.
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] software IO TLB: mapped [mem 0x03115000-0x03155000] (0MB)
Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] Primary instruction cache 78kB, virtually tagged, 39 way, 16 sets, linesize 128 bytes.
Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] Primary data cache 32kB, 32-way, 8 sets, linesize 128 bytes.
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Zone ranges:
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   DMA32    [mem 0x0000000000000000-0x00000000efffffff]
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   Normal   empty
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Movable zone start for each node
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Early memory node ranges
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x0000000003065fff]
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000003100000-0x000000000f0fffff]
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   node   0: [mem 0x000000000f200000-0x000000000fdfffff]
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000020000000-0x000000004effffff]
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000004effffff]
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000] On node 0 totalpages: 257126
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000]   DMA32 zone: 3516 pages used for memmap
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000]   DMA32 zone: 0 pages reserved
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000]   DMA32 zone: 257126 pages, LIFO batch:31
Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x90/0x4fc with crng_init=0
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] percpu: Embedded 19 pages/cpu s39472 r8192 d30160 u77824
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000] pcpu-alloc: s39472 r8192 d30160 u77824 alloc=19*4096
Mon May 13 22:00:01 2019 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 253610
Mon May 13 22:00:01 2019 kern.notice kernel: [    0.000000] Kernel command line:  bootoctlinux 0x20000000 numcores=2 serial#=752011191521-36409 console=ttyS0,115200
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Memory: 962520K/1028504K available (5182K kernel code, 330K rwdata, 1272K rodata, 8684K init, 16667K bss, 65984K reserved, 0K cma-reserved)
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] Hierarchical RCU implementation.
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] 	CONFIG_RCU_FANOUT set to non-default value of 32
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=2.
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] NR_IRQS: 127
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e000 23
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e200 12
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e400 6
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000ec00 15
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e600 4
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e800 11
Mon May 13 22:00:01 2019 kern.info kernel: [    0.000000] CIB interrupt controller probed: 800107000000e900 11
Mon May 13 22:00:01 2019 kern.info kernel: [   21.052361] clocksource: OCTEON_CVMCOUNT: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
Mon May 13 22:00:01 2019 kern.info kernel: [   21.063418] Calibrating delay loop (skipped) preset value.. 2000.00 BogoMIPS (lpj=4000000)
Mon May 13 22:00:01 2019 kern.info kernel: [   21.071666] pid_max: default: 32768 minimum: 301
Mon May 13 22:00:01 2019 kern.info kernel: [   21.076329] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   21.082950] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
Mon May 13 22:00:01 2019 kern.warn kernel: [   21.090493] Checking for the daddi bug... no.
Mon May 13 22:00:01 2019 kern.info kernel: [   21.095125] Hierarchical SRCU implementation.
Mon May 13 22:00:01 2019 kern.info kernel: [   21.099671] smp: Bringing up secondary CPUs ...
Mon May 13 22:00:01 2019 kern.info kernel: [   21.104302] SMP: Booting CPU01 (CoreId  1)...
Mon May 13 22:00:01 2019 kern.info kernel: [   21.108609] CPU1 revision is: 000d9602 (Cavium Octeon III)
Mon May 13 22:00:01 2019 kern.info kernel: [   21.108613] FPU revision is: 00739600
Mon May 13 22:00:01 2019 kern.info kernel: [   21.108723] smp: Brought up 1 node, 2 CPUs
Mon May 13 22:00:01 2019 kern.info kernel: [   21.124126] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Mon May 13 22:00:01 2019 kern.info kernel: [   21.133747] futex hash table entries: 512 (order: 4, 65536 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   21.140113] NET: Registered protocol family 16
Mon May 13 22:00:01 2019 kern.notice kernel: [   21.149047] PCIe: Initializing port 0
Mon May 13 22:00:01 2019 kern.notice kernel: [   21.155785] PCIe: BIST2 FAILED for port 0 (0x0000000000000003)
Mon May 13 22:00:01 2019 kern.notice kernel: [   21.589901] random: fast init done
Mon May 13 22:00:01 2019 kern.notice kernel: [   23.161477] PCIe: Link timeout on port 0, probably the slot is empty
Mon May 13 22:00:01 2019 kern.notice kernel: [   23.167779] PCIe: Initializing port 1
Mon May 13 22:00:01 2019 kern.notice kernel: [   23.174645] PCIe: BIST FAILED for port 1 (0xffffffffffffffff)
Mon May 13 22:00:01 2019 kern.notice kernel: [   25.185217] PCIe: Link timeout on port 1, probably the slot is empty
Mon May 13 22:00:01 2019 kern.notice kernel: [   25.197177] SCSI subsystem initialized
Mon May 13 22:00:01 2019 kern.info kernel: [   25.201073] usbcore: registered new interface driver usbfs
Mon May 13 22:00:01 2019 kern.info kernel: [   25.206471] usbcore: registered new interface driver hub
Mon May 13 22:00:01 2019 kern.info kernel: [   25.211754] usbcore: registered new device driver usb
Mon May 13 22:00:01 2019 kern.info kernel: [   25.216901] PCI host bridge to bus 0000:00
Mon May 13 22:00:01 2019 kern.info kernel: [   25.220842] pci_bus 0000:00: root bus resource [mem 0x1000000000000]
Mon May 13 22:00:01 2019 kern.info kernel: [   25.227176] pci_bus 0000:00: root bus resource [io  0x0000]
Mon May 13 22:00:01 2019 kern.info kernel: [   25.232744] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Mon May 13 22:00:01 2019 kern.info kernel: [   25.239522] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Mon May 13 22:00:01 2019 kern.debug kernel: [   25.247469] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
Mon May 13 22:00:01 2019 kern.info kernel: [   25.248161] clocksource: Switched to clocksource OCTEON_CVMCOUNT
Mon May 13 22:00:01 2019 kern.info kernel: [   25.254570] NET: Registered protocol family 2
Mon May 13 22:00:01 2019 kern.info kernel: [   25.259169] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.266155] TCP bind hash table entries: 8192 (order: 6, 262144 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.272741] TCP: Hash tables configured (established 8192 bind 8192)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.279008] UDP hash table entries: 512 (order: 3, 49152 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.284883] UDP-Lite hash table entries: 512 (order: 3, 49152 bytes)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.291340] NET: Registered protocol family 1
Mon May 13 22:00:01 2019 kern.debug kernel: [   25.295566] PCI: CLS 0 bytes, default 128
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.360626] Crashlog allocated RAM at address 0x3f00000
Mon May 13 22:00:01 2019 kern.info kernel: [   25.365976] workingset: timestamp_bits=62 max_order=18 bucket_order=0
Mon May 13 22:00:01 2019 kern.info kernel: [   25.376262] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Mon May 13 22:00:01 2019 kern.info kernel: [   25.382079] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Mon May 13 22:00:01 2019 kern.info kernel: [   25.393387] io scheduler noop registered
Mon May 13 22:00:01 2019 kern.info kernel: [   25.397177] io scheduler deadline registered (default)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.402685] octeon_gpio 1070000000800.gpio-controller: OCTEON GPIO driver probed.
Mon May 13 22:00:01 2019 kern.info kernel: [   25.410197] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Mon May 13 22:00:01 2019 kern.info kernel: [   25.416889] console [ttyS0] disabled
Mon May 13 22:00:01 2019 kern.info kernel: [   25.420343] 1180000000800.serial: ttyS0 at MMIO 0x1180000000800 (irq = 44, base_baud = 37500000) is a OCTEON
Mon May 13 22:00:01 2019 kern.info kernel: [   25.430147] console [ttyS0] enabled
Mon May 13 22:00:01 2019 kern.info kernel: [   25.437092] bootconsole [early0] disabled
Mon May 13 22:00:01 2019 kern.info kernel: [   25.445365] 1180000000c00.serial: ttyS1 at MMIO 0x1180000000c00 (irq = 45, base_baud = 37500000) is a OCTEON
Mon May 13 22:00:01 2019 kern.info kernel: [   25.455482] octeon_rng octeon_rng: Octeon Random Number Generator
Mon May 13 22:00:01 2019 kern.err kernel: [   25.461806] cacheinfo: Failed to find cpu0 device node
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.466971] cacheinfo: Unable to detect cache hierarchy for CPU 0
Mon May 13 22:00:01 2019 kern.info kernel: [   25.475568] loop: module loaded
Mon May 13 22:00:01 2019 kern.info kernel: [   25.479227] libphy: mdio_octeon: probed
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.483119] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@0: Whitelisted compatible string. Please remove
Mon May 13 22:00:01 2019 kern.info kernel: [   25.498674] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.508158] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@1: Whitelisted compatible string. Please remove
Mon May 13 22:00:01 2019 kern.info kernel: [   25.523280] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.532738] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@2: Whitelisted compatible string. Please remove
Mon May 13 22:00:01 2019 kern.info kernel: [   25.547851] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
Mon May 13 22:00:01 2019 kern.warn kernel: [   25.557304] [Firmware Warn]: /soc@0/mdio@1180000001800/ethernet-phy@3: Whitelisted compatible string. Please remove
Mon May 13 22:00:01 2019 kern.info kernel: [   25.572433] irq: :soc@0:gpio-controller@1070000000800 didn't like hwirq-0x7 to VIRQ48 mapping (rc=-22)
Mon May 13 22:00:01 2019 kern.info kernel: [   25.581865] mdio_octeon 1180000001800.mdio: Probed
Mon May 13 22:00:01 2019 kern.info kernel: [   25.586881] libphy: Fixed MDIO Bus: probed
Mon May 13 22:00:01 2019 kern.info kernel: [   25.591083] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Mon May 13 22:00:01 2019 kern.info kernel: [   25.597633] ehci-platform: EHCI generic platform driver
Mon May 13 22:00:01 2019 kern.info kernel: [   25.602952] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Mon May 13 22:00:01 2019 kern.info kernel: [   25.609165] ohci-platform: OHCI generic platform driver
Mon May 13 22:00:01 2019 kern.info kernel: [   25.614542] usbcore: registered new interface driver usb-storage
Mon May 13 22:00:01 2019 kern.info kernel: [   25.620603] octeon_wdt: Initial granularity 5 Sec
Mon May 13 22:00:01 2019 kern.warn kernel: [   26.533763] Interface 0 has 4 ports (SGMII)
Mon May 13 22:00:01 2019 kern.warn kernel: [   26.538025] Interface 1 has 4 ports (SGMII)
Mon May 13 22:00:01 2019 kern.warn kernel: [   26.542776] Interface 3 has 4 ports (LOOP)
Mon May 13 22:00:01 2019 kern.info kernel: [   26.552841] NET: Registered protocol family 10
Mon May 13 22:00:01 2019 kern.info kernel: [   26.559178] Segment Routing with IPv6
Mon May 13 22:00:01 2019 kern.info kernel: [   26.562942] NET: Registered protocol family 17
Mon May 13 22:00:01 2019 kern.info kernel: [   26.567436] 8021q: 802.1Q VLAN Support v1.8
Mon May 13 22:00:01 2019 kern.warn kernel: [   26.572382] OF: fdt: not creating '/sys/firmware/fdt': CRC check failed
Mon May 13 22:00:01 2019 kern.info kernel: [   26.582767] Freeing unused kernel memory: 8684K
Mon May 13 22:00:01 2019 kern.warn kernel: [   26.587325] This architecture does not have kernel memory protection.
Mon May 13 22:00:01 2019 user.info kernel: [   26.599313] init: Console is alive
Mon May 13 22:00:01 2019 user.info kernel: [   26.602926] init: - watchdog -
Mon May 13 22:00:01 2019 user.info kernel: [   26.610875] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Mon May 13 22:00:01 2019 user.info kernel: [   26.617875] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Mon May 13 22:00:01 2019 user.info kernel: [   26.626577] init: - preinit -
Mon May 13 22:00:01 2019 kern.notice kernel: [   26.707364] random: jshn: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 kern.notice kernel: [   26.733182] random: jshn: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 kern.notice kernel: [   26.752869] random: jshn: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 kern.info kernel: [   26.771818] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mon May 13 22:00:01 2019 user.info kernel: [   29.843525] procd: - early -
Mon May 13 22:00:01 2019 user.info kernel: [   29.846503] procd: - watchdog -
Mon May 13 22:00:01 2019 user.info kernel: [   30.395626] procd: - watchdog -
Mon May 13 22:00:01 2019 user.info kernel: [   30.398978] procd: - ubus -
Mon May 13 22:00:01 2019 kern.warn kernel: [   30.404457] urandom_read: 1 callbacks suppressed
Mon May 13 22:00:01 2019 kern.notice kernel: [   30.404462] random: ubusd: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 kern.notice kernel: [   30.451557] random: ubusd: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 kern.notice kernel: [   30.458100] random: ubusd: uninitialized urandom read (4 bytes read)
Mon May 13 22:00:01 2019 user.info kernel: [   30.464880] procd: - init -
Mon May 13 22:00:01 2019 user.info kernel: [   30.537801] kmodloader: loading kernel modules from /etc/modules.d/*
Mon May 13 22:00:01 2019 kern.info kernel: [   30.546877] ip6_tables: (C) 2000-2006 Netfilter Core Team
Mon May 13 22:00:01 2019 kern.info kernel: [   30.555212] ip_tables: (C) 2000-2006 Netfilter Core Team
Mon May 13 22:00:01 2019 kern.info kernel: [   30.563393] nf_conntrack version 0.5.0 (7680 buckets, 30720 max)
Mon May 13 22:00:01 2019 kern.info kernel: [   30.585430] xt_time: kernel timezone is -0000
Mon May 13 22:00:01 2019 kern.info kernel: [   30.593065] PPP generic driver version 2.4.2
Mon May 13 22:00:01 2019 kern.info kernel: [   30.598126] NET: Registered protocol family 24
Mon May 13 22:00:01 2019 user.info kernel: [   30.603840] kmodloader: done loading kernel modules from /etc/modules.d/*
Mon May 13 22:00:01 2019 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Mon May 13 22:00:01 2019 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: started, version 2.80 cachesize 150
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: DNS service limited to local subnets
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain test
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain onion
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain localhost
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain local
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain invalid
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain bind
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: using local addresses only for domain lan
Mon May 13 22:00:01 2019 daemon.warn dnsmasq[772]: no servers found in /tmp/resolv.conf.auto, will retry
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: read /etc/hosts - 4 addresses
Mon May 13 22:00:01 2019 daemon.info dnsmasq[772]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Mon May 13 22:00:05 2019 authpriv.info dropbear[809]: Not backgrounding
Mon May 13 22:00:05 2019 user.notice : Added device handler type: 8021ad
Mon May 13 22:00:05 2019 user.notice : Added device handler type: 8021q
Mon May 13 22:00:05 2019 user.notice : Added device handler type: macvlan
Mon May 13 22:00:05 2019 user.notice : Added device handler type: veth
Mon May 13 22:00:05 2019 user.notice : Added device handler type: bridge
Mon May 13 22:00:05 2019 user.notice : Added device handler type: Network device
Mon May 13 22:00:05 2019 user.notice : Added device handler type: tunnel
Mon May 13 22:00:06 2019 kern.info kernel: [   36.618012] br-lan: port 1(eth1) entered blocking state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.623299] br-lan: port 1(eth1) entered disabled state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.628753] device eth1 entered promiscuous mode
Mon May 13 22:00:06 2019 kern.info kernel: [   36.643406] br-lan: port 1(eth1) entered blocking state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.648675] br-lan: port 1(eth1) entered forwarding state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.654237] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'lan' is enabled
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'lan' is setting up now
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'lan' is now up
Mon May 13 22:00:06 2019 kern.info kernel: [   36.665342] br-lan: port 2(eth2) entered blocking state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.670628] br-lan: port 2(eth2) entered disabled state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.676099] device eth2 entered promiscuous mode
Mon May 13 22:00:06 2019 kern.info kernel: [   36.680845] br-lan: port 2(eth2) entered blocking state
Mon May 13 22:00:06 2019 kern.info kernel: [   36.686115] br-lan: port 2(eth2) entered forwarding state
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'loopback' is enabled
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'loopback' is setting up now
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'loopback' is now up
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'wan' is enabled
Mon May 13 22:00:06 2019 kern.info kernel: [   36.697040] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Mon May 13 22:00:06 2019 daemon.notice netifd: bridge 'br-lan' link is up
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'lan' has link connectivity
Mon May 13 22:00:06 2019 daemon.notice netifd: Network device 'lo' link is up
Mon May 13 22:00:06 2019 daemon.notice netifd: Interface 'loopback' has link connectivity
Mon May 13 22:00:06 2019 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/dhcp
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/network reload dependency on /etc/config/radvd
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/wireless reload dependency on /etc/config/network
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/luci-splash
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/qos
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/firewall reload dependency on /etc/config/miniupnpd
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/odhcpd
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/luci_statistics
Mon May 13 22:00:06 2019 user.notice ucitrack: Setting up /etc/config/system reload dependency on /etc/config/dhcp
Mon May 13 22:00:07 2019 daemon.info procd: - init complete -
Mon May 13 22:00:07 2019 kern.info kernel: [   37.628477] br-lan: port 1(eth1) entered disabled state
Mon May 13 22:00:07 2019 kern.info kernel: [   37.633974] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Mon May 13 22:00:07 2019 kern.info kernel: [   37.640998] br-lan: port 2(eth2) entered disabled state
Mon May 13 22:00:07 2019 daemon.err odhcpd[899]: Failed to send to ff02::1%lan@br-lan (Address not available)
Mon May 13 22:00:08 2019 daemon.notice netifd: bridge 'br-lan' link is down
Mon May 13 22:00:08 2019 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon May 13 22:00:09 2019 kern.notice kernel: [   40.196176] random: crng init done
Mon May 13 22:00:09 2019 kern.notice kernel: [   40.199595] random: 3 urandom warning(s) missed due to ratelimiting
Mon May 13 22:00:09 2019 daemon.info urandom_seed[1326]: Seed saved (/etc/urandom.seed)
Mon May 13 22:00:10 2019 daemon.info dnsmasq[772]: exiting on receipt of SIGTERM
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: started, version 2.80 cachesize 150
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: DNS service limited to local subnets
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Mon May 13 22:00:10 2019 daemon.info dnsmasq-dhcp[1413]: DHCP, IP range 10.10.10.100 -- 10.10.10.249, lease time 12h
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain test
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain onion
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain localhost
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain local
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain invalid
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain bind
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: using local addresses only for domain lan
Mon May 13 22:00:10 2019 daemon.warn dnsmasq[1413]: no servers found in /tmp/resolv.conf.auto, will retry
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: read /etc/hosts - 4 addresses
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon May 13 22:00:10 2019 daemon.info dnsmasq-dhcp[1413]: read /etc/ethers - 0 addresses
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: read /etc/hosts - 4 addresses
Mon May 13 22:00:10 2019 daemon.info dnsmasq[1413]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses
Mon May 13 22:00:10 2019 daemon.info dnsmasq-dhcp[1413]: read /etc/ethers - 0 addresses
Mon May 13 22:00:14 2019 kern.info kernel: [   45.297164] mmc1: new DDR MMC card at address 0001
Mon May 13 22:00:14 2019 kern.info kernel: [   45.302359] mmcblk1: mmc1:0001 P1XXXX 3.60 GiB
Mon May 13 22:00:14 2019 kern.info kernel: [   45.307042] mmcblk1boot0: mmc1:0001 P1XXXX partition 1 2.00 MiB
Mon May 13 22:00:14 2019 kern.info kernel: [   45.313095] mmcblk1boot1: mmc1:0001 P1XXXX partition 2 2.00 MiB
Mon May 13 22:00:14 2019 kern.info kernel: [   45.319145] mmcblk1rpmb: mmc1:0001 P1XXXX partition 3 128 KiB
Mon May 13 22:00:14 2019 kern.info kernel: [   45.325700]  mmcblk1: p1 p2 p3 p4
Mon May 13 22:00:56 2019 kern.notice kernel: [   86.890333] eth0: 1000 Mbps Full duplex, port 0, queue 0
Mon May 13 22:00:56 2019 kern.info kernel: [   86.895683] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mon May 13 22:00:56 2019 daemon.notice netifd: Network device 'eth0' link is up
Mon May 13 22:00:56 2019 daemon.notice netifd: Interface 'wan' has link connectivity
Mon May 13 22:00:56 2019 daemon.notice netifd: Interface 'wan' is setting up now
Mon May 13 22:00:56 2019 daemon.notice netifd: wan (1457): udhcpc: started, v1.30.1
Mon May 13 22:00:56 2019 daemon.notice netifd: wan (1457): udhcpc: sending discover
Mon May 13 22:00:56 2019 daemon.notice netifd: wan (1457): udhcpc: sending select for 192.168.0.19
Mon May 13 22:00:57 2019 daemon.notice netifd: wan (1457): udhcpc: lease of 192.168.0.19 obtained, lease time 3600
Mon May 13 22:00:57 2019 daemon.notice netifd: Interface 'wan' is now up
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: reading /tmp/resolv.conf.auto
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain test
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain onion
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain localhost
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain local
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain invalid
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain bind
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using local addresses only for domain lan
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using nameserver 209.18.47.63#53
Mon May 13 22:00:57 2019 daemon.info dnsmasq[1413]: using nameserver 209.18.47.62#53
Mon May 13 22:00:57 2019 user.notice firewall: Reloading firewall due to ifup of wan (eth0)
Mon May 13 22:08:57 2019 kern.notice kernel: [  105.290553] eth2: 1000 Mbps Full duplex, port 2, queue 2
Mon May 13 22:08:57 2019 kern.info kernel: [  105.295907] br-lan: port 2(eth2) entered blocking state
Mon May 13 22:08:57 2019 kern.info kernel: [  105.301157] br-lan: port 2(eth2) entered forwarding state
Mon May 13 22:08:57 2019 daemon.notice netifd: Network device 'eth2' link is up
Mon May 13 22:08:57 2019 daemon.notice netifd: bridge 'br-lan' link is up
Mon May 13 22:08:57 2019 daemon.notice netifd: Interface 'lan' has link connectivity
Mon May 13 22:08:59 2019 daemon.info dnsmasq-dhcp[1413]: DHCPREQUEST(br-lan) 192.168.1.198 ac:e2:d3:00:d4:df
Mon May 13 22:08:59 2019 daemon.info dnsmasq-dhcp[1413]: DHCPNAK(br-lan) 192.168.1.198 ac:e2:d3:00:d4:df wrong network
Mon May 13 22:09:02 2019 daemon.info dnsmasq-dhcp[1413]: DHCPDISCOVER(br-lan) ac:e2:d3:00:d4:df
Mon May 13 22:09:02 2019 daemon.info dnsmasq-dhcp[1413]: DHCPOFFER(br-lan) 10.10.10.198 ac:e2:d3:00:d4:df
Mon May 13 22:09:02 2019 daemon.info dnsmasq-dhcp[1413]: DHCPREQUEST(br-lan) 10.10.10.198 ac:e2:d3:00:d4:df
Mon May 13 22:09:02 2019 daemon.info dnsmasq-dhcp[1413]: DHCPACK(br-lan) 10.10.10.198 ac:e2:d3:00:d4:df gribbits
Mon May 13 22:09:53 2019 daemon.err uhttpd[985]: luci: accepted login on / for root from 10.10.10.198




If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1732.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: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Roadrunnere42
The SD card slot did work on mine, when i put an sd card in it booted into a version of the Shield which was a really early version, the sd card was blank at the time.
The speed issue, try commiting out the snort rules in sbin/fw_upgrade, this loads snort without any rules to slow it down.

Have you got the link to download your lastest build, and with instruction on how to load and i will have a play.

Which switch postion are you boot the shield in?

roadrunnere42

On Tue, 14 May 2019 at 20:56, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
I'm running into a performance issue and I'm not sure where it is coming from.  I really wish some of the folks who've dealt with the Shield for longer than the few months I've been playing with it would chime in :p

My throughput drops when going through the Shield by a factor of 10.  If I direct wire to my laptop, I'll pull 90-100MB/s down on Speedtest.  If I put that connection into the Eth0 and hook the Laptop up to Eth2, it drops to 10Mb/s.

I loaded Snort, but none of the configuration aside from the default because I've never used Snort before.  I'm going to remove Snort and see if that makes a difference, otherwise, I'll have to continue looking to see what the issue is.

So, if anyone wants to lend a hand in configuring, I'd be most appreciative.  I'm happy to put another image up and you can "test" configurations out on it, and if you find one that works well, you can send it to me and I'll pre-bake it into the image.  I know the Shield is "old", but if you look at the hardware, it's amazing.  Ubiquiti routers use the same architecture without nearly the amount of storage flash space.  This thing has FOUR Gigs of Flash ram, and even the biggest Itus image (router) was only 50mb.  It has 1GB ram, but I wonder if we could make a Swap partition to help pad that out some (On flash, I dunno).  At the very least, I figured out how to make the damn LED (labelled "M" on the front of the box) work with three colors.  I'm sure we can get the SD Card slot to work as well without too much trouble.


If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1734.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: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Turrican
Grommish and Roadrunnere42,

So happy you guys are still passionate about getting this little box singing.  Speed thoughput was always an issue for me, and others.

Following intently to see how you guys get on with this project!

Cheers

Running Bridge Mode
v1.51 SP1 + Hotfix Mar 9
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Roadrunnere42
It's been sometime since i did anything on the Shield, it's been rock solid for months, if my memory serves me the snort rules were download into and sorted in ram and only kept in ram to save mmc memory write.
Have not had time to install your image  and i agree the forum seems dead but every now and again someone appears.

Where about are you in the world? and i'm in the UK

On Wed, 15 May 2019 at 20:48, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
If you know anyone else who might be interested, point them this way!  The forums seem dead, but there have to be others out there who have the boxes, even if they don't use them.

And if your feeling adventurous, have a look at the image.  I am unfamiliar with programs like snort or iptables, but I can certainly build out.  I know someone was asking about PPPoE at one point and that is an available option in the source (if it isn't already built in).  The space we have to play with means we can really have everything we want and make it robust.

Zram swap is on, but I'm not sure I want to leave it in. Thinking on it, the mmc is a destructive write flash and using it as swap might cause premature failure.  Like using an SD card as swap.


If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1739.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: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Roadrunnere42
I did notice the case getting hot but thought it was normal because both of my shields are the same, still have not installed new image as i have had a family death and will be dealing with that for the next few weeks.
Keep up the good work.

Roadrunnere42

On Sun, 19 May 2019 at 16:34, Grommish [via Itus Networks Owners Forum] <[hidden email]> wrote:
It's been a few days since I've built out the source, and something positive has come from it!

I've been looking at the Shield and noticed (like many of you, I'm sure) just how bleepin' hot the case gets.  I decided to tear the thing apart and see just what was going on.

Itus really did a number on things in there in an effort to "look slick" (I guess).  the bare Octeon chip and "foam" bumper really underwhelmed me, especially since I'm not really sure that foam will do much more than trap heat against the chip - there certainly wasn't thermal tape or conductivity gel between the foam and the chip.

I noticed there was a 3-pin stub-out, and that I see 5.5v from it.  So, I ordered a 30x30x10mm 5v 3pin fan and I'm going to try and mount it externally in a push configuration over the vent holes.  I'll report back on that when I get it done.

In the mean time, I left the case open and running because, well, I'm lazy.

With the case off, and no changes to the software, I'm now seeing full throughput on the Shield.  I'm pulling 92Mb/S on the WAN, and seeing 92Mb/s on the LAN!  I really am convinced the pisspoor thermal design is causing the chipsets to throttle.

I'll keep playing with it, but the speed throughput issues have gone away since I took the cover off.


If you reply to this email, your message will be added to the discussion below:
http://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1743.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: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
Reply | Threaded
Open this post in threaded view
|

Re: [FIRMWARE] Itus Networks Shield Firmware Upgrade *WIP*

Grommish
This post was updated on .
CONTENTS DELETED
The author has deleted this message.
Running Itus Shield v2 Firmware
1234