Iopsys EG400 - possible to run up to date OpenWrt?

Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.497000] Cross Bar MUX Config : Internal Port 01 maps to External Port 02 <reg_val : 0x00000014>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.498000] Cross Bar MUX Config : Internal Port 02 maps to External Port 00 <reg_val : 0x00000014>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.499000] Cross Bar MUX Config : Internal Port 02 maps to External Port 00 <reg_val : 0x00000014>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.502000] GPIO 36 is assigned to Serdes Fiber Signal Detection.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.504000] Setting SGMII Calibration value to 0xb
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.509000] Energy detection is used as SFP module insertion detection
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.510000] Broadcom BCM63139B0 Ethernet Network Device v0.1 Feb 20 2018 11:47:35
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.513000] dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.514000] ++++ disabling GSO on logical_port=0 dev=eth0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.516000] eth0: <Int sw port: 0> <Logical : 00> PHY_ID <0x06180006 : 0x06> MAC : 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.518000] eth1: <Ext sw port: 0> <Logical : 08> PHY_ID <0x0007f008 : 0x08> MAC : 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.520000] eth2: <Ext sw port: 1> <Logical : 09> PHY_ID <0x0007f009 : 0x09> MAC : 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.522000] eth3: <Ext sw port: 2> <Logical : 10> PHY_ID <0x0007f00a : 0x0a> MAC : 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.524000] eth4: <Ext sw port: 3> <Logical : 11> PHY_ID <0x0007f00b : 0x0b> MAC : 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.527000] Ethernet Auto Power Down and Sleep: Enabled
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.528000] Cross bar port 1 of Int switch port 0; Adv capability change : MII=0x01e1, GMII=0x0f00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.530000] Ext switch port 0; Adv capability change : MII=0x01e1, GMII=0x0f00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.531000] Ext switch port 1; Adv capability change : MII=0x01e1, GMII=0x0f00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.532000] Ext switch port 2; Adv capability change : MII=0x01e1, GMII=0x0f00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.534000] Cross bar port 4 of Ext switch port 3; Adv capability change : MII=0x01e1, GMII=0x0f00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.536000] All Port Bit Map: 0x0f01: eth0,eth1,eth2,eth3,eth4
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.537000]    Chip WAN Only Ports 0001, Defined WAN Only Ports 0000, WAN Only Port Result: 0x0001:eth0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.538000]    Chip WAN Preffered Ports 0000, Defined WAN Preffered Ports 0000, WAN Preffered Port Result: 0x0000:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.539000]    Chip LAN Only Ports 0f00, Defined LAN Only Ports 0000, LAN Only Port Result: 0x0f00:eth1,eth2,eth3,eth4
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.540000]    WAN/LAN Both Capable Ports 0x0000:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.541000] Creating Enet CPU ring for queue number 1 with 512 packets,Descriptor base=ffdec000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.541000]  Creating Enet CPU ring for queue number 0 with 512 packets,Descriptor base=ffde8000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.542000]  ===> Activate Deep Green Mode
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.559000] Initialized Runner Host Layer
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.560000] Initialized Runner Unicast Layer
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.561000] Initialized Runner L2 Unicast Layer
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.562000] Initialized Runner Multicast Layer
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.565000] Broadcom Packet Flow Cache HW acceleration enabled.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.567000] Enabled Runner binding to Flow Cache
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.571000] Initialized Runner Protocol Layer (700)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.573000] Broadcom Runner Blog Driver Char Driver v0.1 Feb 20 2018 11:47:20 Registered <252>
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.606000] NComm TMS V6.80 Kernel Module loaded.
Thu Sep  6 16:31:29 2018 kern.debug kernel: [    4.630000] libata version 3.00 loaded.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.644000] ++++ Powering up SATA block
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.650000] writing PORT0_SATA3_PCB_BLOCK_ADDR
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    4.655000] INFO: PLL lock for port0 detected 9100...
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.672000] ahci: SSS flag set, parallel bus scan disabled
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.684000] ahci strict-ahci.0: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.685000] ahci strict-ahci.0: flags: 64bit ncq sntf stag clo pmp slum part 
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.687000] scsi0 : ahci_platform
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.688000] ata1: SATA max UDMA/133 mmio [mem 0x8000a000-0x8000bfff] port 0x100 irq 77
Thu Sep  6 16:31:29 2018 kern.info kernel: [    4.994000] ata1: SATA link down (SStatus 0 SControl 300)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.007000] Wifi Forwarding Driver is initialized!
Thu Sep  6 16:31:29 2018 kern.info kernel: [    5.016000] Initializing WLCSM Module
Thu Sep  6 16:31:29 2018 kern.info kernel: [    5.017000] WLCSM Module loaded successfully 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.103000] DHD_FKB_POOL size is:1280 and entry size:2592
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.105000] fkbpool address range: d8800000 <-> d8b2a000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.106000] DHD_PKTTAG POOL size is:1280 and entry size:64
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.107000] dhd_module_init in
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.108000] dhd_queue_budget = 256
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.109000] dhd_sta_threshold = 2048
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.110000] dhd_if_threshold = 65536
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.111000] no wifi platform data, skip
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.112000] dhdpcie_chipmatch: Unsupported vendor 14e4 device a8db
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.113000] dhdpcie_pci_probe: chipmatch failed!!
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.114000] PCI_PROBE:  bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.115000] dhdpcie_init: can't find adapter info for this chip
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.116000] PCI: enabling device 0001:01:00.0 (0140 -> 0142)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.234000] DHD: dongle ram size is set to 1835008(orig 1835008) at 0x200000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.235000] dhd:0: fw path:/etc/wlan/dhd nv path:(null)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.236000] Creating CPU ring for queue number 7 with 128 packets descriptor=0xbf128134
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.236000]  Done initializing Ring 7 Base=0xffdfe000 End=0xffdfe800 calculated entries= 128 RDD Base=0x00c17000 descriptor=0xbf128134
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.238000] RDPA returned tx wakeup reg = <0x80299004>, val = <0x10000000>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.239000] RDPA returned rx wakeup reg = <0x8029a004>, val = <0x26000000>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.240000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.241000] dhd_runner_attach: Rx Offload - Enabled, Ring Size = 1024
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.246000] dhd_attach: wl0: pre-allocated buffer mode is disabled (allocskbsz=0)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.247000] dhd_attach(): thread:dhd_watchdog_thread:1d8 started
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.248000] dhd_attach(): thread:dhd0_dpc:1d9 started
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.249000] dhd_deferred_work_init: work queue initialized 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.250000] Creating CPU ring for queue number 0 with 1024 packets descriptor=0xbf2b4844
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.250000]  Creating CPU ring for queue number 1 with 1024 packets descriptor=0xbf2b4860
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.251000]   wfd_bind: Dev wl%d wfd_idx 0 wl_radio_idx 0 Type fkb configured WFD thread wfd0-thrd minQId/maxQId (8/9), status (0) qmask 0x3
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.252000] Instantiating WFD 0 thread
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.253000] dhd:0: fw path:/etc/wlan/dhd nv path:(null)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.254000] dhd_bus_download_firmware: firmware path=/etc/wlan/dhd, nvram path=
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.256000] dhdpcie_ramsize_adj: Enter
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.261000] dhdpcie_ramsize_adj: Adjust dongle RAMSIZE to 0x240000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.262000] dhdpcie_download_code_file: download firmware /etc/wlan/dhd/4366c0/rtecdc.bin
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.743000] wl:srom/otp not programmed, using main memory mapped srom info(wombo board)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.744000] wl: ID=pci/1/1/0/
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.746000] wl: loading /etc/wlan/bcm43664_EG400R0_map.bin
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.747000] wl: updating srom from flash...
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.755000] wl: reading /etc/wlan/bcmcmn_nvramvars.bin, file size=20
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.757000] wl: reading /etc/wlan/bcm43664_nvramvars.bin, file size=20
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.757000] Replace or append with internal Mac Address
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.762000] dhdpcie_bus_write_vars: Download, Upload and compare of NVRAM succeeded.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.958000] PCIe shared addr (0x002a6e5c) read took 195023 usec before dongle is ready
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.959000] DMA RX offset from shared Area 0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.960000] dhdpcie_readshared: Dongle advertizes 2 size indices
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.961000] dhdpcie_readshared: Host support DMAing indices: H2D:1 - D2H:1. FW supports it
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.962000] H2D DMA WR INDX : array size 544 = 2 * 266
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.963000] D2H DMA RD INDX : array size 32 = 2 * 3
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.964000] D2H DMA WR INDX : array size 32 = 2 * 3
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.965000] H2D DMA RD INDX : array size 544 = 2 * 266
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.966000] ring_info_raw: 56 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.967000] e0 6a 43 00 b0 7b 43 00 c4 7d 43 00 d8 7f 43 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.972000] de 7f 43 00 00 00 00 00 00 00 00 00 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.977000] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.982000] 00 00 00 00 0a 01 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.985000] dhdpcie_readshared: max H2D queues 266
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.986000] dhd_bus_start: Initializing 266 h2drings
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.987000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.988000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.989000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.990000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.991000] dhd_runner_profile_init: N+M profile = 3 01:1024 -1:2048 -1:1024 -1:0512 01:0512
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.992000] Scratch pad is not initialized.
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    5.993000] dhd_runner_policy_init: N+M Policy = 0 1 (HW)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.037000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.038000]   0000: 00 a0 c8 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.039000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.040000]   0000: 00 00 c2 00 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.041000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.042000]   0000: 00 80 d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.043000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.044000]   0000: 00 c0 d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.045000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.046000]   0000: 00 80 c2 00 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.047000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.048000]   0000: 00 00 e0 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.049000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.050000]   0000: 00 10 14 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.051000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.052000]   0000: 00 48 d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.053000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.054000]   0000: 00 4c d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.055000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.056000]   0000: 00 40 d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.057000] dhd_bus_cmn_writeshared:
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.058000]   0000: 00 44 d3 18 00 00 00 00 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.059000] Attach flowrings pool for 264 rings
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.060000] Runner DHD PCIE: vendor<0x14e4> device<0x4365> bus<1> slot<0>
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.061000] Initial configuration
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.062000] =================================
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.063000] 	rx_post_flow_ring_base_addr : c0c20000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.064000] 	tx_post_flow_ring_base_addr : 0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.065000] 	rx_complete_flow_ring_base_addr : c0c28000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.066000] 	tx_complete_flow_ring_base_addr : 0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.067000] 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.068000] 	r2d_wr_arr_base_addr : ffde0000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.069000] 	d2r_rd_arr_base_addr : ffde0402
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.070000] 	r2d_rd_arr_base_addr : ffde0c00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.071000] 	d2r_wr_arr_base_addr : ffde0802
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.072000] 	tx_post_mgmt_arr_base_addr : ffde1000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.073000] 	tx_post_mgmt_arr_base_phys_addr : 18d35000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.074000] 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.075000] 	r2d_wr_arr_base_phys_addr : 18d34000
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.076000] 	d2r_rd_arr_base_phys_addr : 18d34402
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.077000] 	r2d_rd_arr_base_phys_addr : 18d34c00
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.078000] 	d2r_wr_arr_base_phys_addr : 18d34802
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.079000] 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.080000] 	Doorbell ISR : bf2de190
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.081000] 	Doorbell CTX : d8c1c600
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.082000] Runner DHD Offload initialization complete
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.085000] dhd_rx_frame: net device is NOT registered. drop event packet
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.091000] dhd_rx_frame: net device is NOT registered. drop event packet
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.098000] CUR_ETHERADDR : 6 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.101000] 00 22 07 72 85 4d 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.104000] dhd_sync_with_dongle: GET_REVINFO device 0x43c5, vendor 0x14e4, chipnum 0xaa90
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.114000] 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.114000] Dongle Host Driver, version 7.14.164.20.cpe4.16L05.0-kdb
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.124000] wfd_registerdevice Successfully registered dev wl0 ifidx 0 wfd_idx 0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.131000] Broadcom PCI Device 0x6313 has allocated with driver pcieport
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.138000] Broadcom PCI Device 0x6313 has allocated with driver pcieport
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.145000] dhd_module_init out
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.796000] --SMP support
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.798000] wl: dsl_tx_pkt_flush_len=338
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.802000] wl: norm_wmark_tot=20194, pktc_wmark_tot=20194
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.808000] PCI: enabling device 0000:01:00.0 (0140 -> 0142)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.813000] wl: passivemode=1
Thu Sep  6 16:31:29 2018 kern.info kernel: [    6.816000] wl1: creating kthread wl1-kthrd
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.827000] wl: napimode=0
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.843000] initvars_cis_pci: Not CIS format
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.847000] Neither SPROM nor OTP has valid image
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.852000] wl:srom/otp not programmed, using main memory mapped srom info(wombo board)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.860000] wl: ID=pci/0/1/0/
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.864000] wl: ID=pci/0/1/0/
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.867000] wl: loading /etc/wlan/bcm43217_map.bin
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.872000] srom rev:8
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.876000] wl: reading /etc/wlan/bcmcmn_nvramvars.bin, file size=20
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.906000] wl1: allocskbmode=1 currallocskbsz=2300
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.915000] Creating CPU ring for queue number 2 with 1024 packets descriptor=0xbf2b487c
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.915000]  Creating CPU ring for queue number 3 with 1024 packets descriptor=0xbf2b4898
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.925000]   wfd_bind: Dev wl%d wfd_idx 1 wl_radio_idx 1 Type skb configured WFD thread wfd1-thrd minQId/maxQId (10/11), status (0) qmask 0xc
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.946000] Instantiating WFD 1 thread
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.951000] wfd_registerdevice Successfully registered dev wl1 ifidx 0 wfd_idx 1
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.958000] wl1: Broadcom BCM43227 802.11 Wireless Controller 7.14.164.20.cpe4.16L05.0-kdb
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.966000] dgasp: kerSysRegisterDyingGaspHandler: wl1 registered 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.979000] Loading DECT Shim driver 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.982000] Initialize DECT Shim layer....
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.986000] Obtained board id string (Si32260_LCQC)
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    6.991000] Obtained Base board id string (EG400R0)Successfully obtained voice parameters
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.000000] DECT is disabled by OTP/boardparms or is initialized already
Thu Sep  6 16:31:29 2018 kern.notice kernel: [    7.011000] Loading PCM shim driver
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.319000] Endpoint: endpoint_init entry
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.322000] ---------- Voice board configuration ----------
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.328000] Number of FXS lines          =  2
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.332000] Number of FXO lines          =  0
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.337000] Number of DECT lines         =  4
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.341000] Number of failover relay pins=  1
Thu Sep  6 16:31:29 2018 kern.alert kernel: [    7.346000] ---------- 
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.348000] Endpoint: endpoint_init COMPLETED
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.362000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.374000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.383000] ++++ Powering up USB blocks
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.711000] ehci-platform ehci-platform.0: Generic Platform EHCI Controller
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.718000] ehci-platform ehci-platform.0: new USB bus registered, assigned bus number 1
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.726000] ehci-platform ehci-platform.0: irq 105, io mem 0x8000c300
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.739000] ehci-platform ehci-platform.0: USB 2.0 started, EHCI 1.00
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.745000] hub 1-0:1.0: USB hub found
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.748000] hub 1-0:1.0: 2 ports detected
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.753000] ohci-platform ohci-platform.0: Generic Platform OHCI Controller
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.760000] ohci-platform ohci-platform.0: new USB bus registered, assigned bus number 2
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.768000] ohci-platform ohci-platform.0: irq 104, io mem 0x8000c400
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.830000] hub 2-0:1.0: USB hub found
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.833000] hub 2-0:1.0: 2 ports detected
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.841000] usbcore: registered new interface driver usblp
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.856000] Initializing USB Mass Storage driver...
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.860000] usbcore: registered new interface driver usb-storage
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.866000] USB Mass Storage support registered.
Thu Sep  6 16:31:29 2018 kern.info kernel: [    7.889000] Broadcom 802.1Q VLAN Interface, v0.1
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.902000] BRCM TRNG registered
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.909000] brcm_otp_init entry
Thu Sep  6 16:31:29 2018 kern.warn kernel: [    7.922000] RDPA DS WAN UDP Filter Command Driver
Thu Sep  6 16:31:29 2018 kern.info kernel: [   11.306000] procd: - early -
Thu Sep  6 16:31:29 2018 kern.info kernel: [   11.846000] procd: - ubus -
Thu Sep  6 16:31:29 2018 kern.info kernel: [   12.850000] procd: - init -
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.133000] Custom GPIO-based I2C driver version 0.1.1
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.136000] i2c-gpio i2c-gpio.1: using pins 24 (SDA) and 25 (SCL)
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.197000] Bluetooth: Core ver 2.20
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.201000] NET: Registered protocol family 31
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.205000] Bluetooth: HCI device and connection manager initialized
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.212000] Bluetooth: HCI socket layer initialized
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.217000] Bluetooth: L2CAP socket layer initialized
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.222000] Bluetooth: SCO socket layer initialized
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.231000] Bluetooth: RFCOMM socket layer initialized
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.236000] Bluetooth: RFCOMM ver 1.11
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.242000] usbcore: registered new interface driver btusb
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.252000] usbcore: registered new interface driver cdc_ether
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.259000] usbcore: registered new interface driver cdc_eem
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.266000] usbcore: registered new interface driver cdc_ncm
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.272000] usbcore: registered new interface driver cdc_wdm
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.278000] usbcore: registered new interface driver cdc_mbim
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.286000] usbcore: registered new interface driver asix
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.291000] usbcore: registered new interface driver kalmia
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.298000] usbcore: registered new interface driver rndis_host
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.306000] usbcore: registered new interface driver qmi_wwan
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.313000] ip_tables: (C) 2000-2006 Netfilter Core Team
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.320000] Netfilter messages via NETLINK v0.30.
Thu Sep  6 16:31:29 2018 kern.notice kernel: [   15.327000] ip_set: protocol 6
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.366000] nf_conntrack version 0.5.0 (7561 buckets, 30244 max)
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.382000] gre: GRE over IPv4 demultiplexor driver
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.389000] ip_gre: GRE over IPv4 tunneling driver
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.441000] xt_time: kernel timezone is -0000
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.449000] ip6_tables: (C) 2000-2006 Netfilter Core Team
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.461000] PPTP driver version 0.8.5
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.465000] usbcore: registered new interface driver qcaux
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.467000] USB Serial support registered for qcaux
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.470000] usbcore: registered new interface driver qcserial
Thu Sep  6 16:31:29 2018 kern.info kernel: [   15.477000] USB Serial support registered for Qualcomm USB modem
Thu Sep  6 16:31:29 2018 kern.notice kernel: [   15.480000] Registering the dns_resolver key type
Thu Sep  6 16:31:29 2018 kern.warn kernel: [   16.968000] DFS_SW_VERSION=002.003. DDMMYYYY=10122011
Thu Sep  6 16:31:29 2018 kern.warn kernel: [   17.363000] Software Version: EG400-WU21U_GET3.14.0-180220_1313
Thu Sep  6 16:31:30 2018 kern.warn kernel: [   19.573000] wait instruction: disabled
Thu Sep  6 16:31:30 2018 kern.warn kernel: [   19.597000] Ethernet Auto Power Down and Sleep: Disabled
Thu Sep  6 16:31:30 2018 user.info syslog: brcmnetlink daemon starting up
Thu Sep  6 16:31:30 2018 user.emerg syslog: Powered up 
Thu Sep  6 16:31:30 2018 user.notice /sbin/imonitor[2920]: Band Steering is deactivated; will be re-activated when both 2.4GHz and 5GHz radios are enabled.
Thu Sep  6 16:31:30 2018 user.emerg syslog: Success
Thu Sep  6 16:31:30 2018 user.emerg syslog: Powered up 
Thu Sep  6 16:31:30 2018 user.emerg syslog: Success
Thu Sep  6 16:31:30 2018 user.emerg syslog: Powered up 
Thu Sep  6 16:31:30 2018 user.emerg syslog: Success
Thu Sep  6 16:31:30 2018 user.emerg syslog: Powered up 
Thu Sep  6 16:31:31 2018 user.emerg syslog: Success
Thu Sep  6 16:31:31 2018 user.emerg syslog: Powered up 
Thu Sep  6 16:31:31 2018 user.emerg syslog: Success
Thu Sep  6 16:31:31 2018 user.emerg syslog: Command failed: Not found

