383 karma · joined November 19, 2015
The problem is: If the first connection of the client is a https connection, your captive portal has no possibility to redirect this request to the portal.
Note: That there are many better devices available for hacking with more Flash and RAM f.e. something like this: https://openwrt.org/toh/gl.inet/gl-mt300n_v2
echo 1 > /sys/kernel/mm/ksm/runThe documentation was telling something like: Ensure you applied all previous migrations and then start from scratch. Thats not an upgrade path. It may work for standalone web applications, but I have a python project (packaged as deb/rpm package and using the packaged django version of different distributions) that should work with multiple django versions and the user may upgrade the django version at any point.
I had to write raw sql statements to get the mirgration status of south (after the upgrade, without a working version of south anymore) and "fake" apply the migrations of the new native solution.
The DFN will change this praxis while migrating to a new root certificate from "Deutsche Telekom" until 2019, but the staff at my university has major headaches. It's far more easier to document, that the members of the university should only trust (e.g. enter their password on) sites with a certificate signed by a CA with the same name as the university.