From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: networkmanager: update to 0.9.2.0 causes trouble
Date: Fri, 18 Nov 2011 10:51:58 +0100 [thread overview]
Message-ID: <ja59ru$sno$1@dough.gmane.org> (raw)
In-Reply-To: <201111180227.55333.schnitzeltony@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 18-11-11 02:27, Andreas Müller schreef:
> On Friday, November 18, 2011 12:21:47 AM Andreas Müller wrote:
>> On Friday, November 18, 2011 12:07:50 AM Koen Kooi wrote:
>>> Op 15-11-11 15:07, Andreas Müller schreef:
>>>> On Tuesday, November 15, 2011 12:23:45 PM Koen Kooi wrote:
>>>>> Op 14-11-11 22:07, Andreas Müller schreef:
>>>>>> On Monday, November 14, 2011 01:05:00 AM Andreas Müller wrote:
>>>>>>> since
>>>>>>>
>>>>>>> commit 037cb32f99f229c9c55a029bec088ebc7f59d278 Author: Koen
>>>>>>> Kooi <koen@dominion.thruhere.net> Date: Fri Nov 11 12:50:38
>>>>>>> 2011 +0100
>>>>>>>
>>>>>>> networkmanager: update to 0.9.2.0
>>>>>>>
>>>>>>> wlan connects successfully to my router but *fails* to
>>>>>>> connect external locations.
>>>>>>>
>>>>>>> networkmanager / nm-applet set up my network as eth0: IPv4
>>>>>>> fixed IP wlan0: WPA & WPA 2 Personal / IPv4 DHCP
>>>>>>>
>>>>>>> Attached you find the results for networkmanager 0.9.2 and
>>>>>>> networkmanager 0.9.0 (reverted
>>>>>>> 037cb32f99f229c9c55a029bec088ebc7f59d278)
>>>>>>>
>>>>>>> My suggestion: * revert
>>>>>>> 037cb32f99f229c9c55a029bec088ebc7f59d278 until fixed * send a
>>>>>>> note to gnome bugzilla
>>>>>>
>>>>>> FYI: with network-manager-applet the problem persists
>>>>>
>>>>> I'm seeing the same problem with default route not getting set,
>>>>> but rolling back to the older release won't solve much since
>>>>> binaries are already out there :/
>>>>>
>>>>> regards,
>>>>>
>>>>> Koen
>>>>
>>>> So let's see it as another challenge :)
>>>
>>> As a small update: I'm still working on it. Although I haven't fixed
>>> the route issue, I have found (and fixed!) other issues :)
>>
>> I saw that - and I was full of hope but 10 minutes ago I tested your
>> last commit fixing version detecttion of dhclient.
>>
>> It is not much but I tried with elder versions to bisect a bit when we
>> were kicked out.
>>
>> 0.9.1.95: same - no default route 0.9.1.90: build gets totally confused
>> when libnl-1 and libnl-2 are found. So I build from scratch with
>> libnl-2 only but fall over a linker error...
>>
> I checked the first commit working with libnl-2 (two commits after our
> working version 0.9.0) [1] together with libnl-2 and nm-applet 0.9.0: It
> does not create a default route.
>
> Two possible reasons for not working: * commit [1] causes malfunction *
> libnl-2 causes our trouble for networkmanager 0.9.0 libnl-1 was used
Or both :)
If it's the libnl2 code, we're out of luck, NM will use the highest version
available. So either we add libnl3 to meta-oe with all the associated pains
or we patch out libnl2,3 detection out of configure.
Any volunteers for taking this up with upstream NM?
regards,
Koen
>
> So long
>
> Andreas
>
> [1]
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0fe8c80faef07777b9d6712abbdfbb9671b70899
>
> _______________________________________________ Openembedded-devel
> mailing list Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk7GKr0ACgkQMkyGM64RGpG6ZACfR4IVSFnvdRehk3HOLO1XY/4J
0fAAn1/wshh+/sDFu/f1JO0hLuGgJUc4
=tgL4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-11-18 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 0:05 networkmanager: update to 0.9.2.0 causes trouble Andreas Müller
2011-11-14 21:07 ` Andreas Müller
2011-11-14 21:43 ` Andreas Müller
2011-11-15 11:23 ` Koen Kooi
2011-11-15 14:07 ` Andreas Müller
2011-11-17 23:07 ` Koen Kooi
2011-11-17 23:21 ` Andreas Müller
2011-11-18 1:27 ` Andreas Müller
2011-11-18 9:51 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ja59ru$sno$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.