Bug 4375

Where it's work without issue

But you need to connect to the ssid before opening the browser.

Does it work with other hotspot/ wlan ?

forget the part "with mageia, launching an internet browser does not launch the network connection", it's not the pb

step to reproduce :

i launch the wifi connection to an open wlan (no secured protocol, just asking an id and passwd)
then
connection failed

addendum : the power of the hotspot is 100 %

other experiment :

i launch a wifi connection to a secured (wep/wpa) wlan
then
it succeeds


Does it work with other hotspot ?
i have a pc not a laptop.
each customer of FREE isp has an adsl box to connect to internet
each box is a wifi hotpsot

connecting to the wifi hotpsot of my neighbor is a backup solution if my adsl connection failed

and remember : with my smartphone it works, i can connect to the hotspot

i found an open hotspot from another isp in my building
then
no pb connection succeeds. i can have its authoring template with firefox

the difference is with "FREE" isp when dhclient send a dhcpdiscover request
there is no answer then "no dhcpoffers received"

it seems the dhcp server is slow to answer to the request.

where to put a delay in draknet or in a file ?

if i use dhcpd instead of dhclient there is an improvement
i have this :

inet adr:169.254.243.178  Bcast:169.254.255.255  Masque:255.255.0.0

but draknet says "connection fails"
with firefox i can't get the authoring template

it is strange that dhcpd get an ip address and draknet says connection succeeds
but the net applet says connection fails

i tried same experiments with ndiswrapper and the windows xp driver then i get exactly the same results

with dhcpd i get this

wlan0     Link encap:Ethernet  HWaddr 68:7F:74:FB:D1:DB  
          inet adr:169.254.15.169  Bcast:169.254.255.255  Masque:255.255.0.0
          adr inet6: fe80::6a7f:74ff:fefb:d1db/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:356 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:2018 (1.9 KiB)  TX bytes:72112 (70.4 KiB)
          Interruption:18 Mémoire:dbff0000-dc000000 


and this

wlan0     IEEE 802.11g  ESSID:"FreeWifi"  Nickname:"localhost.localdomain"
          Mode:Managed  Frequency:2.462 GHz  Access Point: DA:6E:D6:71:B5:6A   
          Bit Rate=270 Mb/s   Tx-Power:20 dBm   Sensitivity=0/3  
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:95/100  Signal level:-35 dBm  Noise level:-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

i also found this in the syslog

ifplugd(wlan0)[5786]: client: NETLINK: Packet too small or truncated! 60!=16!=1008

@ blino

do you have an idea?

CC: (none) => mageia, marja11
Source RPM: (none) => drakx-net

If you take a look at the output of "whois 169.254.15.169", part of it
says ...
Comment:        It is allocated for communication between hosts                     
Comment:        on a single link. Hosts obtain these addresses                     
Comment:        by auto-configuration, such as when a DHCP                     
Comment:        server cannot be found.

So the dhcp server is still likely not responding.

Does the adsl box have a port for a wired connection?  If it does,
I think the most useful output would be a wireshark capture of the
smartphone connecting, and a capture of the mageia system attempting
to connect.  Don't forget to edit out any passwords before attaching
such a capture.

CC: (none) => davidwhodgins

> Does the adsl box have a port for a wired connection?  If it does,
>I think the most useful output would be a wireshark capture of the
> smartphone connecting, and a capture of the mageia system attempting
> to connect.  Don't forget to edit out any passwords before attaching
> such a capture.
 yes there is a wired connexion
but for this part it is too technie for me

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX