You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an AP (Aruba IAP-315) where I want to try and get some configuration data from.
This U-boot clone (apboot) is very limited, especially in getting data out. I did first attempt to boot a more open kernel and firmware, but the firmware format is also non standard, so initial attempts at that also fails.
I have found this possibility to read "the volume data" not sure this will even work.
ubi part ubifs
ubi info
ubi read 0x44000000 ubifs
md.b 0x44000000 63361024
I would like to receive any insight on any kind of special cases I would need to think about if performing this.
But I would also like to attempt an "over serial block device read" what this would do is convert any read request to commands sent over serial.
It would send md.b 0x44000000 2048 to read first 2048 bytes and dynamically adjust any requests.
One goal here would be to get a filesystem dump, without reading every byte of the volume (that would take around 40 hours over 9600 baud)
I fully acknowledge there will be challenges, but is there anything about ubifs (which I so far understand very little about) that makes this approach unusable? For example, do I need to get data that isn't available from this kind of memory dump?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have an AP (Aruba IAP-315) where I want to try and get some configuration data from.
This U-boot clone (apboot) is very limited, especially in getting data out. I did first attempt to boot a more open kernel and firmware, but the firmware format is also non standard, so initial attempts at that also fails.
I have found this possibility to read "the volume data" not sure this will even work.
I would like to receive any insight on any kind of special cases I would need to think about if performing this.
But I would also like to attempt an "over serial block device read" what this would do is convert any read request to commands sent over serial.
It would send
md.b 0x44000000 2048to read first 2048 bytes and dynamically adjust any requests.One goal here would be to get a filesystem dump, without reading every byte of the volume (that would take around 40 hours over 9600 baud)
I fully acknowledge there will be challenges, but is there anything about ubifs (which I so far understand very little about) that makes this approach unusable? For example, do I need to get data that isn't available from this kind of memory dump?
More info about the device in question https://gist.github.com/NiKiZe/19fb14f665f36db494769ae196e6b04e
Beta Was this translation helpful? Give feedback.
All reactions