I, Robert Love, agree to relicense my contributions to NetworkManager as
LGPL-2.1+ as proposed by Thomas Haller.
Some of my work may be held under copyright by Novell, Inc. I do not speak
for that entity.
Robert
___
networkmanager-list mailing
On Fri, 2007-01-26 at 06:23 -0500, Neal Becker wrote:
I've been using nm with a local named for caching. Works fine, but probably
overkill.
What is the simplest way to use nm and get some local name caching?
nscd, glibc's caching daemon.
Robert
On Sat, 2006-12-02 at 16:28 -0500, Jim Popovitch wrote:
In order to connect to T-Mobile (and presumably some other) 802.1x
networks (Not the current tmobile WEP), NM needs to use PAP for the
secondary (Inner Auth). I'm presently using NM v0.6.3-2ubuntu6, which
doesn't support this. Is there
On Thu, 2006-11-30 at 11:49 +0200, Tambet Ingo wrote:
Here's a small patch to mark devices disabled when they're disabled in
yast.
I have one concern about this...people might have various settings as
their STARTMODE from when they used ifup, NetworkManager currently
works, and then they
On Tue, 2006-11-14 at 09:41 +0100, Martin Vidner wrote:
Hey, Martin.
How about a small superimposed 1:1 or 2 to hint that this kind
of connection is only useful for an ad-hoc connection of two
computers?
There are also Apple-style networks without a DHCP server (or anything
else) where there
On Thu, 2006-10-19 at 13:25 -0400, Christopher Aillon wrote:
Given that --sm-disable is for all intents ubiquitous, I wonder whether
we ought to make that the default.
I suggested this before (we do so in our SUSE package) but it was
rejected. I'd be happy to do so--its a one-line change.
On Mon, 2006-10-02 at 14:51 +0200, Vincent Untz wrote:
IIRC, there was some interest to propose nm-applet for GNOME 2.18. Is
this still the case? If yes, a small mail to d-d-l would be great ;-)
Yah, I stirred that up before. I will do it right now.
Robert Love
network interfaces, but only one can be up at a time. Multiple
concurrently-up interfaces is a feature slated for our 0.7 development
tree.
Best,
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
know what you find.
The T60 has an ipw3945, which is a great chip. Try using the latest
version of the driver and firmware. I had issues with earlier versions,
but the current stuff is great.
Robert Love
___
NetworkManager-list mailing list
for this machine, if that's what you mean.
No, I mean firmware for the ipw3945.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
not need it.
What wireless driver do you have?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
in NM's init script, after you launch
it. This will block the initscript until NM obtains
a network connection or N seconds elapse (whatever
happens first).
I think (1) is ideal, but that requires a bit of work.
Robert Love
got a network connection. There are
tools to do this, Robert Love has one somewhere.
src/nm-online in CVS.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager
of glib.
Agreed.
I converted a bunch of g_malloc/g_new calls to g_slice_new, bumped out
glib requirement to 2.10, and checked it into HEAD. Everyone, please
test.
Also, I found a memory leak in the process. I back-ported that to the
0.6 branch.
Enjoy,
Robert Love
On Fri, 2006-08-04 at 13:59 -0400, Dan Williams wrote:
Thanks for finding this; though I think rather than using compile-time
flags we should be doing runtime endianness conversions...
No architecture we care about (that I know of) has machine types with
varying endianness.
Robert
Party people,
I did some preliminary testing[1] the other day with beaglefs[2], to
measure the performance gain or hit from using glib's new memory
slices[3].
In a workcase where many objects are created and freed[4], I measured a
sizable performance gain from memory slices over g_malloc. Even
, whether or not my hunch w.r.t.
wpa_supplicant is correct.
madwifi, for example, just blows up when it roams.
I wonder if locking the BSSID makes sense? It has other benefits, too
-- e.g., security.
Robert Love
___
NetworkManager-list mailing list
if wpa_supplicant does dumb things with roaming.
We sure have a lot of issues surrounding AP roaming.
Does wpa_supplicant consider roaming association loss, and kill the
connection?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list
and NM work fine out-of-the-box, although there are
a few known bugs in the driver.
Perhaps try a more recent driver and firmware.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo
.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Thu, 2006-07-13 at 12:45 -0400, Matthew Saltzman wrote:
Please push to FC5 updates-testing. Thanks!
I don't work for Red Hat.
Please bring this up on a fedora list.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list
.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
if roaming worked ...
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
if needed where it shows all is
well and a hour later drops the connection. I then have to add my AP
again.
How repeatable / reproducible?
Please attach the log.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
for editing WPA Enterprise, we should put
that in the applet. The current UI is pretty heavy -- but so are the
number of WPA-EAP options.
Is this bad boy in C? I don't see any reason not to stick it in CVS,
under gnome/editor or similar. Dan?
Robert Love
a WITH_GNOME option for
building stuff in that directory.
I think we want to integrate the editor and the applet tightly, but keep
them separate processes.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
-specific commits.
If your commit is appropriate for the stable branch, by all means commit
there, too. But keep in mind that the branch is indeed stable ...
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
the wireless spec.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
back.
Users found it confusing and it offered little gain.
Sorry that you liked it!
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
still punch a vendor for reusing the
same BSSID.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Thu, 2006-06-08 at 12:20 -0500, Paul Johnson wrote:
Perhaps the NetworkManager RPM should have a pre-requisite of
gnome-keyring-manager.
It should. But this is a Fedora issue.
Robert Love
___
NetworkManager-list mailing list
fallback support is in HEAD. Enjoy!
You can mark a network as fallback via other-network-dialog or the tool
nm-set-fallback.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman
there. Since nothing actually sets the trusted bit
true, this is merely a cleanup, the net effect is null.
All of these are against the STABLE 0.6 branch but also apply to HEAD.
You will want to `cvs up` as of now, because I just committed some bug
fixes.
Robert Love
Index: gnome/applet
. Use is simple:
$ ./nm-set-trusted network true|false
Yes, we need a wireless networks editor. I agree with you all.
Robert Love
nm-set-trusted
Description: application/shellscript
Index: gnome/applet/applet.glade
and cannot scan, if your card is broken and does not return
hidden networks, or if your network is hidden and you don't know all of
the MAC addresses.
What we do here is debatable. This is one such solution.
Robert Love
Index: src/NetworkManagerAPList.c
networks in the scan list, but
do perform the fall-back brute-force thingy.
And then...PROFIT.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
of the previous three.
Robert Love
Index: gnome/applet/applet-dbus-devices.c
===
RCS file: /cvs/gnome/NetworkManager/gnome/applet/applet-dbus-devices.c,v
retrieving revision 1.51.2.4
diff -u -r1.51.2.4 applet-dbus-devices.c
fixes since 0.6.2.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
, with two different
ESSID's, but sharing one BSSID?
That violates the wireless spec, I am 99% sure. Who makes the access
point?
The reason NM chokes on it is that we have logic to merge two AP
objects into one if they share the same BSSID.
Robert Love
. But that seems useful in very few cases.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Tue, 2006-05-30 at 18:02 +0200, Rémi Cardona wrote:
Filed it as bug #343404 :
http://bugzilla.gnome.org/show_bug.cgi?id=343404
I believe that this bug is now fixed in CVS, in which case this bug is a
dupe of #341297.
Robert Love
stuff goes to
HEAD, or gets vendor-patched instead.
I agree. I'd like to lock all API, though -- NMI, too.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
: See Joe Shaw's
patch at http://bugzilla.gnome.org/show_bug.cgi?id=331003
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Morgan Read wrote:
- Nothing, my point.
Worry not, the TODO list is not even remotely all-inclusive. And it
is mostly architectural changes.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
, but that is untrue. We want it. I do not have a time
table, but it is certainly on the list -- if you write a patch
tomorrow, we'd merge it!
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman
: ‘NMDevice80211WirelessPrivate’
has no member named ‘scan_mutex’
nm-device-802-11-wireless.c:196: error: ‘NMDevice80211WirelessPrivate’
has no member named ‘scan_mutex’
Whoops.
I checked in the STABLE patch on HEAD. Fixed, now.
Thanks,
Robert Love
.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Here it is. A bunch of crap we sadly should never need but
unfortunately do.
Robert Love
Index: src/nm-device-802-11-wireless.c
===
RCS file: /cvs/gnome/NetworkManager/src/nm-device-802-11-wireless.c,v
retrieving revision
probably need new icons.
It can be handled in the same way we do secure networks now, with a
different icon.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
,
OPT_TYPE_ASCII },
{ NULL,
OPT_TYPE_UNKNOWN } };
unsigned inti;
What else do we need (vpnc patches, etc.) to make rekeying work?
And no NM changes should break users without a patched vpnc.
Robert
On Wed, 2006-03-29 at 22:14 -0600, Eli Criffield wrote:
And how do you set it to have no password ?
I don't think he said that he did. He wants to change it.
If it is ever not set, it will prompt you for a new one on first use.
Robert Love
of the
keyring. Of course, you will lose all of your data, too.
Pretty lame!
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
file.
I added a note to NEWS on the top of the branch.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
'
for class `GtkDialog'
I don't know what these errors mean. Do anyone else?
Warnings, not errors. I suppose your libglade is old. It works fine
with 2.5.x. Does everything work fine, otherwise? If so, don't sweat
it.
Robert Love
Yes.
How can I put the icon back in notification area ?
gnome-session-properties should allow you to reenable the service.
Otherwise, do `rm ~/.config/autostart/nm-applet.desktop`.
Robert Love
___
NetworkManager-list mailing list
On Fri, 2006-03-24 at 17:32 +, Jon Escombe wrote:
Anyway, full patch attached.
Thank you, sir.
I banged on this with various networks. Works good and looks right.
Committed to HEAD and the 0.6 branch.
Robert Love
___
NetworkManager
On Sat, 2006-03-25 at 08:49 -0500, Dan Williams wrote:
Is the if.h change OK? I fear another back-and-forth with kernel vs.
userspace hearders here...
I do too, but it seems to work for me, and we should prefer glibc to
kernel headers when possible ... so, committed.
Robert Love
On Sun, 2006-03-26 at 23:31 +0200, [EMAIL PROTECTED] wrote:
why debugging at all? what about not passing any -d's?
Also possible, but don't expect anyone to be able to debug any problems.
I find -d a nice balance between noise and signal.
Robert Love
for this information, Jouni.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
then.
Presumably if the connection isn't successful then the configuration
details aren't stored?
Correct.
Anyway, full patch attached.
Thank you, sir.
I'll bang on it. Dan, what do you think?
Robert Love
___
NetworkManager-list mailing list
the options I'd prefer. That way, we have
everything together in one place, and it's in a place that's got a track
record of both KDE and GNOME devs working together :)
So long as it is f.d.o SVN (not CVS), I am 100% for this.
Robert Love
easy to pile all these options
into a single UI.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
no get that long.
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
Robert Love
___
NetworkManager-list
=invisible_char*/property
entries from .glade files in cvs
Good catch.
Committed to HEAD and the 0.6 branch.
At least in my version, Glade sets this property for me. So another
patch would be to have glade not set the field whatsoever, by default.
Robert Love
On Thu, 2006-03-23 at 10:15 -0500, Pat Suwalski wrote:
Robert Love wrote:
This won't fly.
As just one example, my passphrase at home is a legitimate hex key (I
am, yes, an idiot). Differentiating between ASCII and passphrase is
even harder. We need to ask.
I've seen
, and most users going forward, use
passphrases, so the best bet we can have is default to passphrase as
the key type and expect our users to change it if needed. Otherwise, as
Dan wrote, we are just asking for confusion.
Robert Love
___
NetworkManager
On Thu, 2006-03-23 at 10:43 -0500, Pat Suwalski wrote:
I don't see how -- to the best of my knowledge, the ascii keys are not
allowed to be 26 characters long, and the hex keys must be 26 characters
long...
Right, but passphrases can be either of those things.
Robert Love
of typing hex...
Yah, this would be nice. We would have to re-run our validation
function on the input and clear it if it no longer matched, though.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
to discuss: I wanted to propose
NetworkManager (or at least nm-applet) for the GNOME Desktop proper, as
g-v-m is now a member.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo
it.
Glade seems to be setting it, so it snuck in when I or someone else last
edited the file, I guess.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
. To be sure, most ifup scripts wait longer than 25s.
Dan, any thoughts here on a bump?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
, we do not
support that. I have been intending to add second-stage authentication,
but I don't know a lot about it.
If you could get a hold of a working wpa_supplicant.conf for your
configuration, that would be a start.
Robert Love
Hi, guys.
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
Thanks!
Robert Love
On Wed, 2006-03-22 at 14:50 -0500, Robert Love wrote:
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
If not obvious: Select Dynamic WEP
time you send the other parameters.
... if you can do this while testing Dynamic WEP, that would be
helpful. ;-)
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo
... and selecting
WPA Enterprise with a key type of Dynamic WEP and filing out the
other fields selectively, as needed.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager
generate this exact configuration now...
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Tue, 2006-03-21 at 12:24 +, Jan Mynarik wrote:
same here (802.1x EAP/TLS) and no n-m's WPA profile works (via Connect to
Other
Wireless Network).
I am going to look at adding this -- but, what in here actually says
use WEP ?
Robert Love
for all users of the 0.6 branch.
See ChangeLog and NEWS for the full scoop.
Enjoy,
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Recent madwifi-ng releases (since r1451 or so) have been busted.
The attached patch fixed it for me.
Robert Love
diff -ur madwifi-ng-r1451-20060212/net80211/ieee80211_input.c madwifi-ng-r1451-20060212.mod/net80211/ieee80211_input.c
--- madwifi-ng-r1451-20060212/net80211
tarballs that don't match the module name?
I don't think you can.
So we can do this, but we'd have to put all of the VPN plugins in one
tarball.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org
in the
base NetworkManager package.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Mon, 2006-03-06 at 23:01 +0100, krischan wrote:
WEP and VPN worked perfectly.
This is because your wireless driver does not support WPA (or more
likely reports that it does not). What driver?
NM only displays security methods that your driver supports.
Robert Love
to
be), so we do not necessarily have something to release.
I agree it would be nice to get tarballs of these packages up. I can
talk with the gnome.org folks and see what we can do other than created
n new modules for all of the VPN plugins.
Robert Love
, and there is still a problem, but I think this patch
is fine.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
don't need dynamic allocations here.
const char *driver = madwifi;
is sufficient. As it stands, this code allocates both a static
character array and a dynamic one. Just a tip ;-)
Robert Love
___
NetworkManager-list mailing list
= cat;
else if (bar)
driver = dog;
else
driver = fox;
And you do not free it.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo
Attached patch is a collection of workarounds for madwifi, orinoco, and
ndiswrapper that I have worked on or that have been posted to this list.
We are probably not going to merge any of this. If NM does not work for
you but works with this patch, we would like to know.
Robert Love
basis.
I actually would prefer to just require DBUS 0.60, although your patch
is a viable option, too. By and by, I don't see where we require 0.50,
though.
Dan, opinions?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list
On Fri, 2006-03-03 at 13:31 -0500, Dan Williams wrote:
Not particularly, but I think I'd rather require dbus 0.60 too. While
the patch does preserve the old behavior, the old behavior was clearly
broken.
I bumped our requirement from 0.22 (!) to 0.60.
Robert Love
to identify list traffic in a long list of
email. I get several hundred mails a day and every little bit helps.
Set up a mailing list filter!
The subject prefix is ugly and annoying.
Filter on
^X-BeenThere: networkmanager-list@gnome.org
and you are gold.
Robert Love
On Thu, 2006-03-02 at 10:39 -0500, Robert Love wrote:
Bill said the committed patch worked for him, but that obviously doesn't
make sense now.
s/Bill/Brian/
sorry.
Anyhow, this patch at least does not break anything for me.
ndiswrapper users, does this fix your problems?
Robert
On Thu, 2006-03-02 at 09:52 -0500, Dan Williams wrote:
We've seen this around as well, but it seems to be fairly random.
I have a bug report (Novell bug #153536) where it is happening pretty
regularly.
Very odd.
Robert Love
On Thu, 2006-03-02 at 10:42 -0500, Robert Love wrote:
On Thu, 2006-03-02 at 10:39 -0500, Robert Love wrote:
Bill said the committed patch worked for him, but that obviously doesn't
make sense now.
s/Bill/Brian/
sorry.
Anyhow, this patch at least does not break anything for me
On Wed, 2006-03-01 at 19:38 -0500, Brian Magnuson wrote:
Appears to be ok. Comments?
Unfortunately, it won't work for everyone. There are only a handful of
wpa_supplicant drivers. ndiswrapper just happens to be one of them.
Robert Love
);
+ }
Has anyone tested without this chunk, and with just the second hunk that
sets the wpa_supplicant driver?
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo
requisite, or if
setting the driver is sufficient. Partly my curiosity stems from the
fact that we do a set_mode() a few lines later ... and apparently that
is okay.
Robert Love
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http
a generic wext driver that handles the wireless
extension API. it also defines a handful of custom drivers, because the
kernel wireless drivers are such pieces of cat poop. madwifi and
ndiswrapper are two of them. but, say, airo (a valid kernel driver) is
not.
Robert Love
to do.
So ... this works for you? Good.
I would be curious if you needed the second hunk. The reason being is
that Dan doesn't want to put these driver-specific hacks in NM (with
good reason), but the first hunk makes more sense.
Robert Love
1 - 100 of 265 matches
Mail list logo