I was at my brother's house for part of last week, and he's using WPA in
a location where there are a lot of APs visible, all on different
networks (i.e. suburbia). Occasionally NM would try to associate to the
wrong AP, and it'd log a message about roaming between two APs. When I
look up the
On Wed, 2006-05-03 at 11:20 -0400, Dan Williams wrote:
On Wed, 2006-05-03 at 10:32 -0400, Robert Love wrote:
What else do we need (vpnc patches, etc.) to make rekeying work?
And no NM changes should break users without a patched vpnc.
I asked about this when the patch for vpnc came
Dan, may I?
Index: vpn-daemons/vpnc/src/nm-vpnc-service.c
===
RCS file: /cvs/gnome/NetworkManager/vpn-daemons/vpnc/src/nm-vpnc-service.c,v
retrieving revision 1.17
diff -u -p -r1.17 nm-vpnc-service.c
---
On Wed, 2006-03-29 at 07:53 +0200, Trond Husø wrote:
Hi list,
Fedora Core 5 has just been released, and I might concider upgrading
from FC4. But before I do, I need to know if some of my favorite
programs works. One of these are Network Manager.
So: Does it work under FC5?
We ship it and
On Wed, 2006-03-22 at 10:27 -0500, Robert Love wrote:
On Thu, 2006-03-16 at 16:09 +0100, Radek Vokál wrote:
Hi, I've realized that 25sec DHCP timeout limit is not enough on my slow
network, so I've proposed a small patch on RH bugzilla for adding new
option to NetworkManager, allowing to
On Wed, 2006-03-22 at 10:57 -0500, Darren Albers wrote:
I have had other bug reports that users need DHCP timeouts in the 30~40
second range. To be sure, most ifup scripts wait longer than 25s.
I think a timeout in the 30-40 second range would also resolve the
issues with portfast...
On Tue, 2006-03-14 at 10:41 -0500, Dan Williams wrote:
What's the situation here? NM only cares if the machine's ethernet card
has a link or not, which is reported by the driver for the card itself.
Once the driver reports that it has a link, NM will attempt to acquire a
DHCP address on that
On Tue, 2006-03-14 at 11:47 -0500, Derek Atkins wrote:
Quoting Eli Criffield [EMAIL PROTECTED]:
I opened a ticket at madwifi.org asking for compliance to wext 19 with
the infomation from Dans email. It promptly got changed to minor and
to enhancement instead of defect.
Anyone using
On Thu, 2006-02-23 at 10:16 -0500, Robert Love wrote:
I think we can separate should never restart the system bus from foo
should be able to survive a system bus restart.
The former is good policy, the latter is good programming. We can have
both.
Well, half right anyway. The former
On Fri, 2006-01-27 at 15:17 -0500, Dan Williams wrote:
See attached screenshot and patch.
So what do we do when you have more than one wireless card in this case?
A horizontal separator between each network card's list would be good...
The same question really applies to wired networks as
On Thu, 2006-01-26 at 09:29 -0500, Robert Love wrote:
On SUSE, you set NM_CONTROLLED=no in the network interface's config file
and NM will not handle it. Personally, I don't know why you would ever
want NM to not handle an interface ;-) but people asked.
Because you're building an AP that
On Mon, 2005-12-12 at 11:02 -0500, Robert Love wrote:
Just a thought, as we move to libnm-util, we should settle on a
signedness of the char* we use for wireless keys. Sometimes we use
char*, sometimes we use unsigned char*. But the bigger problem is that
we mix the types via e.g. return
On Mon, 2005-12-12 at 13:49 -0500, Robert Love wrote:
On Mon, 2005-12-12 at 13:48 -0500, Dan Williams wrote:
Sounds good to me unless there are other objections. What kind of
annoys me though is that when doing strlen(), strcmp() and whatnot, all
the standard library calls take signed
On Wed, 2005-11-09 at 15:14 -0500, Bill Moss wrote:
If atheros/madwifi has a big following, maybe someone out there can take
a look at that driver relative making it work better with NM.
What actually needs to happen is for somebody to write a real driver for
it. A couple of people have
On Fri, 2005-10-21 at 01:58 +0200, Tomislav Vujec wrote:
On Thu, 2005-10-20 at 14:38 -0400, Peter Jones wrote:
Both of them should be started by init during boot. I think starting it
through this mechanism is just incorrect.
Can you elaborate on this? From my point of view, named can
On Thu, 2005-10-20 at 18:39 +0200, Tomislav Vujec wrote:
On Tue, 2005-10-18 at 14:41 -0400, Dan Williams wrote:
No, NM no longer spawns named directly at any point. If named is
already running (we check whether the DBUS service that named provides
is active or not) then NM will use it. If
On Tue, 2005-09-06 at 10:55 +0200, Rene Rask wrote:
Hi list
One of the most frustrating this about NM is the DHCP server response
policy. After a long and exhausting fight with an Atheros based card I
got a lot of:
NetworkManager: DHCP: Reply message's source port (5353) was not the
DHCP
On Sat, 2005-07-23 at 01:49 +0200, Pierre Ossman wrote:
Is there a special reason that the VPN plugins are located in /usr/bin?
It seems more correct to have them in /usr/libexec since they are only
called by NetworkManager.
Yeah, you're right.
--
Peter
On Thu, 2005-07-14 at 13:00 -0400, Derek Atkins wrote:
Hi,
I've got two issues with 0.3.5 right now (well, STABLE_0_3 branch):
1) it's not noticing eth0. I've got kernel log messages that the
cable is plugged in, but NM never seems to switch to the ethernet
device. I'm wondering
On Thu, 2005-06-30 at 10:47 -0400, Robert Love wrote:
On Thu, 2005-06-30 at 09:03 -0400, Bill Moss wrote:
After an acpi suspend/resume, both e1000 and ipw2200 drivers are loaded
but the wired interface is not up. The patch fixes this by bringing up
all devices when NM wakes.
Ha! I
On Mon, 2005-06-27 at 11:52 -0400, Derek Atkins wrote:
But you're right -- just re-clicking the network would work.. BUT it would be
nice to have better 'scripting' support for suspend/resume to force a new
network discovery and re-running DHCP even if the lease is still valid and the
SSID
On Mon, 2005-06-27 at 13:00 -0400, Robert Love wrote:
On Mon, 2005-06-27 at 12:55 -0400, Robert Love wrote:
On Mon, 2005-06-27 at 12:35 -0400, Robert Love wrote:
Hrm, neither of these work for me with NM current CVS.
Nevermind. I just looked at the code and realized the errors of my
On Mon, 2005-06-27 at 21:31 -0400, Robert Love wrote:
On Mon, 2005-06-27 at 15:45 -0400, Peter Jones wrote:
Just to be sure -- ethtool shows that the interface has link, right?
Yup.
I can reproduce it simply by sending the sleep and then the wake D-BUS
method, so its definitely NM
On Thu, 2005-06-23 at 10:33 -0400, Bill Peck wrote:
Is there a technical reason why the keyring can't be unlocked by the
login? (Obviously the passwords would have to be the same) I know I'm
thinking in fairy land where we might have single sign on one day.. but
I can dream can't I?
Well,
On Thu, 2005-06-16 at 16:22 -0400, Robert Love wrote:
Some more stuff from this kernel-hacker-turned-UI-ninja.
Some of this might be a bit more contentious, but it is all in the name
of the illusive stetic:
- Rename Other Wireless Networks... to Connect to Other
Wireless
On Mon, 2005-06-13 at 11:44 -0400, Bill Moss wrote:
1. in vpn-daemons/vpnc do 'autogen.sh --prefix=/usr --sysconfdir=/etc'
Now the VPN Connections menu shows up.
I think this means you need to add vpn-daemons to the SUBDIRS line in
Makefile.am and rerun autogen.sh
--
Peter
On Mon, 2005-06-13 at 13:56 -0400, Dan Williams wrote:
On Mon, 2005-06-13 at 13:50 -0400, Peter Jones wrote:
On Mon, 2005-06-13 at 11:44 -0400, Bill Moss wrote:
1. in vpn-daemons/vpnc do 'autogen.sh --prefix=/usr --sysconfdir=/etc'
Now the VPN Connections menu shows up.
I think
On Tue, 2005-06-07 at 20:15 +0200, Kay Sievers wrote:
This makes NM reading the MAC address for real instead of only a few
bytes + garbage.
Thanks, applied.
--
Peter
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
On Mon, 2005-04-11 at 13:53 +0100, Simon Kelley wrote:
. Query a configuration setting from the DHCP server. (using DHCPINFORM,
and cached.)
I think NM (or, rather, any program in the position of asking for a new
lease to be requested by the dhcp client, etc) should be the part doing
the
On Mon, 2005-04-11 at 12:07 -0400, Dan Williams wrote:
NM enforces security on devices that are not the active device my
ensuring that those inactive devices have no IP address and do not
show up in the routing table.
Just as a side note, this is (slightly) broken by design. The Linux
kernel
On Tue, 2005-04-12 at 16:35 +0100, Simon Kelley wrote:
Peter Jones wrote:
On Mon, 2005-04-11 at 13:53 +0100, Simon Kelley wrote:
. Query a configuration setting from the DHCP server. (using DHCPINFORM,
and cached.)
I think NM (or, rather, any program in the position of asking
On Tue, 2005-04-12 at 17:25 +0100, Simon Kelley wrote:
[...]
It's worth pointing that AFAIK no current Unix DHCP
implementaions allow use of DHCPINFORM and therefore fetching of DHCP
configuration independent of getting a DHCP lease _at_all_.
AFAICS ISC's dhcpd has support for it; have a look
On Tue, 2005-04-05 at 14:16 -0700, Marc D. Field wrote:
Hi,
I'm having a problem with NM: Even though my computer is not connected
to an ethernet cable (and my wired interface, eth0, is set NOT to start
at boot), NM brings up eth0 automatically. This, of course, screws-up
my wireless
33 matches
Mail list logo
