PROXIMUS_AUTO_FON automatic connexion on linux using wpa_supplicant

If you understand this title, you don’t need more explanation :

/etc/network/interfaces
auto wlan1
iface wlan1 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

/etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="PROXIMUS_AUTO_FON"
scan_ssid=1
key_mgmt=WPA-EAP
eap=TTLS
identity="LOGIN@proximusfon.be"
password="PASS1234"
phase2="auth=MSCHAPV2"
}

Some may ask why some people would want to do that… I’m now using Voo, but I use my parent’s FON login when voo crash. My current project is towards aggregating the two links by load balancing, or at least have some kind of automatic failover. The more interesting part would be to switch to “FON only” when I reach my 100Gb limit…

8 Replies to “PROXIMUS_AUTO_FON automatic connexion on linux using wpa_supplicant”

  1. Bonjour,

    je viens d’essayer votre manipulation sur ubuntu mate mais pas moyen de pouvoir me connecter au réseau auto fon de proximus.

    Auriez vous une idée ? Wpa_supplicant est en 2.4, quand j’essaye de lancer la ligne de commande manuellement avec le fichier de configuration, il me renvoit une erreur comme quoi le driver n’es tpas compatible avec ce type d’authentification ?

    Cela viendrait du récepteur Wifi ?

    Merci et bonne journée,

    Yannik

  2. Hi,

    Very interesting !
    I’m trying to write some scripts so that my server can route the internet from an available hotspot to my local network (I live in a bus, so I’m changing locations from time to time)
    I was using the PROXIMUS_FON hotspots, but now I want to switch to PROXIMUS_AUTO_FON

    I tried logging in using your config example, but that didn’t work.
    My phone managed to connect, but in comparing the wpa_supplicant.conf file I found some differences, namely in the authentication protocols being used. (eap=PEAP instead of TLS)
    and no mschap is being mentioned, so I left it out.
    Neither this or your exmaple seems to work.
    The wpa_supplicant return REASON=3, followed by auth_failures=

  3. Hi,

    I was using a script to connect to the proximus_auto_fon ap. I’m living in a bus, so it would be cool to have some mechanism to switch between 3g and WiFi when there is no ap near.
    This was working great with a raspberry pi with arch on it (but my sd-card broke and for some reason arch won’t boot with the new 8Gb card, while debian does)
    Now debian doesn’t want to connect the ‘auto_fon’, only the other proximus connection…

    I was looking into the load balancing, but I read somewhere it would be rather difficult. Instead I was thinking of having my server change the router address, based on some checks (ap availability, speed (in case of different routers in different spots connected to my network))
    Maybe we can help each other ?

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.