We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2013-12-29 20:14:07 +0200 |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a cewrtain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Chrtistmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
2 | No.2 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a cewrtain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Chrtistmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
3 | No.3 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a cewrtain certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Chrtistmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
4 | No.4 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Chrtistmas Christmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
5 | No.5 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Christmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
6 | No.6 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Christmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Christmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...
8 | No.8 Revision |
Well, it's a complicated thing, but I'd like to raise the issue anyway ...
Worldwide more and more public WiFi/WLAN hotspots pop up, being usable under different commercial and technical concepts
All such concepts are basically using just 2 technical concepts
[UPDATE]: nodevel just loaded "ROAMER" app to openrepos: https://openrepos.net/content/nodevel/roamer It's providing EAP/802.1x/WPA enterprise access. It's primarily targeting Eduroam but I also tested it on an EAP based WiFi hotspot service ....
The pity of the whole approach is, that (almost) all clients allowing automated Hotspot access, are proprietary and only available on certain OS platforms.
One of the reasons is, that WISPr and 802.1x allow different flavours of implementation within the hotspot system, so interoperability is not given. Clients have to "know" the individual network to a certain extent, in order to allow automated access. Future might see "Hotspot 2.0", but until then a truly interoperable client could only be set up with the help of a community being able to provide testing and results within hundreds of networks worldwide.
So - as Christmas just passed, I'm still dreaming of a hotspot client being so versatile/modular, that (like modern instant messaging clients) different accounts could be configured and the client automatically logs me into a hotspot as soon as it detects a suitable one .... don't know whether this is too far fetched, but I'm happy to learn ...