Temporary solution to NM LEAP glitch.

This is only for people who believe in kludgey solutions to annoying
problems. As was decided, LEAP does not work in the current NM in the
sense you can configure it and it will connect but never connect on
further logins.

A solution has been suggested Jon Escombe and eventually it will be
included in the distribution. What can you do in the meantime?

What I have done is the following. Created a script which removes the
directory TrinityAP which represents the LEAP access point in my .gconf
directory tree. The next time you can configure the LEAP connection from
the beginning and connect; and go on your merry way. Before you log off
you must remember to run the script, which completes the "kludge"
solution to the problem.

It works but be free to ignore it if you hate kludges.
Who goeth a-borrowing goeth a-sorrowing. -- Thomas Tusser
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam sbcglobal net

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]