Bug#903320: debian-installer: drops ULA address after network setup

(from this prefix or from other ones), provided iptables allows the forwarding. However, d-i behaves in a way that prevents it to run successfully in this network. During the network setup, it does indeed get both addresses, sets up routes accordingly, and also gets other settings from the DHCP

Re: netinst network setup

Jude DaShiell (2016-11-17): > If a netinst version of the installer connects with the internet would it be > possible to have a version as part of the installation process at least give > the installer the option to save those network settings in > /etc/network/interfaces so

netinst network setup

If a netinst version of the installer connects with the internet would it be possible to have a version as part of the installation process at least give the installer the option to save those network settings in /etc/network/interfaces so if that option were chosen the post-install debian

Bug#779794: installation-reports: netinst hangs between network setup and user setup

Hi Shane, It would be nice if you could extract /var/log/syslog when the hang happens. Mraw, KiBi. I can see the syslog by alt-f2 when it freezes, but it will not save anywhere permanent because the setup iso is un-writable. I have it actually on a usb so it should not be physically

Bug#779794: installation-reports: netinst hangs between network setup and user setup

, and any thoughts, comments and ideas you had during the initial install. The installation hangs between the network setup phase and the user creation phase, as best I can tell. It stays on a blue screen that allows me to type but does not respond to commands. alt-f2 gets me to emergency

Bug#779794: Acknowledgement (installation-reports: netinst hangs between network setup and user setup)

$ lspci00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express

Bug#779794: installation-reports: netinst hangs between network setup and user setup

the initial install. The installation hangs between the network setup phase and the user creation phase, as best I can tell. It stays on a blue screen that allows me to type but does not respond to commands. alt-f2 gets me to emergency command line, but I really have no idea where to go from

Bug#688650: debian-installer: Wrong IP added to interfaces config file if you go back to network setup menu

Package: debian-installer Version: 20110106+squeeze4+b1 Severity: normal During the install you setup the IP informatio manually, then if you go back to the network setup screen and change the IP information the install doesn't add the new IP to the interfaces file, instead it creates the file

Bug#685127: installation-report: Wheezy beta installed on AMD64, network setup failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: installation-reports Version: 2.47 Severity: normal Dear Maintainer, - -- Package-specific info: Boot method: DVD Image version: http://hammurabi.acc.umu.se/cdimage/weekly-builds/amd64/iso-dvd/debian-testing-amd64-DVD-1.iso Date:

Bug#685127: marked as done (installation-report: Wheezy beta installed on AMD64, network setup failed)

Your message dated Fri, 17 Aug 2012 21:28:23 +0200 with message-id 20120817192823.gg5...@mykerinos.kheops.frmug.org and subject line Re: Bug#685127: installation-report: Wheezy beta installed on AMD64, network setup failed has caused the Debian Bug report #685127, regarding installation-report

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

[Joey Hess] Attached patch implements that. Please test. I managed to get hold of the HP Mini again, and tested the svn version of check-missing-firmware.sh. The version solved the problem, and the PXE installation no longer failed because the network settings were lost. :) Now it failed

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

Petter Reinholdtsen p...@hungry.com writes: [Joey Hess] Attached patch implements that. Please test. I am unable to test. The Debian Edu developer gathering is over, and the test machines have been placed back into their storage boxes. :( I've got access to Dell PE2650 machines with

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

Ferenc Wagner wrote: I've got access to Dell PE2650 machines with Tigon3 cards, which also work without the TSO firmware. I could probably seize one for testing if needed. I'd appreciate that. Ping me if you need a boot image for testing. -- see shy jo signature.asc Description: Digital

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

Joey Hess jo...@debian.org writes: Ferenc Wagner wrote: I've got access to Dell PE2650 machines with Tigon3 cards, which also work without the TSO firmware. I could probably seize one for testing if needed. I'd appreciate that. Ping me if you need a boot image for testing. Looks like I

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

Package: installation-reports Version: 2.43 Severity: important User: debian-...@lists.debian.org UserTags: debian-edu Boot method: network / PXE via TP cable Image version: PXE images from debian-installer-6.0-netboot-i386 version 20100912 Date: 2010-11-05 18:00 +0100 Machine: HP

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

Petter Reinholdtsen wrote: Dec 4 19:00:29 check-missing-firmware: missing firmware files (b43/ucode13.fw b43-open/ucode13.fw tigon/tg3_tso5.bin) for b43 b43 tg3 So there is missing firmware for your ethernet controller (tigon/tg3_tso5.bin), which is not really needed for it to basically work.

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

One way to fix this would be to make check-missing-firmware refuse to reload NIC modules whose interfaces have an address assigned. Problem: How to map from module to interface? Attached patch implements that. Please test. -- see shy jo Index: debian/changelog

Bug#605983: installation-report: PXE installation of HP Mini fails in partman step because network setup is lost

[Joey Hess] Attached patch implements that. Please test. I am unable to test. The Debian Edu developer gathering is over, and the test machines have been placed back into their storage boxes. :( Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to

Bug#572013: marked as done (udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail)

Your message dated Tue, 03 Aug 2010 08:48:08 + with message-id e1ogdao-0006rs...@franck.debian.org and subject line Bug#572008: fixed in busybox 1:1.17.1-1 has caused the Debian Bug report #572008, regarding udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail

Bug#572013: marked as done (udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail)

Your message dated Tue, 03 Aug 2010 08:48:08 + with message-id e1ogdao-0006rx...@franck.debian.org and subject line Bug#572013: fixed in busybox 1:1.17.1-1 has caused the Debian Bug report #572013, regarding udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail

Bug#572013: marked as done (udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail)

Your message dated Tue, 03 Aug 2010 08:48:08 + with message-id e1ogdao-0006s2...@franck.debian.org and subject line Bug#572622: fixed in busybox 1:1.17.1-1 has caused the Debian Bug report #572622, regarding udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail

Bug#572013: bashism in /usr/share/udhcpc/default.script causes network setup to fail

Package: udhcpc Version: 1:1.15.3-1 Severity: normal The proposed fix -- $((metric += 1)) -- doesn't have the same semantics. The routing table metric will start at 1 rather than 0. You need to increment $metric in a separate command, after using it in the route command: for i in $router;

Bug#572013: udhcpc: bashism in /usr/share/udhcpc/default.script causes network setup to fail

://bugs.debian.org/572006), but dash definitely can't parse it, since it's not necessary for POSIX conpliance. This causes causes network setup failures at least in some cases. (Worked fine for me + checkbashisms didn't find it, so I didn't notice this bashism when testing that code.) The easy solution

Bug#421805: installation-reports: Network setup incorrect after installation

Package: installation-reports Version: 2.29 Severity: normal Installation of the system was ok but I didn't have a network connection after the reboot. Saw the following on the console: ... SIOCSIFADDR: No such device eth0_rename: ERROR while getting interface flags: No such device

Bug#421805: installation-reports: Network setup incorrect after installation

reassign 421805 udev tags 421805 moreinfo d-i thanks Op 01-05-2007 om 13:05 schreef Frank Lenaerts: Checked /etc/network/interfaces and saw that it contained eth0_rename instead of e.g. eth0: ... # The primary network interface auto eth0_rename iface eth0_rename inet dhcp ...

Processed: Re: Bug#421805: installation-reports: Network setup incorrect after installation

Processing commands for [EMAIL PROTECTED]: reassign 421805 udev Bug#421805: installation-reports: Network setup incorrect after installation Bug reassigned from package `installation-reports' to `udev'. tags 421805 moreinfo d-i Bug#421805: installation-reports: Network setup incorrect after

Re: Bug#421805: installation-reports: Network setup incorrect after installation

On May 01, Frank Lenaerts [EMAIL PROTECTED] wrote: Searched for similar bugreports and found out that Debian bug #394047 seems to resemble it. My system has eth0 (on-board) and eth{1,2,3,4} (a qfe card). Which uses the same MAC address for all interfaces. Your system sucks, sorry. You can

Bug#274145: install freezes during network setup

Package: installation-reports Debian-installer-version: 20040927 http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/ uname -a: n/a install failed Date: 20040927 Method: netinst Machine: asus a7n8x Processor:ahtlon 1500 Memory:1 gig Root Device: ide 20gb drive Root Size/partition

No Network Setup

Just installed using todays build. Everything installed fine but there was not way to set up my network. The computer is on a LAN and the install options only setup a ISP connection. With Beta 1 I was able to enter all the information to connect to my LAN. I can enter the info from the command

Re: No Network Setup

Deron Wilkerson wrote: Just installed using todays build. Everything installed fine but there was not way to set up my network. The computer is on a LAN and the install options only setup a ISP connection. With Beta 1 I was able to enter all the information to connect to my LAN. I can enter

Bug#106875: base-config should provide network setup

Package: base-config Version: 1.74 Severity: important Followup-For: Bug #106875 base-config should provide network configuration similar to d-i's netcfg-dhcp and netcfg-static if the network has not been set up by d-i (eg. cdrom install). Otherwise base-config will fail like described above.

Re: Woody bf2.4 laptop network setup broken?

Hello, I've been attempting to do a static IP Woody install on a ThinkPad 600x with a Netgear FA511 cardbus interface. The official CDs never worked for a network install (the pcmcia-scheme error message), but I never really investigated very far (as I've have little experience with pcmcia or

Re: Re: Woody bf2.4 laptop network setup broken?

: David Kimdon [EMAIL PROTECTED] To: Eduardo Duenez [EMAIL PROTECTED] Sent: Fri, 11 Oct 2002 22:16:05 -0700 Subject: Re: Woody bf2.4 laptop network setup broken? Hi, Hi. I'm trying to install Woody from the network on my laptop using . . . /var/log/messages contains after attempting to bring

Woody bf2.4 laptop network setup broken?

Hi. I'm trying to install Woody from the network on my laptop using the bf2.4 floppies. I can configure PCMCIA support OK, and the kernel has pcnet_cs support so my D-Link DFE-670TXD card is recognized fine. I need to enter manually the network config (no DHCP) in case that makes a

Re: Woody bf2.4 laptop network setup broken?

Hi, Hi. I'm trying to install Woody from the network on my laptop using . . . /var/log/messages contains after attempting to bring up eth0 . . . I just built new images (untested) that I believe fix this problem and placed them on :

Re: patch to correct order of network setup items

* Tollef Fog Heen [EMAIL PROTECTED] [2002-09-13 10:02]: * Michael Cardenas | Great! Where should I look? Is it part of anna? No, there is something in the attic of tools/ddetect There are, at least, two methods for hard drive detection. * with parted * with discover For parted, you can

Re: patch to correct order of network setup items

* Thomas Poindessous | * Tollef Fog Heen [EMAIL PROTECTED] [2002-09-13 10:02]: | * Michael Cardenas | | | Great! Where should I look? Is it part of anna? | | No, there is something in the attic of tools/ddetect | | There are, at least, two methods for hard drive detection. | * with

patch to correct order of network setup items

Attached are patches to ddetect and netcfg so that configure network hardware will appear in the menu before setup dhcp networking or setup static networking, since the latter 2 can't be done until the former is complete. Also, is the retriever controller which will let you select your

Re: patch to correct order of network setup items

On Thu, Sep 12, 2002 at 08:45:23AM -0700, Michael Cardenas wrote: Attached are patches to ddetect and netcfg so that configure network hardware will appear in the menu before setup dhcp networking or setup static networking, since the latter 2 can't be done until the former is complete.

Re: patch to correct order of network setup items

* Michael Cardenas | Attached are patches to ddetect and netcfg so that configure network | hardware will appear in the menu before setup dhcp networking or | setup static networking, since the latter 2 can't be done until the | former is complete. thanks. | Also, is the retriever controller

Re: patch to correct order of network setup items

On Fri, Sep 13, 2002 at 02:54:50AM +0200, Tollef Fog Heen wrote: | Also, do we have a cd retriever yet? If not, I plan to work on | these two things. yes, both are working (and anna is being worked on by Martin Sj?gren). You might want to look into hard drive autodetection, that is Not

Re: patch to correct order of network setup items

* Michael Cardenas | Great! Where should I look? Is it part of anna? No, there is something in the attic of tools/ddetect -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' :

Bug#66284: PCMCIA Network setup not working

Package: boot-floppies Version: 2.2.15 Severity: important Installing on a HP omnibook 900 with 3com 556B modem/ethernet, resulted in weird interactions between the PCMCIA setup, which seemed to work fine, and the network config. Telling the network setup that we wanted PCMCIA ethernet (which