If you use the </> button in the editor, you can make the "code" a lot more readable.

Now you just need to find a dev familiar with the components of your device and convince them to help. You'll likely need to help them if they get to the point of being able to "try" a new build.

@ZorgX As Jeff already mentioned:
Please use "Preformatted text </>" for logs, scripts, configs and general console output.
grafik

I did this now for you. In the future, please take the time for this formatting.

sure, no problem :slight_smile: i have two and i can accsess the recoverymenu even after bad flash :slight_smile:

Hey, i try to make one with the builder from iopsys, and i make a image with LEDE reboot

BusyBox v1.27.2 () built-in shell (ash)

   ________  ___  ______  ______
  /  _/ __ \/ _ \/ __/\ \/ / __/
 _/ // /_/ / ___/\ \   \  /\ \  
/___/\____/_/  /___/   /_/___/  

IOP Version: EG400-X-INT-4.2.0BETA1-181210_1329
LEDE Base: Reboot (SNAPSHOT, r6281+1-afa4d51deb)

Is it hard to update this to the last openwrt ?

root@Inteno:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 10000000 00020000 "brcmnand.0"
mtd1: 004e0000 00020000 "kernel_0"
mtd2: 004e0000 00020000 "kernel_1"
mtd3: 00060000 00020000 "nvram2"
mtd4: 00020000 00020000 "nvram"
mtd5: 0f480000 00020000 "ubi"
mtd6: 00040000 00020000 "cfe_extend"
mtd7: 073c4000 0001f000 "rootfs_0"
mtd8: 073e3000 0001f000 "rootfs_1"

