Ian Campbell wrote:
>> 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 ne
Ian Campbell wrote:
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 fixe
> 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
On Thu, 2006-03-02 at 10:59 -0400, Ian Campbell wrote:
> > 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=meth
On Thu, 2006-03-02 at 10:52 -0400, Ian Campbell wrote:
> 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
> 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
On Thu, 2006-03-02 at 07:20 -0400, Ian Campbell wrote:
> > 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:0
> 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
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 know about in advance."
With -x in dhclient do you have problem?
>I'm having a s
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
Hi Ian,
It's possibly not related to my problem but are you using a shared
key(restricted)?
Rob.
Ian Campbell wrote:
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)b
NetworkManager will set the essid a
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
14 matches
Mail list logo
