On Mon, May 15, 2006 at 01:15:54PM -0400, Matthew Saltzman wrote:
> On Mon, 15 May 2006, Chris Adams wrote:
>
> >Once upon a time, Gene Heskett <[EMAIL PROTECTED]> said:
> >>I've been advised by someone on this list that this list does it
> >>correctly and the rest of the world is wrong, but frank
Figured I'd give NM 0.6.0 a try with my ipw2100.
Setup wpa_supplicant.conf the way I remembered seeing somewhere on this list,
although for the life of me I can't find it now.
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
wpa_supplicant is
> So how are you doing DHCP then?
>
> NM requests information from dhcdbd, and dhcdbd gets its information
> from the dhclient script. But the dhclient script only gets notified to
> push the information back to dhcdbd if you have a -x aware dhclient.
>
> So, you will need:
>
> 1) dhcdbd
> 2) d
On Thu, Mar 02, 2006 at 10:00:16AM -0500, Dan Williams wrote:
> Right at the top. Make it the first stuff executed for the script,
> though it can be below the comments.
>
> You'll also need to make your dhclient -x aware, and tell dhcdbd to pass
> -x to dhclient.
Thanks, that fixed it.
For any
> Does your dhclient-script have the correct magic to forward DHCP
> information back to dhcdbd?
>
> if [ -n "${dhc_dbus}" ]; then
>/bin/dbus-send \
>--system \
>--dest=com.redhat.dhcp \
>--type=method_call \
>/com/redhat/dhcp/$interface \
>com.redhat.dh
On Thu, Mar 02, 2006 at 12:34:56PM +0100, [EMAIL PROTECTED] wrote:
>
> man dhclient:
> "The -x argument enables eXtended option information to be
> created in the -s dhclient-script environment, which would
> allow applications running in that environment to handle
> options they do not kno
> Same configuration, same problem. It appears to be a problem with
> wpa_supplicant; it is not associating with the AP. I'll try to get a log
> sometime tomorrow, but the basic problem is that wpa_supplicant just
> gets to "Trying 0C:0A:.." (the AP). I'm running the (in)famous
> broadcom/ndisw
On Thu, Mar 02, 2006 at 04:11:17PM +1100, Robert Bertram wrote:
> It's possibly not related to my problem but are you using a shared
> key(restricted)?
Whoops, I meant for this to go to the list too.
No, open.
___
NetworkManager-list mailing list
Netwo
I'm having a strange problem with NetworkManager 0.5.1 and 0.5.2 from
2006-02-21 (The two current builds in the Gentopia portage overlay)
NetworkManager will set the essid and the wep key for the network properly,
it'll get an ip address and set a route, and then it will just... hang there,
spinni
> It's better to discuss Ubuntu NM problems in the Ubuntu bugtracker since
> Ubuntu makes quite a few intrusive changes to Networkmanager. The
> problems most (if not all) Ubuntu users are currently facing is due to
> these changes (and because they don't read the notification bubble on
> updates).
Has anyone else had problems with NetworkManager on Ubuntu Dapper?
I figured I'd take a look at it, but it doesn't seem to be cooperating.
This is a fresh, updated install of Ubuntu. I installed the NetworkManager
package, its requirements, and the nm-applet package. NetworkManager doesn't
see my
> 'Enable Networking' does supersede 'Enable Wireless' in all cases except
> where you want to disable scanning, but not all networking. I think
> this is a valid use case.
>
> Disabling all networking has two primary uses: As a "lock down" or
> "flight mode" and in the case of performing a clea
A wireless network I use has a space in the essid. Every time
NetworkManager tries to associate to it, it crashes. The association
succeeds, NetworkManager restarts, and everything continues as it was
before.
Is there any reason NetworkManager would crash on a network with a
space
I'm not sure if this is the appropriate forum for this, but hey.
I'm having two separate problems with the 20051209 CVS. One is that
while it can see the networks, it doesn't seem to be properly changing
the ssid on the cards when I attempt to connect. I'm not sure if this is
because
14 matches
Mail list logo
