Well, I think I've been wrong. Recently, I noticed that the problem was also
similar under Windows, and from this perspective, I bought a new access point
(D-Link DIR-615, couldn't find anything else that supports 802.1X and RADIUS
available last saturday afternoon).
This access point has a way to set up the "Authentication Timing", which
defaults to ... 60 minutes. With this setup, and WPA Supplicant 0.6.6 (from
Jaunty), I reproduce the "issue".
Setting up the timing at 43200 minutes (roughtly a month, it's no problem for
me), I connected without any trouble to the AP at 21:13 yesterday evening, and
I'm currently still connected.
I can understand this behavior, and conclude that my setup of Session-Timeout
in my FreeRADIUS was either bugged or inefficient. Or maybe it's the 3Com
Access Point that has an issue, which was revealed by recent WPA Supplicant
releases.
** Changed in: wpasupplicant (Ubuntu)
Status: New => Invalid
--
Frequent Wireless disconnections from WPA EAP-TLS network
https://bugs.launchpad.net/bugs/377227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
