Created attachment 57811 [details]
YaST2 logs

Created attachment 57812 [details]
/var/log/messages

You can use dhcp or NetworkManager but AFAIK not both.

I did not change any network related settings during installation...

Peter, does it work for you if you switch the network interface(s) to "Managed by NetworkManager"?

No, it did not work.
But when I followed the suggestion from http://lists.opensuse.org/archive/opensuse-factory/2005-Nov/0031.html and deleted NetworkManager, then all of my networking troubles were solved.

Please be a little more verbose and explain "no did not work".

Did not work := eth0 did not get an IP address, gw, DNS, etc.
After deleting networkmanager, everything was OK, and worked as expected.

Would you mind giving it a second run?

* Install NM
* Set interfaces to 'managed'
* rcnetwork stop
* rcnetwokmanager restart

I never have seen one with a network device which NM could not configure using DHCP.

I did it now, and it still does not work.
What logs should I send? YaST2 + /var/log/messages?

BTW: if I set it to 'managed', how can I set a static IP?

> What logs should I send? YaST2 + /var/log/messages?

Could you please stop NM and afterwards attach the output of

   $ NetworkManager --no-daemon

to this bug.  Thanks.

> BTW: if I set it to 'managed', how can I set a static IP?

Static configurations are set using YaST (as before).  The device should _not_ set to "manageed".  Once NM is started, it is taking such configurations into account and does _not_ try to configure the device using DHCP but is setting the static configuration.

Created attachment 58367 [details]
NetworkManager log

It does not get an IP address, so it assigns something random, as I see. It should receive: 192.168.2.193 from an SMC broadband router, and it works correctly if NetworkManager is deleted.

Created attachment 58368 [details]
ps aux after NetworkManager is stopped

This is a ps aux after NetworkManager is stopped. The interesting thing is: the dhcp clients, which were started by NetworkManager are still running. On the next run of NM, it posts an error message about it each second.

One more remark. You asked me to 'rcnetwork stop'. I thought, that 'insserv -r network' and I dont' have to stop it any more. But it seems to be a hard coded dependency for a lot of packages:

insserv: Service network has to be enabled for service syslog
insserv: Service network has to be enabled for service smbfs
insserv: Service network has to be enabled for service nfs
insserv: Service network has to be enabled for service portmap
insserv: Service network has to be enabled for service sendmail
insserv: Service network has to be enabled for service postfix
insserv: Service network has to be enabled for service nfsboot
insserv: Service network has to be enabled for service sshd
insserv: Service network has to be enabled for service rendezvous
insserv: exiting now!

(In reply to comment #12)
 
> It does not get an IP address, so it assigns something random,

NM is falling back to zeroconf since the DHCP transaction takes too long.

> as I see. It
> should receive: 192.168.2.193 from an SMC broadband router, and it works
> correctly if NetworkManager is deleted.

Does your DHCP server of the SMC router provide DNS server(s) via DHCP?

Strange, when I don't use NetworkManager, just good, old YaST2, I get an IP within seconds.

Yes, it provides DNS servers as well.

(In reply to comment #13)

> This is a ps aux after NetworkManager is stopped. The interesting thing is: the
> dhcp clients, which were started by NetworkManager are still running. On the
> next run of NM, it posts an error message about it each second.

I could not reproduce this on a box with Alpha3.  Once NetworkManager is stopped, all dhclient processes are gone, too.  Maybe it relates to the timeout you encounter. 

(In reply to comment #16)
> Strange, when I don't use NetworkManager, just good, old YaST2, I get an IP
> within seconds.
> 
> Yes, it provides DNS servers as well.

OK. Good to know, otherwise it this bug would be related to #134369.

What hapens if you remove /etc/sysconfig/network/ifcfg-* file for your device and restart NetworkManager?

The same result. Looking at /var/log/messages (which I have already posted once), I found this:

Nov 23 11:27:19 czp dhclient: /etc/dhclient.conf line 34: expecting a statement.
Nov 23 11:27:19 czp dhclient: 
Nov 23 11:27:19 czp dhclient: ^

I have a stock dhclient config:

czp:~ # cat /etc/dhclient.conf~
# dhclient configuration file
# see "man dhclient.conf" for further details
# file: /etc/dhclient.conf
#


######################################################
# Suggested configurations for Cable Modem providers #
#
# uncomment and fill in the appropriate section

#####################################################
# @Home -- TCI, etc
#
# Uncomment the following line and enter your Client ID, which should
# have come in your mail from @Home
#
# send dhcp-client-identifier "c32423-a"

#send host-name "andare.fugue.com";
#send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
#supersede domain-name "fugue.com home.vix.com";
#prepend domain-name-servers 127.0.0.1;

send dhcp-lease-time 3600;
request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, host-name;
require subnet-mask, domain-name-servers;
timeout 60;
retry 60;
reboot 10;
select-timeout 5;
initial-interval 2;
script "/sbin/dhclient-script";

#media "-link0 -link1 -link2", "link0 link1";
#reject 192.33.137.209;

(In reply to comment #19)

> czp:~ # cat /etc/dhclient.conf~
                                ^- ? Did you want to cat this file?

Yes. I removed comment lines from /etc/dhclient.conf to see, if that changes anything (sometimes lines starting with # were used in config files (which is a bug of course), and ~ is the original, after editing with joe). But it did not change anything.

OK, line 34 looks very sane, though. What happens if you remove the line with

   SCRIPT "/sbin/dhclient-script";

?

(In reply to comment #22)
> OK, line 34 looks very sane, though. What happens if you remove the line with
> 
>    SCRIPT "/sbin/dhclient-script";

Anything I remove, I get the same warning message for the last line containing configuration.

Peter, do you have an idea what is going wrong regarding dhclient?

No. I also tried the sample config from 'man dhclient.conf' with the same result...

Looks as if dhclient is broken on ppc >= 10.0.

It works when compiled with -fsigned-char on ppc/ppc64 (as it used to be
in RPM_OPT_FLAGS before).

It is fixed in STABLE/edge/factory. 

Andreas: should we fix it for 10.0-ppc?

Yes, update for 10.0-ppc is approved, swampid is:  	 Maintenance-Tracker-3027

Update and patchinfo submitted.

I have tried 'factory' as of 2005 dec. 8. and it works fine.

Thank you!

released