No more network after removing network-manager

Just tried the alternate-install-cd of Karmic and installed just a command-line-system, and indeed network-manager was not installed. Strange enough, I had a good functioning network connection. So, I don't get it anymore... Seems like a command line install of just more than 200 MB without network-manager and network-manager-gnome has better network than a full 700 MB CD of which I uninstalled only network-manager and network-manager-gnome!

After that, got to system, tools, network diagnostics and saw the IPv4 was 0.0.0.0
Will now check if the problem also occurs on the full installation of the alternate-install-cd.

Well, I wasn't able to check because of bug #407767.

how could that be a problem with network-manager if the package is not installed?. the bug needs to be reassigned.

It is possible (I can't deny or confirm) that it's not a network-manager problem.
But the question remains: Which package then, is responsible for this problem? I don't know.

The strange thing is, as said earlier: A command line install without network-manager is working just fine,
but a full (approx. 700 MB) Karmic CD without network-manager has no network connection at all.

So, if I'm not mistaken, there must be some packages on the full cd that cause the network connection to be shut down if network-manager is removed. These packages are, apparently, not part of the command-line install, because there, the problem doesn't occur.

Note: I've only tested this with Alpha 3, so if you want me to test a more recent version, just ask me.

did you use /etc/interfaces to configure your network, or did you use network manager?

Sorry, but since when do I have to configure my network?
The only thing I do is selecting dhcp during installation.
That should configure the network automatically, as it has always done before.
So, simply put, I didn't use any of both.

your network always has to be configured, though it sounds like you are used to it being autoconfigured. I suspect that the network in general is autoconfed at least with network-manager and by the installer. If you don't use network-manager to configure your network, then /etc/network/interfaces will be used (and vis a versa).

I'm looking at my interfaces file (jaunty) and it isn't configured even for dhcp, so I wouldn't expect it to work without network-manger or some sort of configuration. It might be a change from previous releases?

So I think you should check your interfaces. BTW, I gave the wrong location, it is /etc/network/interfaces

gl!

Thanks for your reply.

It surely is a change from previous releases. However, the beginning of this problem is already noticeable in Jaunty.
When creating a custom Jaunty live-cd (with remastersys for example), you have to include network-manager or the live-cd won't boot (it gets stuck at configuring network interfaces). If you force it a little, it continues to boot, but you have no network at all on live-cd.

I consider this not really desired, I mean Jaunty works fine without network-manager as long as you install it to your harddrive. But when you use that installation to create a custom live-cd (I mean, the packages on your installation are (mostly) the same as those that will be on the custom live-cd, and network-manager is not one of them), it gives problems (it won't boot, or the network is broken, or both). However, this did not happen before (I'm pretty sure the problem didn't exist with Intrepid (8.10) and very certain it didn't with Hardy (8.04)

So there must have changed something I guess from 8.10 to 9.04 and it seems even worse from 9.04 to 9.10.
You will probably agree that a custom live-cd without network connection isn't very useable.

So, I'm gonna test Alpha 6 as soon as it's available (maybe today, or otherwise this weekend) and see if network-manager is really required to have network connection (it wasn't in the past, but now apparently, it is). I will also try (it's a little risky, I know, because it's still alpha) to make a custom live cd without network-manager. If that one fails to boot, I'll retry with network-manager and let you know the results.

Hello Lieven.
From:
http://www.debian.org/releases/stable/amd64/ch03s01.html.en

The installer software, debian-installer, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses dhcp-client to set up the network connection, runs debootstrap to install the base system packages, and runs tasksel to allow you to install certain additional software.
Can i close this report ?
:)Fabio

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!