I was also able to install Luci at "parallell" with juci but the loginscreen didnt work for some rison .. maybe just me that need to aktivate more stuff in the builder hehe

Is it posible to make a build file with this builder and run it with a openwrt builder so i can get all the latest updates and i can use the drivers and stuff from Iopsys ?

How feeds work

The OpenWRT build system contains several core packages but can be
extended and modified by using feeds. Feeds are repositories that
contain package Makefiles, i.e. descriptions on where to find the
source code for a package and how to build an OpenWRT package from
it. Feeds are defined in feeds.conf file in TOPDIR. The layout for
the dectmngr package is shown below. That is the feeds.conf contains a
reference to a feeds git repo and a commit, then in that feed the
dectmngr git repo and commit id is specified.

feeds.conf #commit -> feeds/intenopackages/dectmngr/Makefile #commit -> dectmngr.git

feeds.conf:
src-git-full intenopackages git@iopsys.inteno.se:inteno-packages.git^e0bb62451d8b2030d84191732b42a0d3064b1c5f

feeds/intenopackages/dectmngr/Makefile:
PKG_SOURCE_URL:=http://ihgsp.inteno.se/git/dectmngr.git
PKG_SOURCE_VERSION:=6ba403663bc9cfdb8f89fb34de367f0796d68552

While the OpenWRT build system supports branch names in feeds.conf, in
Iopsys we only use commit id:s. This ensures that we can always
recreate a build at a later date by checking out a specific commit in
the top level repository.


Iopsys initialization

After cloning the repository the iop command needs to be initialized
to install the commands for this version of iopsys.

Running iop without arguments gives the following output:

./iop
Usage: iop []

Avaliable commands:
bootstrap Initial command to run to install other commands
setup_host Install needed packets to host machine

As can be seen, there is only two command avaliable. First you need to
install everything needed to your host with.

./iop setup_host

This will only work on debian based distroes. ex ubuntu. not on
fedora.

After the host is setup openwrt build needs to be populated with
packages to build. Run this to install more commands from feeds:

./iop bootstrap

When bootstrap completes you should have more commands avaliable (some
commands can differ for your version):

./iop
Usage: iop []

Avaliable commands:
bootstrap Initial command to run to install other commands
feeds_update Update feeds to point to commit hashes from feeds.conf
genconfig Genereate configuration for board and customer
generate_tarballs Generate tarballs for openstk
setup_host Install needed packages to host machine
status Display the state of your working tree
update_package Publish changes to packages and feeds

Next, all feed repositories need to be cloned and packages
installed. This is handled by running:

iop feeds_update

This clones all feed repositories into feeds/ and installs the
packages from those repositories into the build system by creating
symlinks in packages/feeds/.

NOTE. iop bootstrap only needs to be run once to install the commands
above. After you have installed feeds_update, running that command
will update iop commands along with all other packages.

Now, generate a .config file for the board and customer you're
building for with

iop genconfig

To summarize, to intialize the repository, run:

git clone
iop bootstrap
iop feeds_update
iop genconfig

If it's the first time you're building an image on your host, you
should run:

iop setup_host

to install the required packages on your
host machine. After that run:

make

alt: for parallel build.
make download
make -j8

Updating the repository

If you run git pull in the toplevel repository you will most probably
get changes that modify feeds.conf. Now your feeds.conf points to
newer commits then what is checked out in the feed repositories and
you need to update your feeds. Do this by running:

iop feeds_update

This will pull in the latest changes in the modified feed for you. To
summarize, to update your repository, run:

git pull
iop feeds_update
make


Working with feeds

The build system will clone and checkout the packages in build_dir in
detached head state so before you can commit you need to checkout a
branch to work on. To prevent an invalid state where you update
feeds.conf with commits that are not pushed to the remote repository,
the script pushes the new commits to the remote repos. For this to
work the script needs to know what remote branches to push to. For
that reason, always make sure to check out remote tracking branches,
for example with git checkout -t origin/mybranch.

