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
Go to OpenWRT release page, select the latest release stable release, then targets -> x86 -> 64. Right-click generic-ext4-combined.img.gz (not the "efi"!) and copy the link.
On the Proxmox host, download the archive and unpack it:
wget *paste link here*
gunzip openwrt-*.img.gz
Resize the image to be the size you want your VM's disk to be (example with 8 GiB):
Getting 802.11r Fast Transition working with WPA(2)-Enterprise is quite painful. There is information on the forums, but things have changed quite a bit during the last few years. These are notes mostly for my own benefit.
Tricky bits as of OpenWRT 23.05 (in Luci "WLAN roaming" tab of wireless network settings):
NAS Id should be set to something unique, like the name of the AP.
Mobility domain defaults to a sane value. Leave it empty.
Reassociation deadline's default of 1000 is bad. Apparently Cisco uses 20000 here, setting that appears to be helpful.
FT Protocol "Over the air" is the good setting.
If you're using WPA2-PSK, check "Generate PMK locally" and you're done. Save&apply and it should just work.
These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing.
With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.
Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.
Sending authorization values
There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed.
It's recommend to use the Authorization header. If header auth isn't an option, the token may be sent through the ApiKey query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adb shell "cmd package install-existing com.sec.android.app.simsettingmgr"# SIM card manager, maybe required, contains configuration and settings for handling dual SIM (give a SIM an icon, a name, and so on)
adb shell "pm uninstall -k --user 0 com.samsung.android.smartcallprovider"# The 4th tab in the Phone app for 'local places'
adb shell "pm uninstall -k --user 0 com.sec.vsim.ericssonnsds.webapp"# NSDSWebApp. The Non Sim Device Solution (NSDS) is linked to VoLTE and VoWifi (Wifi Calling). NSDS allows connecting non sim devices to IMS core: https://uk.linkedin.com/in/hemant-kumar-dewnarain-2b779679
adb shell "pm uninstall -k --user 0 com.android.cts.ctsshim"# Part of the Android Compatibility Test Suite: https://source.android.com/compatibility/cts/setu