Linux router help needed Post: 302996177

Sponsored Content

Top Forums UNIX for Beginners Questions & Answers Linux router help needed Post 302996177 by ygemici on Friday 21st of April 2017 02:45:18 AM

04-21-2017

Registered User

Hi , apoklyps3

Your linux is embedded ( for that Your "rootfs" ( "/") is in like RAM drive/disk ( as temp/pivot root ) -> then you cannot remount for r/w and this only r/w only at runtime ). )

( Your firmware in the flash ( mostly ) loaded to the RAM at the boot stages by bootloader ( like u-boot ).. )

Your "/dev/root" device is mounted to (/) point that is "read-only fs" with squashfs ( compressed ) that located in the flash ( or sometimes sdcard ? )
it should contains all binaries , startup files , default config files and the others....

* Your mount command is wrong as already @Corona688 said this.
* And you cannot re-mount the squahfs for r/w ( try with "/dev/root" lets see what happen or not )

Your device ( /dev/mtdblock5 is read/writable block device ( Flash or disk-on-chip ) with "rootfstype=jffs2" and
then you can read the some configs or other related files from it.
But also you can write via "/dev/mtd5" ( safe way ) char device to flash partiton which is writable side.
Shortly , mount command works via block device and must used via the char device for i/o operations..
Your ( /apps ) mount point is writable and has contains user apps/data/configs ( already i said above ) and these are permanent.
Look at the some details..
Managing flash storage with Linux

( the others are Kernel partitions from RAM or other memory chips ( ssd ? ) .. )

* You can look for the details of the flash partitions ( "cat /proc/mtd" )

Now i m not sure is there a easy way ? , ( because i have no knowlodge about the routers and firmware )
But i can say , you have to create the customized firmware and you must flash it to router for permanent solution.. ( if it has not nvram settings for non-squash filesystem support )
( or you must unsquashfs to extract the contents to writable partition then mksquashfs to create new image from thises and write it to the target mtd device ( like "writemtd.c" codes or image dump tools )

Another try , you maybe update the router firmware with ( open-source ) alternatives like dd-wrt , open-wrt .. ( if your product ( Kaon media ) vendor does not the new firmware..)

But best way as @Corona688 said , you must update the new firmware from original Kaon hardware vendor if there is..

Good lucks
regards
ygemici

Last edited by ygemici; 04-21-2017 at 03:58 AM..

This User Gave Thanks to ygemici For This Post:

ygemici

View Public Profile for ygemici

Find all posts by ygemici

3 More Discussions You Might Find Interesting

1. IP Networking

Linux Router?

I am trying to set up a linux box as a router, but I am a little confused on how to do this. I am using Red Hat 9.0 on a machine that has 2 nic cards. Also, I am using a DSL pppoe connection. I have installed rp-pppoe and I am connected to the internet via the pseudo pppoe interface. I have...

2. Cybersecurity

Help needed in IPTables firewall/router setup - Linux

HI all, I have setup IPTables firewall/Router and my home network, with address space 192.168.10.XXX Form my private network hosts, i can ping the gateway ( 192.168.10.101 ) , but the reverse is not happening. Can someone help me as of what i need to do, so that i can ping my private...

3. Shell Programming and Scripting

Expect script help needed- script failing if router unavailable

Hey all. Sometimes I'm tasked to change some router configs for the entire network (over 3,000 Cisco routers). Most of the time its a global config parameter so its done with a loop and an IP list as its the same configuration change for all routers. This is working OK. However, sometimes an...

LEARN ABOUT MOJAVE

eficheck

EFICHECK(8)						    BSD System Manager's Manual 					       EFICHECK(8)

NAME

     eficheck -- check the integrity of the x86 flash chip firmware.

SYNOPSIS

     eficheck --integrity-check [-h EFI-hash-input-file] [-b EFI-binary-input-file]
     eficheck --show-hashes [-h EFI-hash-input-file] [-b EFI-binary-input-file]
     eficheck --generate-hashes [-h EFI-hash-output-file] [-p output-path]
     eficheck --save [-b EFI-binary-output-file]
     eficheck --cleanup [-b EFI-binary-input-and-output-file>]
     eficheck --version
     eficheck --help

DESCRIPTION

     eficheck is a tool to check the x86 flash chip firmware.

     The following commands can be used with eficheck:

     --integrity-check hashes portion of the firmware and compares against known-good hashes

     --generate-hashes outputs hashes for a given firmware to be used as known-good hashes

     --show-hashes shows the hashes for the sub-sections of the firmware which are measured

     --save saves the full flash chip contents to a binary file. Requires root privileges.

     --cleanup zeros any privacy-sensitive data (such as nvram), enabling the file to be shared for analysis.

     --version print out eficheck version number.

     --help display a short help.

EXAMPLES

	    'eficheck --save -b firmware.bin'

		Save this system's EFI firmware as firmware.bin

	    'eficheck --cleanup -b firmware.bin'

		Overwrite the EFI variables portion of the firmware.bin, in place

	    'eficheck --generate-hashes'

		Analyze the current system's installed EFI firmware, and store the hashes into hash file(s) in current folder

		File name(s) will be selected according to image's EFI version(s)

	    'eficheck --generate-hashes -b firmware.bin'

		Analyze the firmware.bin, and store the hashes into hash file(s) in current folder. Filename will be based on the detected
     firmware version.

	    'eficheck --generate-hashes -p /usr/local/allowlists'

		Analyze the current system's installed EFI firmware, and store the hashes into hash file(s) in /usr/local/allowlists folder

	    'eficheck --integrity-check'

		Attempt to automatically determine which firmware you are running, and integrity check against the appropriate file, and report
     any differences

	    'eficheck --integrity-check -h /usr/libexec/firmwarecheckers/eficheck/EFIAllowListShipping.bun-
     dle/allowlists/IM171.88Z.0105.B08.1604111319.0.ealf'

		Compare the current system's EFI firmware against the Apple-provided expected measurements for an "iMac17,1" at firmware revision
     B08, and report any differences

	    'eficheck --integrity-check -h hash.ealf -b firmware.bin'

		Compare the given hash file against against the given firmware image and report any differences

	    'eficheck --show-hashes'

		Print the hashes for the current system's installed EFI firmware to stdout

	    'eficheck --show-hashes -b firmware.bin'

		Print the hashes for the given firmware.bin to stdout

	    'eficheck --show-hashes -h IM171.88Z.0105.B08.1604111319.0.ealf'

		Print the hashes for the given allowlist to stdout

								   May 25, 2017