Comment 1 Andre Klapper 2010-05-29 01:17:56 UTC

Hi,

(In reply to comment #0)
> 1. Connect to an open Wifi network requiring Layer-7 authentication via a
> captive portal

Uhm, I miss technical background. A link to some info about this is welcome.

What does "broken connectivity" mean?
If you manually disconnect from the first WiFi network and manually reconnect,
can it be used again? Or is that bad that you would have to reboot?

I resolved this problem using a script in /etc/network/if-up.d/

You have to use wget with post-data options. Good luck to find your post-data
syntax…

Here is my script :

#!/bin/sh

ESSID="my-essid-with-auth"
LOGIN="Login=mylogin"
PASSWORD="Passwd=mypasswd"
SUBMIT="submit_button=mybutton"
URL="https://provider/cgi-bin/script.ext"

if test "`iwconfig wlan0 |grep -o $ESSID`" = "$ESSID" ; then
   wget --no-check-certificate --post-data "${SUBMIT}&${LOGIN&}${PASSWORD}"
$URL -O - > /dev/null
fi

Andre: sorry about the delay, I somehow lost track of that bug.

Captive portal: http://en.wikipedia.org/wiki/Captive_portal

Broken connectivity means: Manual switching to 3G connection (or other, usable
Wifi) is needed. I consider anything that has to be done manually as "broken".

angus.frinc: That might work, but it's an ugly hack. And btw. - do you
understand the risks of using --no-check-certificate? If not you should better
stop using that script ...

(In reply to comment #3)
> angus.frinc: That might work, but it's an ugly hack. And btw. - do you
> understand the risks of using --no-check-certificate? If not you should better
> stop using that script ...

Thank you for your suggestion… For the certificate, I'm using it in a trusted
environment (my University), so your are right I should not write it on this
bug report, and for my use, it should be better to add the certificate to check
it.
For me, the "ugly hack" is the clear password in it. Do you have suggestion to
hide it ?

For wget, SSL and maemo, checking certificate can be done with :
wget --ca-directory=/etc/certs/common-ca/
(Sorry for the irrelevant)

Comment 6 Andre Klapper 2010-06-30 18:20:26 UTC

(Not considered a bug => enhancement)

Comment 7 Andre Klapper 2012-03-24 11:45:48 UTC

The Maemo 5 User Interface and Maemo 5 platform components (e.g. libraries)
used for the N900 are considered stable by Nokia and it seems that there are no
plans for official updates currently, hence nobody plans to work on this
enhancement/wishlist request. 
(And in case you feel like discussing this situation: Nokia Customer Care or
http://talk.maemo.org would be the place to do so as you will not reach Nokia
officials in this community bugtracker - though all of this is really no news.)

Reflecting this status by setting RESOLVED WONTFIX for this
enhancement/wishlist request (see
https://bugs.maemo.org/page.cgi?id=fields.html#status for status explanations).

There is a small chance for issues in those Maemo components that are open
source: Contributed patches could be included and made available in the Maemo 5
Community CSSU updates. 
The Maemo CSSU project is run by a small team of volunteers; see
http://wiki.maemo.org/CSSU for more information.
So in case that you can provide a patch that fixes the reported problem, please
feel encouraged to file a request under
https://bugs.maemo.org/enter_bug.cgi?product=Maemo%205%20Community%20SSU .
Please note: The Maemo CSSU project is not related in any way to Nokia.


( Tag for mass-deleting bugmail: [cleanup20120324] )