[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#182849: net install - no DHCP after reboot



Hello Thomas

Please cc debian-boot, since I am not
experienced with the net install images, and the people reading -boot are in
fact the ones which built those images.

Thomas Pohl wrote:

> Andreas Wüst wrote:
>
>> Hi Thomas
>> 
>> Thomas Pohl wrote:
>> 
>>  
>> 
>>> Package: install-doc
>>> Version: 3.0.24
>>> 
>>> Installing Debian GNU/Linux 3.0 For Intel x86
>>> version 3.0.24, 18 December, 2002
>>> http://www.debian.org/releases/stable/i386/ch-init-config.en.html
>>> 
>>> Moin,
>>> 
>>> i made a installation with http on my new computer. DHCP was used. 
>>> After rebooting DHCP was not used.
>>>    
>>> 
>> 
>> I don't understand. Was it not used because it didn't work, because you
>> didn't want it to be used, or because you broke it?
>> 
> OK, i try again to describe what i did.
> 
> If you want any log files (and tell me where to find) i can send it to you.
> 
> 1. download the net boot iso image and burn a boot CD

Just a short question: did you download the testing net install image or the stable net
install image?

> 2. buy a new Computer (i guess this is optional :-)
>    P4 2,4, 512MB, Asus P4PE,  onboard ADI AD1980 audio, Broadcom BCM 
> 4401 Ethernet, ser, par, usb
>    maxtor 120GB IDE, USB intelli Explorer Mouse, PS/2 Keyboard with 
> logo, Geforce4 Ti4200 128MB,
> 3. boot from CD but network is not found
> 4. put in 3Com 905B network card
> 5. Boot from CD , press F3 for net install
> 6. follow instructions and choose DHCP, http, www.uni-koeln.de, testing 
> (Sarge)

Why did you choose testing? I guess it would have been sensible to install
woody (stable) if you are using the stable net install images. Once installed,
you can always

    apt-get update
    apt-get dist-upgrade

to sarge (after providing the testing lines in sources.list).

If you installed using the testing images, don't expect it to work flawlessly
since it is still under development. From an earlier post to this list:

    > I read through the install documents and found nothing anywhere near
    > describing how to use this CD.
    >
    You obviously have grabbed a CD with the new installer
    (debian-install, d-i for short). It's not yet in a state for general
    consumption. If you want to install sarge, it'd be best to grab a
    woody (netinst) CD and dist-upgrade to sarge (or unstable).


> 7. some downloading
> 8. request for rebooting, put out boot CD
> 9. boot
> 10. script is going on, but no network
> 11. made some brainstorming what to do, searched around, ifconfig eth0 
> showed not IP adress
> 12. go and get my Laptop an ask google how to set up network with DHCP - 
> found posted link
> 13. open /etc/network/interfaces with vi - was empty, only to comment lines
> 
>    # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
>    # /usr/share/doc/ifupdown/examples for more information
> 
> 14. added this lines - installed no additional packages:
> 
>    auto eth0
>    iface eth0 inet dhcp
>    hostname tpo
> 
> 15. reboot
> 16. http install is working (had fun!).
> 17. debian is working - gnome, mozilla etc, KDE is not working but this 
> is an other story - i am still reading documentation about this.
> 
>> If you chose DHCP during the first part of the installation, your
>> interfaces will be configured using DHCP every time you switch on your
>> computer.
>> 
> no, i think that's the problem !
> 
>>    1. Your computer is trying to configure the interfaces during boot, but
>> you don't have any cable plugged in or your dhcp server isn't working. 
>> 
> DHCP was up an working, network was plugged in

Ok. Since you hadn't had the corresponding lines in interfaces, it is clear
that the networking scripts didn't configure it.

>> process. I can't imagine you wouldn't notice that booting takes extremely
>> long.
>> 
> long is relativ, it's my first debian net install - i do not remember
> (but a internet OS install give's me some crazy feeling of future is now 
> - remembering this disk jockey installs :-)

With long I mean you would have been annoyed by the boot process, but since
you aren't, it shouldn't be the case.

>> But if it does like that, and you'd like to configure the interfaces later
>> on
>> and not during boot (which is quite a natural setup for notebooks btw.),
>> the problem seems to be that
>> 
>>    2. You don't know how to manually bring up the interfaces. Well, no
>> worrying, just issue
>> 
>>            # ifup eth0
>> 
>>    to bring it up (eth0 or whatever, eth1, etc.). Note that this DOES
>> automatically use
>> DHCP if you chose DHCP during the installation process.
>> 
>>            #ifdown eth0
>> 
>>    to stop it (as before, eth0 or whichever your favorite interface is).
>> 
>> If this isn't the case, there could be a third problem,
>> 
>>    3. The kernel you are using isn't compiled with
>> 
>>            CONFIG_PACKET=y and
>>            CONFIG_FILTER=y
>> 
>>        This stuff is needed for the dhcp client to operate AFAIK.
>>  
>> 
> hmm, i am afraid i do not know what kind of kernel i get. i took what 
> ever the download was giving me.

Well, if it works manually by ifup/down then the kernel shouldn't be the
problem.

>>> Google found a nice text from Martin Rasp about howto configure DHCP on 
>>> a Debian.
>>> maybe you can use this part for the install-doc.
>>> 
>>> -part of http://www.linux-fuer-alle.de/doc_show.php?docid=8------------
>>> 
>>> Auf meinem Arbeitsrechner musste ein DHCP-Client installiert sein. Das 
>>> Paket "pump" war bereits durch die Debian-Installation verfügbar. 
>>> Ansonsten hätte ich es nachträglich mit dem folgenden Kommando 
>>> installieren müssen:
>>> 
>>> | apt-get install pump |
>>>    
>>> 
>> 
>> Well, pump is not being used for woody installation dhcp, is it?
>> 
> don't know i tryed without installing additional packages

Ok, that's fine!

>>> Anschließend editierte ich die Datei "/etc/network/interface
>>> 
>>> ### /etc/network/interfaces 
>>> #################################################
>>> 
>>> auto eth0
>>> iface eth0 inet dhcp
>>> hostname speedy
>>> 
>>> #############################################################################
>>>    
>>> 
>> 
>> If you chose DHCP during the first part of the installation, you get a
>> /etc/networking/interfaces looking like this:
>> 
>> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>> 
>> # The loopback interface
>> auto lo
>> iface lo inet loopback
>> 
>> # The first network card - this entry was created during the Debian
>> installation auto eth0
>> iface eth0 inet dhcp
>> 
> no, file had only comments
> 
>> This will cause the networking script to try to configure the interface
>> eth0 using a dhcp client.
>> 
>> If you don't want to have the networke started automatically during boot
>> time, you can comment out the "auto eth0" to look something like this
>> 
>> # auto eth0
>> iface eth0 inet dhcp
>> 
>> Now you have to bring up the interfaces manually by using the ifup and
>> ifdown scripts as described above. I also suggest to have a look at man
>> interfaces.
>> 
>>  
>> 
>>> Über den folgenden Befehl startete ich das Netzwerk neu:
>>> 
>>>   /etc/init.d/networking restart |
>>>    
>>> 
>> 
>> Yeah, or ifup ifdown.
>>  
>> 
> at this moment i am happy that i have my network somehow running, i am 
> afraid i have to find out how to configure it correct.
> at the end it should have a fixed network adress a hostname ,

Is this required by your dhcp ntwork setup? You can also fetch a dynamic
hostname if your dhc server is configured for this.

> My first steps in Linux were made with SUSE and there is this yast tool 
> doing a lot of work for newbies.
> 
>> So, finally, I would not suggest to include the above mentioned text in the
>> installer manual, as it should not be needed if everything works the way it
>> is intended to do. If it doesn't work like that, this is a software bug and
>> shouldn't be cured by simply telling the user to fsck around with the
>> interfaces script.
>> 
> sounds logical to me ...
> 
>> 
>> But, altough a bit off topic, but in this context it came to my mind, I
>> would strongly suggest to add a requester during the first part of the
>> installation, after being asked if the user wants to use dhcp for interface
>> configuration, a requester which now asks if the user does also want to
>> have the network brought up immediately during boot time! Because this is
>> seldom useful for notebook and similar configurations. But since the guys
>> are working on a new installer anyway, I guess this would rather be a
>> suggestion for debian-installer instead of boot-floppies.
>>  
>> 
> i think it's not only notebook, the amount of people behind routers with 
> DHCP or behind some Microsoft ICS is growing.

Amen.

> thanks for helping !!!
> 
> Thomas

-- 
Best wishes,
Andi



Reply to: