On Wed, 16 Feb 2011 21:55:19 +, I wrote:
> I installed Wheezy (testing) with a netinst CD, at which point it obviously
> had a network connection. On booting, though, it does not.
On Mon, 21 Feb 2011 03:45:39 +0200, Andrei Popescu replied:
> Ok, nothing obviously wrong that I can spot. One
On Jo, 17 feb 11, 16:04:19, Steve Kleene wrote:
[snip configs]
Ok, nothing obviously wrong that I can spot. One more thing to consider:
make sure eth0 and eth1 are not reversed (the names, not the physical
cards). You can compare MACs from ifconfig or just watch syslog while
pluging/unpluging
On Wed, 16 Feb 2011 21:55:19 +, I wrote:
> I installed Wheezy (testing) with a netinst CD, at which point it obviously
> had a network connection. On booting, though, it does not. If I transfer
> the Ethernet cable to the adjacent Lenny machine, the connection is fine.
>
> /etc/network/in
On Mi, 16 feb 11, 21:55:19, Steve Kleene wrote:
>
> /etc/network/interfaces, /etc/inetd.conf, and /etc/resolv.conf are the same
> on the two machines.
Still, please post them here (not inetd.conf).
> On Wheezy, ifconfig -a (see below) shows no addresses for IP, broadcast, or
> mask. I chose et
From: Steve Kleene
To: debian-user@lists.debian.org
Subject: no network connection with Wheezy
I installed Wheezy (testing) with a netinst CD, at which point it obviously
had a network connection. On booting, though, it does not. If I transfer
the Ethernet cable to the adjacent Lenny machine
I can run gconf-editor, but there is no NetworkManagerApplet
under apps.
I see that there is something called NetworkManager and
NetworkManagerDispatcher
under /usr/sbin; but when I run gconf-editor, there's no
apps->NetworkManagerApplet
entry.
continued thanks...
Ed Sutter wrote:
> My goal is to have the debian-based system start up with Ethernet
> enabled immediately (I would have thought that would be the standard
> way it would boot up). I don't want to have to log into my console
> and click something to start up Ethernet.
You shouldn't have to. It's
On Wed, Aug 20, 2008 at 5:29 PM, Ed Sutter <[EMAIL PROTECTED]>wrote:
> Thanks for the responses!
> My /etc/network/interfaces file already has the following:
>
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > allow-hotplug eth0
On Wednesday 20 August 2008 23:53, Ed Sutter wrote:
> My goal is to have the debian-based system start up with Ethernet
> enabled immediately (I would have thought that would be the standard
> way it would boot up). I don't want to have to log into my console
> and click something to start up Ethe
My goal is to have the debian-based system start up with Ethernet
enabled immediately (I would have thought that would be the standard
way it would boot up). I don't want to have to log into my console
and click something to start up Ethernet. My typical usage of
this system is to ssh into it fr
On Wednesday 20 August 2008 23:29, Ed Sutter wrote:
> Thanks for the responses!
>
> My /etc/network/interfaces file already has the following:
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > allow-hotplug eth0
> > iface
Thanks for the responses!
My /etc/network/interfaces file already has the following:
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet dhcp
> auto eth0
I commented out the "auto eth0" line and reboote
On Wed, Aug 20, 2008 at 4:52 PM, Shachar Or <[EMAIL PROTECTED]> wrote:
> On Wednesday 20 August 2008 22:46, Sebastian Canagaratna wrote:
> > Ed Sutter wrote:
> > > Hi,
> > > I have Debian 4.0 on a machine now for 2 days.
> > > Thanks to this list, my screen resolution problem is
> > > resolved. N
Hi
On Wed, Aug 20, 2008 at 4:39 PM, Shachar Or <[EMAIL PROTECTED]> wrote:
> On Wednesday 20 August 2008 22:33, Ed Sutter wrote:
> > Hi,
> > I have Debian 4.0 on a machine now for 2 days.
> > Thanks to this list, my screen resolution problem is
> > resolved. Next (and hopefully last) problem is t
On Wednesday 20 August 2008 22:46, Sebastian Canagaratna wrote:
> Ed Sutter wrote:
> > Hi,
> > I have Debian 4.0 on a machine now for 2 days.
> > Thanks to this list, my screen resolution problem is
> > resolved. Next (and hopefully last) problem is that
> > each time I boot the system I have to m
Ed Sutter wrote:
Hi,
I have Debian 4.0 on a machine now for 2 days.
Thanks to this list, my screen resolution problem is
resolved. Next (and hopefully last) problem is that
each time I boot the system I have to manually enable
my network connection. When Gnome starts up, I see in
the top of the
On Wednesday 20 August 2008 22:33, Ed Sutter wrote:
> Hi,
> I have Debian 4.0 on a machine now for 2 days.
> Thanks to this list, my screen resolution problem is
> resolved. Next (and hopefully last) problem is that
> each time I boot the system I have to manually enable
> my network connection.
Hi,
I have Debian 4.0 on a machine now for 2 days.
Thanks to this list, my screen resolution problem is
resolved. Next (and hopefully last) problem is that
each time I boot the system I have to manually enable
my network connection. When Gnome starts up, I see in
the top of the screen a small et
wrote:
Hello,
Im using exim just to send system emails.
When the system has no network connection, exim takes too long to start.
Is there any way to reduce this time?
Thanks
This was just on the list; search the archives. Hint: minimal-dns,
dial-on-demand.
Celejar
--
mailmin.sourcefor
On Tue, 18 Sep 2007 15:36:26 +0100
Jaime Ventura <[EMAIL PROTECTED]> wrote:
> Hello,
> Im using exim just to send system emails.
> When the system has no network connection, exim takes too long to start.
> Is there any way to reduce this time?
> Thanks
This was just on
Hello,
Im using exim just to send system emails.
When the system has no network connection, exim takes too long to start.
Is there any way to reduce this time?
Thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
network connection.
I suppose it is erroneous behaviour on NM's part but if you only have
statically configured interfaces, why do you need NM?
Vibhav
Regarding your description of its purpose, I probably don' t need it.
Having used (and still using) other distro'
Huub van Niekerk wrote:
Hi,
I recently installed Debian Etch and it works fine...including the
network connection. But in the top-bar, on the right I have 4 icons,
from right to left: Window Selector, speaker, time and NetworkManager
that says No network connection. When I right click on it
Hi,
I recently installed Debian Etch and it works fine...including the network
connection. But in the top-bar, on the right I have 4 icons, from right to
left: Window Selector, speaker, time and NetworkManager that says No network
connection. When I right click on it, I get a drop-down menu with
24 matches
Mail list logo