Sponsored Content
Full Discussion: Linux router help needed
Top Forums UNIX for Beginners Questions & Answers Linux router help needed Post 302996439 by apoklyps3 on Wednesday 26th of April 2017 08:27:09 AM
Old 04-26-2017
unfortunately the firmare image is not public. the router is branded by the ISP and automaticaly updates the firmware.
My guess is that they put the firmware somewhere and it gets updated on a reboot.
Hopefuly I'll be able to intercept it next time there will be an update.
I have probed /bin/busybox myself and it seems to be an ELF-64 kind of executable...not sure what to make of that ...
the files I attached before were from mtdblock0 and 1 , because when trying to do it on mtd0 and 1 i got "dd: can't open '/dev/mtd0': No such file or directory",wich is weird because they are mentioned in "cat /proc/mnt"
In /dev I have mtd from 5 to 7 and mtdblock from 0 to 7. which of them do you want me to post?
 

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... (1 Reply)
Discussion started by: cstovall
1 Replies

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... (1 Reply)
Discussion started by: chandan_m
1 Replies

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... (3 Replies)
Discussion started by: mrkz1974
3 Replies
FIRMLOAD(9)						   BSD Kernel Developer's Manual					       FIRMLOAD(9)

NAME
firmload -- Firmware loader API for device drivers SYNOPSIS
#include <dev/firmload.h> int firmware_open(const char *drvname, const char *imgname, firmware_handle_t *fhp); int firmware_close(firmware_handle_t fh); off_t firmware_get_size(firmware_handle_t fh); int firmware_read(firmware_handle_t fh, off_t offset, void *buf, size_t size); void * firmware_malloc(size_t size); void firmware_free(void *buf, size_t size); DESCRIPTION
firmload provides a simple and convenient API for device drivers to load firmware images from files residing in the file system that are nec- essary for the devices that they control. Firmware images reside in sub-directories, one for each driver, of a series of colon-separated path prefixes specified by the sysctl variable hw.firmware.path. FUNCTIONS
The following functions are provided by the firmload API: firmware_open(drvname, imgname, fhp) Open then firmware image imgname for the driver drvname. The path to the firmware image file is constructed by appending the string ``/drvname/imgname'' to each configured path prefix until opening the firmware image file succeeds. Upon success, firmware_open() returns 0 and stores a firmware image handle in the location pointed to by fhp. Otherwise, an error code is returned to indicate the reason for failure. firmware_close(fh) Close the firmware image file associated with the firmware handle fh. Returns 0 upon success or an error code to indicate the reason for failure. firmware_get_size(fh) Returns the size of the image file associated with the firmware handle fh. firmware_read(fh, offset, buf, size) Reads from the image file associated with the firmware handle fh beginning at offset offset for length size. The firmware image data is placed into the buffer specified by buf. Returns 0 upon success or an error code to indicate the reason for failure. firmware_malloc(size) Allocates a region of wired kernel memory of size size. Note: firmware_malloc() may block. firmware_free(buf, size) Frees a region of memory previously allocated by firmware_malloc(). SEE ALSO
autoconf(9), malloc(9), vnsubr(9) HISTORY
The firmload framework first appeared in NetBSD 4.0. AUTHORS
Jason Thorpe <thorpej@NetBSD.org> BSD
January 17, 2006 BSD
All times are GMT -4. The time now is 09:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy