Yes! I have that... I hav not had time to try your patch yet. Maybe today.
Magnus
Nathaniel McCallum wrote:
On Tue, 2005-06-28 at 18:16 +0200, Magnus Ottosson wrote:
I will try the patch when I get home and see if I can get it working... Did
you also make an ebuild?
Magnus
-Original
On Fri, 2005-07-01 at 08:29 +0200, Magnus Ottosson wrote:
Yes! I have that... I hav not had time to try your patch yet. Maybe today.
I was kind of waiting to apply the gentoo patch until somebody said it
worked, but if you don't get to it today I'll apply it anyway.
Dan
On Fri, 2005-07-01 at 09:11 -0400, Dan Williams wrote:
On Fri, 2005-07-01 at 08:29 +0200, Magnus Ottosson wrote:
Yes! I have that... I hav not had time to try your patch yet. Maybe today.
I was kind of waiting to apply the gentoo patch until somebody said it
worked, but if you don't get to
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
The problem I have found is the dhclient patches from redhat. I solved
this by installing the binaries from redhat. The I used the ebuild from
gentopia (https://dev.cardoe.com/gentopia/) and this actually works
quite well. I hav not had enough time to test it so much but it works
fairly good. But
I think long term that diamond is the best solution.
Nathaniel
On Fri, 2005-07-01 at 18:41 +0200, Magnus Ottosson wrote:
The problem I have found is the dhclient patches from redhat. I solved
this by installing the binaries from redhat. The I used the ebuild from
gentopia
Yo!
Attached patch implements (working) fallback to link-local IP generation
in the case that DHCP fails on a wired or unencrypted wireless network.
Same behavior as Hadess's patch.
The problem with the previous approach is that DHCP timeout is caught in
the other Stage 4, IP Configure Timeout,
Hi Ho!
nm_system_device_set_ip4_route_with_iface() will fail if ip4_gateway
is zero. Zero is not a legal gateway and the ioctl will return EINVAL.
The problem is, the zeroconf IP stuff (and possibly other places) set
the gateway to zero to mean no gateway. But
On Fri, 2005-07-01 at 15:37 -0400, Robert Love wrote:
Hi Ho!
nm_system_device_set_ip4_route_with_iface() will fail if ip4_gateway
is zero. Zero is not a legal gateway and the ioctl will return EINVAL.
The problem is, the zeroconf IP stuff (and possibly other places) set
the gateway to
On Thu, 2005-06-30 at 14:34 -0400, Dan Williams wrote:
NetworkManager doesn't have the infrastructure to do this right now
either. The target use-case for NetworkManager right now is for laptop
users who are fairly mobile.
Nod.
Any comment on the patch, then?
It's a bit hard to imagine a
FYI, I think this patch (against 0.3) fixes this problem.. It looks
like the issue is an ordering issue and the fact that it's using
strncmp() to find the right AP. This is why it works sometimes and
not others, it's order dependent. If I have 'foo' before 'foo-a' the
it will always find 'foo'
Im trying to get NetworkManager running on a Chinese
linux distribution using the 0.3 stable branch pulled from CVS. I have
run into two different problems. When I run NetworkManagerInfo, a space
for the applet appears on the notification bar, but no images appear.
There isnt a radar
12 matches
Mail list logo
