Results 1 to 1 of 1

Thread: 802.1x network manager no longer working under 13.04 64 bit

  1. #1
    Join Date
    Dec 2009
    Beans
    1

    802.1x network manager no longer working under 13.04 64 bit

    Did a fresh 64bit install and connection to a Ethernet with 802.1x is not working anymore. With 12.10 32 bit worked fine and upgrading from 12.10 to 13.04 32bit also worked fine.

    But decided to do a fresh 64 bit install of 13.04 and 802.1x is not working now.

    Conf:

    Authentication: Protected EAP
    No CA Certificate
    PEAP: Automatic
    Inner Authentication: MSCHAPv2
    User: myuser
    Password: mypassword

    When trying to use this sometimes network manager applet crashes.

    syslog:
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) starting connection 'ProtectedEthernet'
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0/wired): connection 'ProtectedEthernet' has security, but secrets are required.
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> (eth0): device state change: config -> need-auth (reason 'none') [50 60 0]
    May 14 17:48:16 pc109 NetworkManager[1253]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
    May 14 17:48:16 pc109 kernel: [ 1321.113459] r8169 0000:13:00.0 eth0: link up
    May 14 17:48:16 pc109 kernel: [ 1321.113472] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    May 14 17:48:17 pc109 avahi-daemon[1197]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7a45:c4ff:fea6:5be8.
    May 14 17:48:17 pc109 avahi-daemon[1197]: New relevant interface eth0.IPv6 for mDNS.
    May 14 17:48:17 pc109 avahi-daemon[1197]: Registering new address record for fe80::7a45:c4ff:fea6:5be8 on eth0.*.

    it remains here for a while trying to connect until:
    May 14 17:50:16 pc109 NetworkManager[1253]: <warn> No agents were available for this request.
    May 14 17:50:16 pc109 NetworkManager[1253]: <info> (eth0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
    May 14 17:50:16 pc109 NetworkManager[1253]: <info> Marking connection 'ProtectedEthernet' invalid.
    May 14 17:50:16 pc109 NetworkManager[1253]: <warn> Activation (eth0) failed for connection 'ProtectedEthernet'
    May 14 17:50:16 pc109 NetworkManager[1253]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    May 14 17:50:16 pc109 NetworkManager[1253]: <info> (eth0): deactivating device (reason 'none') [0]

    This connection has always worked for me.

    Any tips, workarounds will be appreciated.


    I also found this so it seems I'm not the only one. Serious issue (for me) since I bet many connect through 802.1x in their office.

    https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1173152


    ---

    If anyone cares I added an alternate solution to using network-manager at the end of that bug report.
    Last edited by dafema; May 14th, 2013 at 07:22 PM. Reason: Solved

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •