|
|

08-20-2008, 09:59 PM
|
|
|
no network connection
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 Ethernet. My typical usage of
> this system is to ssh into it from another machine, that won't
> necessarily be local to my debian machine's console. This all works
> fine, except that I have to log into the console the first time after
> bootup to enable ethernet through that icon I mentioned earlier.
>
> I assumed that the ifup/ifdown stuff discussed in the "man interfaces"
> was referring to some call to ifup that was being done during
> system startup somewhere; hence, the reason for my reboot.
>
> See what I mean?
So, as I said, you'd want networking configured with ifupdown. The
documentation is good for that, so you should not have a problem if you know
a little how networking works. If you know less than little, you might have
to do some reading. Perhaps TLDP will have some reading material.
>
> Shachar Or wrote:
> > 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 eth0 inet dhcp
> >> >
> >> > auto eth0
> >>
> >> I commented out the "auto eth0" line and rebooted.
> >
> > Don't reboot for network configuration...
> >
> >> No change.
> >
> > What is the change you're looking for?
> >
> >> Then I put "auto eth0" back in and commented out "allow-hotplug eth0".
> >> Same thing.
> >>
> >> Any other thoughts?
> >
> > Did you read the whole documentation and understand how the ifupdown
> > thing works?
> >
> > Also, 'man ifconfig' to see how to check the status of your interfaces.
> >
> >> Ed
> >>
> >> Shachar Or 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. 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 ethernet cable icon with
> >>>>> a big NOT sign (red circle with a slash
> >>>>> through it) over top of it. I right-click on that and
> >>>>> a pull-down menu allows me to enable my wired network.
> >>>>> Then everything is fine.
> >>>>>
> >>>>> How can I fix this so that the network just comes up automatically?
> >>>>> Couldn't find anything on this in the archives or in the GUI.
> >>>>>
> >>>>> Thanks
> >>>>> Ed
> >>>>
> >>>> Hi:
> >>>> You should have a files /etc/network/interfaces
> >>>>
> >>>> which should have something like:
> >>>>
> >>>> auto lo
> >>>> iface lo inet loopback
> >>>>
> >>>>
> >>>> allow-hotplug eth0
> >>>>
> >>>> iface eth0 inet dhcp
> >>>>
> >>>> auto eth0
> >>>
> >>> There's no point in having both allow-hotplug and auto.
> >>>
> >>>> *****
> >>>>
> >>>> try it with and without the auto eth0. I am assuming the eth0 is your
> >>>> wired network: it may be eth1, or eth3 for you. I am also assuming you
> >>>> are using dhcp.
> >>>>
> >>>>
> >>>> man interfaces will give you more information.
> >>>>
> >>>> Sebastian Canagaratna
--
Shachar Or | שחר אור
http://ox.freeallweb.org/
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|

08-21-2008, 01:17 AM
|
|
|
no network connection
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 just a matter of getting the contents of
/etc/network/interfaces correct. I'm not familiar with Gnome's network-manager,
but if you post the contents of your /etc/network/interfaces I bet somebody
could help you.
[...]
> I assumed that the ifup/ifdown stuff discussed in the "man interfaces"
> was referring to some call to ifup that was being done during
> system startup somewhere; hence, the reason for my reboot.
You're correct. If you want to restart ifupdown without rebooting, you can issue
'/etc/init.d/networking restart' (without quotes and as root -- use sudo if
you've got it). That'll save time, especially while you're debugging.
Good luck,
- Chris
>
> See what I mean?
>
>
> Shachar Or wrote:
>> 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 eth0 inet dhcp
>>> >
>>> > auto eth0
>>>
>>> I commented out the "auto eth0" line and rebooted.
>>
>> Don't reboot for network configuration...
>>> No change.
>>
>> What is the change you're looking for?
>>
>>> Then I put "auto eth0" back in and commented out "allow-hotplug eth0".
>>> Same thing.
>>>
>>> Any other thoughts?
>>
>> Did you read the whole documentation and understand how the ifupdown
>> thing works?
>>
>> Also, 'man ifconfig' to see how to check the status of your interfaces.
>>> Ed
>>>
>>> Shachar Or 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. 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 ethernet cable icon with
>>>>>> a big NOT sign (red circle with a slash
>>>>>> through it) over top of it. I right-click on that and
>>>>>> a pull-down menu allows me to enable my wired network.
>>>>>> Then everything is fine.
>>>>>>
>>>>>> How can I fix this so that the network just comes up automatically?
>>>>>> Couldn't find anything on this in the archives or in the GUI.
>>>>>>
>>>>>> Thanks
>>>>>> Ed
>>>>> Hi:
>>>>> You should have a files /etc/network/interfaces
>>>>>
>>>>> which should have something like:
>>>>>
>>>>> auto lo
>>>>> iface lo inet loopback
>>>>>
>>>>>
>>>>> allow-hotplug eth0
>>>>>
>>>>> iface eth0 inet dhcp
>>>>>
>>>>> auto eth0
>>>> There's no point in having both allow-hotplug and auto.
>>>>
>>>>> *****
>>>>>
>>>>> try it with and without the auto eth0. I am assuming the eth0 is your
>>>>> wired network: it may be eth1, or eth3 for you. I am also assuming you
>>>>> are using dhcp.
>>>>>
>>>>>
>>>>> man interfaces will give you more information.
>>>>>
>>>>> Sebastian Canagaratna
>>
>
>
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|

08-21-2008, 03:01 PM
|
|
|
no network connection
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...
I might be assuming wrong things here. Do you have network-manager-gnome
installed? Are you even logging into GNOME?
If you are logging into GNOME and do not have network-manager-gnome, try
installing it and then check gconf-editor again. If you already had
network-manager-gnome, try reconfiguring it ($ sudo dpkg-reconfigure
network-manager-gnome).
If you have no need for Network Manager at all (or if the above does not
solve your problem), which actually seems to be your case, you could
also try this:
Uninstall any network-manager packages ($ sudo aptitude remove
network-manager network-manager-gnome network-manager-kde) and setting
your interface to auto (in /etc/network/interfaces):
auto eth0
iface eth0 inet dhcp
Either approach should work in theory. Please post any further doubts.
Ok, my problem appears to be resolved. Just to recap...
I am running GNOME, and according to dpkg -l network-manager was installed.
I was unable to find network-manager-applet in gconf-editor->apps.
So, I uninstalled network-manager and network-manager-gnome, and at the
moment that appears to have resolved the problem. My system now comes
up with the network enabled.
Note that I made no changes to /etc/network/interfaces to resolve this.
Thanks for the help.
Ed
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
All times are GMT. The time now is 09:08 PM.
VBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org
|