samuelthomas2774 / airport Goto Github PK

Successfully used node-acp to allow ssh access into my Time Capsule, but how can I access the actual drive containing the Time Machine sparse bundles?

I realise I can mount the drive on a Mac, but I want to set file ownership and permissions which I cannot do over the network. So now, logged in via SSH, I was expecting to find them mounted on /Volumes, or /mnt possibly, but nope, not there.

No 'find' command to help search, but is the disk never actually mounted and the 'sever' simply uses the raw device? Seems unlikely though. Is it even possible?

Anyone help? How can I now access the hard drive contents?

Hi there

At first, a happy new year 2021! :-)

This is not a bug report, - it is more a technical question. Apple is using also at their Time Capsules a specific FreeBSD version. That one includes a special samba version which handles the SMB1 and AFP network shares.

My main question is now, exists there a way to change (over SSH) the settings of the smb.conf file? Well, I am unsure how the whole samba situation looks at the Time Capsule, maybe Apple has here a fully different approach without the use of a regular smb.conf file.

The idea is to disable the SMB1 signing feature. This can be achieved with the server signing = disabled setting. The default TC settings seems to be server signing = mandatory. That on enforces the SMB1 signing in any case. Unfortunately this slow downs the transfer speed extremely. Over AFP it is possible to reach up to 100MB/s transfer speed to a network share, when the SMB1 protocol is used that one is falling down to around 15MB/s.

The disabling of the SMB1 signing accelerates the transfer times dramatically. This is confirmed for Mac OS X based SMB1 network shares. More information about that matter can be found here: https://apple.stackexchange.com/questions/401926/a-way-to-disable-the-smb-signing-mechanism-at-the-apple-time-capsule

Hello. You may know, only some of the encryption keys are provided - basebinary 107, 108, 115, 120

I wanted to share the key for device #106, Apple TimeCapsule 1st Gen: 513C1CA5BF035127335F7C2596AA20AA, and ask if anybody can share the key for device #109, Apple TimeCapsule 2nd gen dual-band?

Here's how I got the #106 key: I used acp --setprop dbug 0x1 to enable ssh, logged in, then curl -T /dev/rflash0.raw ftp://username:[email protected]/flash0.primary, then binwalk -e to separate the gzip'd kenrel+filesystem.

You can find the key by opening the uncompressed image and searching for the 16 bytes right before "gec�.APPLE BOOTLOADER INFO"

Why? I'm trying to upgrade my 1st gen TimeCapsule to Atheros dual-band; I have the correct card from a failed 2nd gen. I was able to decrypt and flash the #108 Airport Extreme v3 firmware (similar hardware, but DON'T TRY UNLESS YOU CAN FIX THE CHECKSUM or RECOVER YOUR BRICK). It boots and partially detects the card, so I'm close... I just need that #109 key... Thanks!

https://github.com/ipatch/theairportwiki/ seems to have some good resources on cross-compiling binaries for the version of bsd running on the airports. It might be useful to link this somewhere in your wiki, since information on the web is pretty sparse.

# acp features -h 192.168.10.137 -p passhere

Authenticating
getA: client key length 191 is less than the recommended 256 bits
Authenticated!
Error: Not enough data to parse
    at Function.parse (C:\Users\user\AppData\Roaming\npm\node_modules\node-acp\dist\lib\cflbinary.js:185:19)
    at Function.parse (C:\Users\user\AppData\Roaming\npm\node_modules\node-acp\dist\lib\cflbinary.js:27:37)
    at Client.<anonymous> (C:\Users\user\AppData\Roaming\npm\node_modules\node-acp\dist\lib\client.js:260:44)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\user\AppData\Roaming\npm\node_modules\node-acp\dist\lib\client.js:5:58)

I'm actually trying to change a country code on Airport Extreme 802.11ac.. running latest f/w 7.9.1

Hello dear. I am inspired by your article. I got access to the router. cool. but I ran into a problem. I wanted to install homebridge.io (node.js) on the router. but I couldn’t do it because I don’t understand how. netbsd is greatly reduced and I don’t know how to deliver packages. help me please

firmware version: 7.9.1
the AirPort-startup.sh working,
but the disk sharing broken after reboot even if I disconnect USB drive.
so I must rename rc.local to disable it.
How should I fix it?

Since I didn't find anything online about this, I thought I'd leave some quick notes on how to do this. (It wasn't obvious to me at first, although it's possible that this is common sense for those with bsd networking experience)

• ifconfig works as you'd expect. Be aware that ifconfig has some AP specific suboptions that you may not have used before, e.g. ifconfig wlan0 list sta

• The airports use hostapd to handle the access points creation. At boot there's an rc script that starts hostapd (see the invocation in ps auxww). The corresponding files are in /etc/, e.g. hostap_wlan1.conf.

• Let's say you want to change the ssid currently broadcast on wlan2. You'd do ifconfig wlan2 down followed by killing the corresponding hostapd process (check output of ps). Then change the ssid in hostap_wlan2.conf (since there's no vi, you can use sed to rewrite). Update the wpa psk in hostap_wlan2.wpa_psk as well (same as you would for wpa supplicant). Then relaunch hostap with the same invocation you saw before (add a nohup so it's not killed when you logout), and your changes should be live.

• The specific version of hostapd used seems to be non-standard since I couldn't find the specific config options documented anywhere, but most should be self explanatory. You can download and disassemble the hostapd binary to see a list of all possible config options.

Any idea how to change the raPo (transmit) of the WiFi property using acp? You used to be able to do this with old versions of the AirPort utility but you are no longer able to in the latest version. (Side note: love this wiki, thanks for all of your work).