Re: NM 0.7.0.100 and Slackware

[Sasa Ostrouska <casaxa gmail com>]

On Thu, Apr 9, 2009 at 11:21 PM, Sasa Ostrouska <casaxa gmail com> wrote:
> On Thu, Apr 9, 2009 at 11:14 PM, Dan Williams <dcbw redhat com> wrote:
>> On Thu, 2009-04-09 at 22:58 +0200, Sasa Ostrouska wrote:
>>> On Thu, Apr 9, 2009 at 10:27 PM, Michael Biebl <biebl debian org> wrote:
>>> > Sasa Ostrouska wrote:
>>> >> Dear Michael,
>>> >
>>> > Hi Sasa, please keep the mailing list in CC
>>>
>>> Hehe, didnt even know that I have mailed you directly :) sorry, will
>>> pay more attention on that :)
>>>
>>> >
>>> >> On Thu, Apr 9, 2009 at 12:26 PM, Michael Biebl <biebl debian org> wrote:
>>> >>> Sasa Ostrouska wrote:
>>> >>>> configure --with-distro=slackware \ --with-docs \
>>> >>>> --with-dbus-sys=/etc/dbus-1/system.d \ --with-dhcp-client=dhcdbd \
>>> >>> ^ That doesn't look right, you either want dhclient or dhcpcd here
>>> >>>
>>> >> Corrected it to be dhcpcd
>>> >>
>>> >>>> --with-pppd-plugin-dir=/etc/ppp/plugins \
>>> >>> ^ That is incorrect, too. pppd plugins are usually installed in
>>> >>> /usr/lib/ppp/$ppp_version
>>> >>>
>>> >> Corrected it to point to /usr/lib/pppd/2.4.4
>>> >>
>>> >>>> --with-resolvconf=/etc/resolv.conf \
>>> >>> ^ Here, you should use the path to the resolvconf *binary*. I'm not sure if
>>> >>>  slackware supports resolvconf, so you probably don't want this configure
>>> >>> option.
>>> >>>
>>> >>
>>> >> You are wright about that, so I cut of that line.
>>> >>
>>> >> So here is another nm-serial3.txt file attached with the output I got after
>>> >> recompilling it with the right options.
>>> >
>>> >
>>> > ...
>>> >
>>> >> NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
>>> >> NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
>>> >> NetworkManager: <info>  (eth0): device state change: 5 -> 7
>>> >> NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
>>> >> eth0: dhcpcd 4.0.12 starting
>>> >> NetworkManager: <info>  dhcpcd started with pid 15991
>>> >> NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
>>> >> Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.59" is not allowed to own the service "org.freedesktop.nm_dhcp_client" due to security policies in the configuration file
>>> >> eth0: broadcasting for a lease
>>> >> eth0: offered 192.168.1.104 from 192.168.1.1
>>> >> eth0: acknowledged 192.168.1.104 from 192.168.1.1
>>> >> eth0: checking 192.168.1.104 is available on attached networks
>>> >> eth0: leased 192.168.1.104 for 259200 seconds
>>> >> Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.61" is not allowed to own the service "org.freedesktop.nm_dhcp_client" due to security policies in the configuration file
>>> >> NetworkManager: <info>  Device 'eth0' DHCP transaction took too long (>45s), stopping it.
>>> >> eth0: received SIGTERM, stopping
>>> >> Error: Could not acquire the NM DHCP client service. Message: (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.62" is not allowed to own the service "org.freedesktop.nm_dhcp_client" due to security policies in the configuration file
>>> >> NetworkManager: <info>  eth0: canceled DHCP transaction, dhcp client pid 15991
>>> >
>>> > So, this looks much better now.
>>>
>>> Good to hear that.
>>> >
>>> > As a next step, please make sure, the NetworkManager dbus policy files  are
>>> > installed in /etc/dbus-1/system.d/ and dbus is reloaded/restarted afterwards.
>>> >
>>> >
>>> > Michael
>>> >
>>>
>>> Ok will check all that dbus stuff if it is in, from what I know it
>>> should be in, but its better to recheck twice.
>>> Another thing it makes me mad, is why every time I start NM it resets
>>> my hostname to localhost.localdomain ????
>>>
>>> After that is really impossible to do anything on the machine.
>>
>> The next thing you want to do is write a Slackware system settings
>> plugin that will read wherever Slackware stores the persistent hostname,
>> and provide that hostname to NetworkManager.  Then implement reading of
>> the normal slackware network config scripts so NM can transparently use
>> the existing system network config.
>>
>> That will make your problem here go away.  The problem is that nothing
>> is telling NM what your intended hostname should be.
>>
>> Dan
>
> Dan ,that sounds great, but can somebody advise on where and how to begin ?
>
> Rgds
> Saxa
>

Ok I did some more testings and thats what I get now with
wpa_supplicant started.

Thats the contents of my /etc/dbus-1/system.d/

-rw-r--r-- 1 root root 4473 2009-04-03 01:53
/etc/dbus-1/system.d/ConsoleKit.conf
-rw-r--r-- 1 root root 1183 2009-04-09 16:50
/etc/dbus-1/system.d/NetworkManager.conf
-rw-r--r-- 1 root root  948 2009-03-19 06:40
/etc/dbus-1/system.d/avahi-dbus.conf
-rw-r--r-- 1 root root 1131 2008-11-11 23:36 /etc/dbus-1/system.d/bluetooth.conf
-rw-r--r-- 1 root root  460 2008-10-22 01:15 /etc/dbus-1/system.d/cups.conf
-rw-r--r-- 1 root root  695 2008-04-02 22:25
/etc/dbus-1/system.d/dbus-wpa_supplicant.conf
-rw-r--r-- 1 root root  589 2008-09-01 02:38 /etc/dbus-1/system.d/dhcdbd.conf
-rw-r--r-- 1 root root 3891 2009-03-21 20:20 /etc/dbus-1/system.d/gdm.conf
-rw-r--r-- 1 root root 2091 2008-12-08 02:14 /etc/dbus-1/system.d/hal.conf
-rw-r--r-- 1 root root  792 2007-12-30 18:30
/etc/dbus-1/system.d/newprinternotification.conf
-rw-r--r-- 1 root root 1976 2009-04-05 13:22 /etc/dbus-1/system.d/nm-applet.conf
-rw-r--r-- 1 root root  475 2009-04-09 16:50
/etc/dbus-1/system.d/nm-avahi-autoipd.conf
-rw-r--r-- 1 root root  455 2009-04-09 16:50
/etc/dbus-1/system.d/nm-dhcp-client.conf
-rw-r--r-- 1 root root  465 2009-04-09 16:50
/etc/dbus-1/system.d/nm-dispatcher.conf
-rw-r--r-- 1 root root  492 2009-03-24 16:29
/etc/dbus-1/system.d/nm-openvpn-service.conf
-rw-r--r-- 1 root root  734 2009-03-24 16:32
/etc/dbus-1/system.d/nm-pptp-service.conf
-rw-r--r-- 1 root root  702 2009-04-09 16:50
/etc/dbus-1/system.d/nm-system-settings.conf
-rw-r--r-- 1 root root  480 2009-03-24 16:36
/etc/dbus-1/system.d/nm-vpnc-service.conf
-rw-r--r-- 1 root root 1025 2009-04-03 02:46
/etc/dbus-1/system.d/org.freedesktop.DeviceKit.Power.conf
-rw-r--r-- 1 root root  453 2009-04-03 02:44
/etc/dbus-1/system.d/org.freedesktop.DeviceKit.conf
-rw-r--r-- 1 root root  365 2009-04-03 02:16
/etc/dbus-1/system.d/org.freedesktop.PolicyKit.conf
-rw-r--r-- 1 root root  497 2009-04-08 15:49
/etc/dbus-1/system.d/org.gnome.CPUFreqSelector.conf
-rw-r--r-- 1 root root  591 2009-03-19 10:34
/etc/dbus-1/system.d/org.gnome.ClockApplet.Mechanism.conf
-rw-r--r-- 1 root root 2803 2009-01-30 18:09
/etc/dbus-1/system.d/system-tools-backends.conf
-rw-r--r-- 1 root root  848 2008-09-21 01:38
/etc/dbus-1/system.d/system-tools-backends.conf.old
-rw-r--r-- 1 root root 2786 2009-01-30 18:08
/etc/dbus-1/system.d/system-tools-backends.conf~
-rw-r--r-- 1 root root  810 2008-12-04 11:01 /etc/dbus-1/system.d/wicd.conf

Hre is what the syslog says:

Apr  9 23:12:28 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:13:15 rc-samsung NetworkManager: <WARN>
nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
Sucess
Apr  9 23:13:19 rc-samsung NetworkManager: <WARN>  check_one_route():
(eth0) error -34 returned from rtnl_route_del(): Sucess
Apr  9 23:13:20 rc-samsung nm-dispatcher.action: nm_dispatcher_action:
Invalid connection: '(null)' / 'connection setting not found' invalid:
1
Apr  9 23:13:21 rc-samsung gnome-keyring-ask: Gtk: cannot open display: :0.0
Apr  9 23:13:21 rc-samsung gnome-keyring-daemon[9113]: missing dialog
response from ask tool
Apr  9 23:13:21 rc-samsung NetworkManager: <WARN>  get_secrets_cb():
Couldn't get connection secrets: applet.c.2111
(applet_settings_new_secrets_requested_cb): couldn't find details for
connection.
Apr  9 23:14:57 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:15:06 rc-samsung gnome-keyring-ask: Gtk: cannot open display: :0.0
Apr  9 23:15:06 rc-samsung gnome-keyring-daemon[9113]: missing dialog
response from ask tool
Apr  9 23:15:06 rc-samsung gnome-keyring-ask: Gtk: cannot open display: :0.0
Apr  9 23:15:06 rc-samsung gnome-keyring-daemon[9113]: missing dialog
response from ask tool
Apr  9 23:15:07 rc-samsung gnome-keyring-ask: Gtk: cannot open display: :0.0
Apr  9 23:15:07 rc-samsung gnome-keyring-daemon[9113]: missing dialog
response from ask tool
Apr  9 23:15:08 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:15:16 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:15:24 rc-samsung NetworkManager: <WARN>
nm_dhcp_manager_handle_event(): Received DHCP event from unexpected
PID 9625 (expected 0)
Apr  9 23:15:24 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:15:31 rc-samsung dnsmasq[3100]: no servers found in
/etc/resolv.conf, will retry
Apr  9 23:15:51 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.
Apr  9 23:16:33 rc-samsung NetworkManager: <WARN>
nm_signal_handler(): Caught signal 2, shutting down normally.
Apr  9 23:16:33 rc-samsung dnsmasq[3100]: no servers found in
/etc/resolv.conf, will retry
Apr  9 23:16:33 rc-samsung NetworkManager: <WARN>  check_one_route():
(eth0) error -34 returned from rtnl_route_del(): Sucess
Apr  9 23:16:34 rc-samsung nm-dispatcher.action: Error in
get_property: Message did not receive a reply (timeout by message bus)
Apr  9 23:16:34 rc-samsung pulseaudio[9132]: module-alsa-sink.c: ALSA
woke us up to write new data to the device, but there was actually
nothing to write! Most likely this is an ALSA driver bug. Please
report this issue to the PulseAudio developers.

And here is the NM started from the terminal:

NetworkManager: <info>  starting...
-- Error received: File exists
-- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC>
sequence-nr=1239311600 pid=4203909
NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17
returned from rtnl_addr_add():
Sucess

NetworkManager: <info>  (eth0): new Ethernet device (driver: 'sky2')
NetworkManager: <info>  (eth0): exported as
/org/freedesktop/Hal/devices/net_00_13_77_af_1f_59
NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'ath5k_pci')
NetworkManager: <info>  (wlan0): exported as
/org/freedesktop/Hal/devices/net_00_21_63_92_af_f6
NetworkManager: <info>  Trying to start the system settings daemon...
NetworkManager: <info>  (eth0): carrier now ON (device state 1)
NetworkManager: <info>  (eth0): device state change: 1 -> 2
NetworkManager: <info>  (eth0): preparing device.
NetworkManager: <info>  (eth0): deactivating device (reason: 2).
NetworkManager: <info>  Setting system hostname to
'localhost.localdomain' (no default device)
-- Error received: Numerical result out of range
-- Original message: type=0x19 length=56 flags=<REQUEST,ACK>
sequence-nr=1239311609 pid=4203909
NetworkManager: <WARN>  check_one_route(): (eth0) error -34 returned
from rtnl_route_del(): Sucess

NetworkManager: <info>  (wlan0): device state change: 1 -> 2
NetworkManager: <info>  (wlan0): bringing up device.
NetworkManager: <info>  (wlan0): preparing device.
NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
NetworkManager: <info>  (eth0): device state change: 2 -> 3
NetworkManager: <info>  (wlan0): device state change: 2 -> 3
NetworkManager: <info>  Activation (eth0) starting connection 'office-italy'
NetworkManager: <info>  (eth0): device state change: 3 -> 4
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) started...
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) complete.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info>  (eth0): device state change: 4 -> 5
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) successful.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) scheduled.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager: <info>  (eth0): device state change: 5 -> 7
NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
eth0: dhcpcd 4.0.12 starting
NetworkManager: <info>  dhcpcd started with pid 9625
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
NetworkManager: <info>  DHCP: device eth0 state changed (null) -> preinit
NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
eth0: broadcasting for a lease
eth0: offered 192.168.1.104 from 192.168.1.1
NetworkManager: <info>  Activation (wlan0) starting connection 'rcdiostrouska'
NetworkManager: <info>  (wlan0): device state change: 3 -> 4
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device
Prepare) scheduled...
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device
Prepare) started...
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device
Prepare) complete.
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info>  (wlan0): device state change: 4 -> 5
NetworkManager: <info>  Activation (wlan0/wireless): access point
'rcdiostrouska' has security, but secrets are required.
NetworkManager: <info>  (wlan0): device state change: 5 -> 6
NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <WARN>  get_secrets_cb(): Couldn't get connection
secrets: applet.c.2111 (applet_settings_new_secrets_requested_cb):
couldn't find details for connection.
NetworkManager: <info>  (wlan0): device state change: 6 -> 9
NetworkManager: <info>  Activation (wlan0) failed for access point
(rcdiostrouska)
NetworkManager: <info>  Marking connection 'rcdiostrouska' invalid.
NetworkManager: <info>  Activation (wlan0) failed.
NetworkManager: <info>  (wlan0): device state change: 9 -> 3
NetworkManager: <info>  (wlan0): deactivating device (reason: 0).
eth0: acknowledged 192.168.1.104 from 192.168.1.1
eth0: checking 192.168.1.104 is available on attached networks
eth0: leased 192.168.1.104 for 259200 seconds
NetworkManager: <info>  DHCP: device eth0 state changed preinit -> bound
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) started...
NetworkManager: <info>    address 192.168.1.104
NetworkManager: <info>    prefix 24 (255.255.255.0)
NetworkManager: <info>    gateway 192.168.1.1
NetworkManager: <info>    nameserver '192.168.1.1'
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) complete.
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) started...
NetworkManager: <info>  (eth0): device state change: 7 -> 8
NetworkManager: <info>  Policy set 'office-italy' (eth0) as default
for routing and DNS.
NetworkManager: <info>  Activation (eth0) successful, device activated.
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) complete.
NetworkManager: <info>  Trying to start the system settings daemon...
NetworkManager: <info>  (eth0): device state change: 8 -> 3
NetworkManager: <info>  (eth0): deactivating device (reason: 0).
eth0: received SIGTERM, stopping
NetworkManager: <info>  eth0: canceled DHCP transaction, dhcp client pid 9625
NetworkManager: <info>  Activation (eth0) starting connection 'office-italy'
NetworkManager: <info>  (eth0): device state change: 3 -> 4
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) scheduled...
NetworkManager: <WARN>  nm_dhcp_manager_handle_event(): Received DHCP
event from unexpected PID 9625 (expected 0)
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) started...
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) complete.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info>  (eth0): device state change: 4 -> 5
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) successful.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) scheduled.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager: <info>  (eth0): device state change: 5 -> 7
NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
NetworkManager: <info>  dhcpcd started with pid 9748
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
eth0: dhcpcd 4.0.12 starting
NetworkManager: <info>  DHCP: device eth0 state changed normal exit -> preinit
eth0: broadcasting for a lease
eth0: offered 192.168.1.104 from 192.168.1.1
eth0: acknowledged 192.168.1.104 from 192.168.1.1
eth0: checking 192.168.1.104 is available on attached networks
eth0: leased 192.168.1.104 for 259200 seconds
NetworkManager: <info>  DHCP: device eth0 state changed preinit -> bound
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) started...
NetworkManager: <info>    address 192.168.1.104
NetworkManager: <info>    prefix 24 (255.255.255.0)
NetworkManager: <info>    gateway 192.168.1.1
NetworkManager: <info>    nameserver '192.168.1.1'
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure
Get) complete.
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) started...
NetworkManager: <info>  (eth0): device state change: 7 -> 8
NetworkManager: <info>  Policy set 'office-italy' (eth0) as default
for routing and DNS.
NetworkManager: <info>  Activation (eth0) successful, device activated.
NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure
Commit) complete.

It still doesnt work, but at least seems more closer I hope.

Rgds
Saxa