I'm seeing this bug too. Using my freshly installed Dapper Flight CD4 install, I don't get any network until I do "sudo dhclient3" (or, as I have understand is better to do, "sudo dhclient eth0").
My system is a Dell Inspiron (Centrino) with both a normal ethernet adapter and Intel Pro/Wireless 2915. I only use the non-wireless eth0 and chose that as the default network adapter during install.
For the record, this worked without any problems in Breezy (final release).
I'm seeing this bug too. Using my freshly installed Dapper Flight CD4 install, I don't get any network until I do "sudo dhclient3" (or, as I have understand is better to do, "sudo dhclient eth0").
My system is a Dell Inspiron (Centrino) with both a normal ethernet adapter and Intel Pro/Wireless 2915. I only use the non-wireless eth0 and chose that as the default network adapter during install.
For the record, this worked without any problems in Breezy (final release).