Thank you for your suggestions.

I'm afraid I may need a little hand-holding on this. I had already
purged ifupdown via "aptitude purge ifupdown" right after ifupdown was
removed automatically.

I will hope to find time this weekend to compare the contents of
/etc/netscript/network.conf with those of systems that are behaving
normally.

With respect to the suggestion to "configure eth0_IPADDR", I'm afraid
I'm clueless as to what that means.

Sorry for being a tyro at this.

I'm a happy user of 5 Debian testing systems for a couple of years
(using "testing" instead of "squeeze" or "wheezy" in
/etc/apt/sources.list), and I have the occasional "adventure". But I
have to say that I've never had to go spelunking into the netscript
package locations.

Many thanks for your help.

On 06/15/2012 04:23 PM, Matthew Grant wrote:
> Have a look at /etc/net script/network.conf. further down this file you
> will find eth_start/eth_stop functions. They hook functions to hook dhcp in
> for initial configuration (and where you can hook tunnel daemons etc). Also
> configure eth0_IPADDR. Dpkg --purge ifupdown as it can cause some issues
> with unit script circular dependencies at times. Please let me know how you
> go.
> 
> Matthew Grant
> On Jun 16, 2012 4:39 AM, "Gilbert Sullivan" <whirly...@comcast.net> wrote:
> 
>> Package: netscript-2.4
>> Version: 5.2.11
>> Severity: normal
>>
>> Dear Maintainer,
>> *** Please consider answering these questions, where appropriate ***
>>
>>   * What led up to the situation?
>>
>>        On 05/18/2012 upgrade in netbase:amd64 (4.47, 5.0) resulted in
>> automatic removal of ifupdown and automatic
>>        installation of netscript 2.4. Problem appeared first reboot
>> following these changes to the system.
>>
>>   * What exactly did you do (or not do) that was effective (or
>>     ineffective)?
>>
>>        Setting system to connect using any fixed IP address results in a
>> 60 second timeout at the configuring
>>        interface step of the boot process. Then the system goes on to a
>> second 60 second timeout at the starting
>>        MTA step of the boot process.
>>
>>        Setting system to connect via DHCP results in a normal boot process
>> with no timeouts.
>>
>>        I can turn off Wicd and prevent it from starting. Again,
>> configuring /etc/network/interfaces for fixed IP
>>        address results in two 60 second timeouts, and configuring
>> interfaces for DHCP results in a normal boot
>>        process with no timeouts.
>>
>>        Hitting <Ctrl>+<C> key combination at the configuring interface
>> prompt during the boot process causes the
>>        boot process to continue at a normal pace with no timeout at
>> starting MTA step.
>>
>>   * What was the outcome of this action?
>>
>>        I believe I have eliminated Wicd as a suspect. I have also
>> confirmed that the system does actually have
>>        the correct fixed IP address when these timeouts occur. But it
>> LOOKS as though the system were waiting
>>        the timeout period to receive a DHCP lease.
>>
>> -- System Information:
>> Debian Release: wheezy/sid
>>  APT prefers testing
>>  APT policy: (500, 'testing')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>>
>> Versions of packages netscript-2.4 depends on:
>> ii  bash                            4.2-2
>> ii  bridge-utils                    1.5-3
>> ii  iproute                         20120521-2
>> ii  iptables                        1.4.13-1.1
>> ii  isc-dhcp-client [dhcp3-client]  4.2.2.dfsg.1-5
>> ii  netbase                         5.0
>>
>> Versions of packages netscript-2.4 recommends:
>> ii  quagga  0.99.21-3
>>
>> Versions of packages netscript-2.4 suggests:
>> ii  dnsmasq        2.61-1
>> ii  quagga         0.99.21-3
>> ii  resolvconf     1.65
>> ii  whereami       0.3.34-0.3
>> ii  wicd           1.7.2.4-2
>> ii  wpasupplicant  1.0-2
>>
>> -- Configuration Files:
>> /etc/netscript/ipfilter-defs/README [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/README'
>> /etc/netscript/ipfilter-defs/dnat-defs [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/dnat-defs'
>> /etc/netscript/ipfilter-defs/example.def [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/example.def'
>> /etc/netscript/ipfilter-defs/example2.def [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/example2.def'
>> /etc/netscript/ipfilter-defs/local.def [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/local.def'
>> /etc/netscript/ipfilter-defs/masq-defs [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/masq-defs'
>> /etc/netscript/ipfilter-defs/network-defs [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/network-defs'
>> /etc/netscript/ipfilter-defs/prototypes-defs [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/prototypes-defs'
>> /etc/netscript/ipfilter-defs/prototypes.sh [Errno 13] Permission denied:
>> u'/etc/netscript/ipfilter-defs/prototypes.sh'
>>
>> -- no debconf information
>>
>>
>>
> 




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to