When you have created a new commit in the package repo in the build
directory this commit needs to be pushed to two places. First the
package makefile in the feed needs to be repointed to the new
commit. This in turn creates a new commit in the feed and feeds.conf
needs to be repointed to that commit.

First you need to set the EDITOR environmental variable to your
favorite editor. Ex:

export EDITOR=/usr/bin/emacs

You probably want to add this line to your .bashrc.

iop update_package

First, it will update the toplevel remote repository and abort if it
finds that you are not on the last commit on the branch you're working
on. If you get this complaint, just merge the remote branch into your
local branch. This step is kept manual to ensure that you know that
your repository changes.

If you are on the end of your branch the script continues and checks
if any git repo in the build differs from the commit in the package
makefile. If it finds a diff it first asks you what branch to make the
new commit on since you are in detached head state in the feed
repository. You probably want to select devel here. Once you have
selected a branch to update the script autogenerates a commit message
from the commits between the old and the new commit point of the
package. The same then happens for the commit on feeds.conf

Source: https://github.com/unofficial-inteno-public-mirror/iopsys-barrier-breaker

The builders looks kind of the same like bast on the same stuff .. so.. any good ides on how i can build a image with two bilders ? is it easyes to just build with bouth and edit the folders inside of the builder or is it best to edit the bilder it self ? is it any "autoapps for this ?"

Or is it better to make a "wanilla" image in the iopsys builder and after that install all the package i want ant use opkg-upgrade for autoupdating all ?

Not sure if there’s still any real interest for this device.

Poking around, it’s actually pretty good hardware and it can easily route at 1gbps speeds. Only thing holding it down is IMO the locked down carrier firmware.

I’ve dismantled and researched this device and I’ve made quite some progress.

Main findings/results so far:

  • serial pinout
  • original firmware-image binary dump (via serial and cfedump util)
  • fully extracted filesystem from firmware-image, including /etc
  • isp and vendor specific URLs for updates/unlocked firmware

I’m working on breaking the default passwords so that it can be fully accessed without needing a root exploit or serial.

The most important results so far can be found in this wiki page I’ve started:

If anyone else is interested in working with the device, so let me know!

1 Like

As a status update, I entered the debricking/firmware-recovery mode (as outlined in the wiki-link above), and tried installing the latest, unlocked factory firmware for this device (as obtained through the "secret" links contained in the extracted ISP-firmware).

My idea was that I could flash this to one bank with a known admin-login, and use that to extract more details from the other firmware bank.

Observing the console log though, after successful first boot, the next thing it did was overwrite the other bank too :grinning_face_with_smiling_eyes:

That means flashing latest unlocked default image to one bank, also deletes whatever carrier-specific settings you have on the other bank!

For those who think that still sounds interesting... I now have a completely blank device with default credentials and a more recent IOPSys version:

System Status

Hostname: iopsys
Model: EG400
Serial No: EG4024Hxxxxxxxxx
MAC Address: 44:D4:37:44:xx:xx
Filesystem: UBIFS
Firmware Version: EG400-X-IOPSYS-4.3.5-201023_1113
Other Bank: EG400-X-IOPSYS-4.3.5-201023_1113
Kernel Version: 4.1.38
BSP Version: consumer
CFE Version: 1.0.38-161.189-IOP1.5

So Iopsys is bumped from 3.1 to 4.3 and kernel from 3.4 to 4.1. That's a fairly good upgrade at very low risk IMO!

Login in at the webinterface (http://192.168.1.1) with admin/admin, I can also add an ssh-key for root access, and have full access to the device via SSH.

$ ssh root@192.168.1.1


BusyBox v1.27.2 () built-in shell (ash)

   ________  ___  ______  ______
  /  _/ __ \/ _ \/ __/\ \/ / __/
 _/ // /_/ / ___/\ \   \  /\ \  
/___/\____/_/  /___/   /_/___/  

IOP Version: EG400-X-IOPSYS-4.3.5-201023_1113
LEDE Base: Reboot (SNAPSHOT, r0+7677-22c4faa7fa)
------------------------------------
root@iopsys:~# 

Opkg still refers to LEDE snapshots and doesn't work OOB though:

root@iopsys:~# opkg update
Downloading http://downloads.lede-project.org/snapshots/targets/iopsys-brcm63xx-arm/generic/packages/Packages.gz

It's not OpenWRT, but it's much better than the ISP-locked down unit it used to be. Mission accomplished?

For those interested in doing the same thing to their EG400, I've uploaded a copy of the unlocked firmware I used here:

MD5 checksum: 22d7894c9378985f9494c0c4556375a6

1 Like

I have a ISP supplied unused EG400 which I had no use for due to it's limitations. Before updating I'm curious as to what I could expect as I have no prior knowledge of iopsys.

I would like to use the EG400 as an AP with a trunk port and 5 different SSID on different VLANs. If it might be possible I'll go ahead and update. If you already know that such advanced features won't be possible on iopsys I would apprecate a warning so I don't kill it's value for no reason.

Nice work btw.

Iopsys is sort of like OpenWRT (a fork), but designed to be operated/operatable remotely by service-providers.

This is done via protocols and services which can be disabled with admin-access.

Once those are off, Iopsys is pretty much like an inferior OpenWRT with a different JS-powered GUI (Juci).

Notable differences (for this device at least):

  • much more sophisticated WiFi settings than OOB OpenWRT
  • built on a older OpenWRT base.
  • don’t expect to get Opkg in a usable state. You have what you have. Deal :slight_smile:

That said. You’ll find most of the things where you expect them to. Either in the GUI or in /etc/config.

The network management in general is clearly VLAN-capable (my isp used 4 in its default config), but I haven’t tried applying this to WiFi. Worst case scenario, try ifname.vlanid notation?

That said i haven’t tried a setup like yours.

Give it a shot and see if it works?

Because I’m a stubborn idiot, I went looking at the Iopsyswrt source to see if there’s more to be had here.

Findings:

  • latest iopsyswrt is v6.4
  • there’s a branch where iopsys is rebased on OpenWRT 21.02.1

My hope was that I could build that for the EG400 and pioint opkg to the 21.02 package repo to extend the usefulness of the device (with obvious disclaimers about packages requiring kernel-modules).

Unfortunately I found support for the EG400 is discontinued at this point.

Going back in time I found the commit where EG400 support was removed, and checked out the revision before that (commit e60775621aad71f7f32d5878d561a80c9fac211c,
Author: Jani Juvan jani.juvan@iopsys.eu,
Date: Fri Nov 20 13:35:25 2020 +0100), hoping that would be more recent and still build.

Even after quite a bit of muscling with the build-system, something still failed the build and I gave up.

But at this point it was trying to build a 4.1 kernel which seems somewhat close to the image we already have.

So I checked the package sources for Iopsyswrt at this point in time, and they seem based on OpenWRT 19.06!

Maybe tweaking opkg to the right 19.06 repo might work for this build too? :slight_smile:

If nobody else beats me to it, I will give it a try myself one of the upcoming days!

Exciting stuff!

Hi @josteink,

Great work! I successfully flashed my EG400 with the image you provided. I was hoping for the possibility to set up a guest WiFi with it (disabled in the ISP's version). Unfortunately, the fiber internet/WAN stopped working. On the original ISP version, all relevant settings were hidden so there was nothing to sneak into for the WAN/SFP settings. No user/password or settings provided by the provider, so I'm a bit lost.

Any idea for typical settings to try? Thx a lot!

For my ISP all I had to do was request DHCP on a specific VLAN on the wan-interface (VLAN 10 for Get/Telia)

This was actually visible in the old interface, I just didn’t notice until afterwards :sweat_smile:

Thanks a lot! Indeed, configuring the ethwan VLAN to (ID from Provider)

VLAN Type:  802.1Q
Base Device:    WLAN (eth0)
VLAN ID:    92
Priority:   0

brought the connection back!

1 Like

Nice! If you share what ISP and subscription you have, it may help others in your situation too :slightly_smiling_face:

Great to see this thread recover :slight_smile:
I have also an EG400 and wanted to use it as an advanced AP, flashed 4.2 beta something on it (I unlocked it from my ISP as they did not patch, so I was able to use this), but it was not working properly. Ever since I tried to build newer versions several times, but I was never able to get it working.

But tell me one thing: My understanding was, that quite a few devices should be compatible with each others build. That's why I tried to build 6.4 just today with the config for the DG400prime device.
But still no luck with that.

I am also slowly giving up on this...

Using the 4.3 formware uploaded above for now, just to see how it behaves. Thanks for that one! :slight_smile:

I’ve contacted Iopsys support. They say 4.3 is the absolutely last version to support the EG400.

I don’t have any good deep insight into Inteno routers, but I wouldn’t by default assume any two router-firmwares are cross-device compatible unless given clear assurances about that.

Successfully flashed the latest firmware, thanks! How do I get root access for this? I need to put in vlan 10 for Telia to get internet access.

See above. You just add your ssh-keys in the management UI, and then you can SSH in as root.

Default login for the web-interface should be admin/admin. You may also be able to set VLANs there without fiddling with SSH.

I did not get SSH to work, but finally found it in the GUI. Works now. Thanks guys!