Wireless

[Brian Anderson]

Sorry, I realize I'm not being clear.  My earlier mail pointed to a 
"message handler" but that seems harmless in that it occurs with both 
versions of NM.  The "dev != NULL" message seem relevant since they only 
occur with the 0.5.1-10 version of NM.

Brian Anderson wrote:

> Well, I've been doing a bit more investigation of this.  I am using 
> the madwifi-ng driver (svn revision 1443) which was working fine with 
> NetworkManager-0.5.1-8.cvs20060131, but stops working with 
> NetworkManager-0.5.1-10.cvs20060205.  I reverted to the previous 
> version and NM connects.
>
> The message handler error I mentioned below appears for both versions, 
> so it seems to be harmless.  The messages that appear for the new 
> version and not in the old are:
>
> NetworkManager: nm_device_is_802_3_ethernet: assertion 'dev != NULL' 
> failed
> NetworkManager: nm_device_is_802_11_wireless: assertion 'dev != NULL' 
> failed
>
> any ideas?
>
> Brian Anderson wrote:
>
>> Before today's rawhide NM was working OK for me, but after today 
>> (2/6) I too see behavior where the IP address isn't being picked up.  
>> NM shows all the APs in my area and attempts to connect, but fails.  
>> The notable message I get is:
>> dhcdbd: message_handler: message handler not found under 
>> /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
>>
>> it appears regardless of whether enforcement is on or not (just in 
>> case there was a suspicion it was selinux related).
>> NM doesn't seem to have a problem with eth0 though.
>>
>>
>>
>> Don Springall wrote:
>>
>>> After today's rawhide update dhclient is started at boot time and 
>>> does not pick up an ip address.  So instead of doing an /sbin/ifup 
>>> eth1 I have to do a /sbin/ifdown eth1 first before bringing up the 
>>> wireless card.
>>>
>>> I have never been able to get the system to start the interface 
>>> correctly I think because it tries to determine an IP address before 
>>> network-manager is up and running.
>>>
>>> Anyone have any insights on what I should change ? My ifcfg-eth1 is 
>>> below.
>>>
>>> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
>>> # for the documentation of these parameters.
>>> ONBOOT=no
>>> USERCTL=yes
>>> IPV6INIT=no
>>> PEERDNS=yes
>>> TYPE=Wireless
>>> DEVICE=eth1
>>> HWADDR=00:13:10:6a:ea:b7
>>> BOOTPROTO=dhcp
>>> NETMASK=
>>> DHCP_HOSTNAME=
>>> IPADDR=
>>> DOMAIN=
>>> ESSID=WirelessCity
>>> CHANNEL=1
>>> MODE=Managed
>>> RATE=Auto
>>>
>>> [root at localhost network-scripts]# /sbin/ip addr
>>> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>>>    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>>    inet 127.0.0.1/8 scope host lo
>>>    inet6 ::1/128 scope host
>>>       valid_lft forever preferred_lft forever
>>> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc 
>>> pfifo_fast qlen 1000    link/ether 00:02:3f:8a:a5:1f brd 
>>> ff:ff:ff:ff:ff:ff
>>> 3: sit0: <NOARP> mtu 1480 qdisc noop
>>>    link/sit 0.0.0.0 brd 0.0.0.0
>>> 4: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>>>    link/ether 00:13:10:6a:ea:b7 brd ff:ff:ff:ff:ff:ff
>>>    inet 172.17.186.240/16 brd 172.17.255.255 scope global eth1
>>>    inet6 fe80::213:10ff:fe6a:eab7/64 scope link
>>>       valid_lft forever preferred_lft forever
>>> [root at localhost network-scripts]#
>>>
>>>
>>
>

-- 
.   __o    Brian "la lumaca"
  _`\<,_
 (*)/ (*)