network not starting at boot
 

I've had a quick look around but can't see why my network's not starting
at boot, but works okay if I run 'sudo dhclient'... this is with
2.6.25-2-amd64 kernel from backports (build by debootstrap and then
apt-get from backports)... I've copied over various /etc files such that
I have a /etc/hosts and /etc/network/interfaces

Pointers to what I've overlooked most welcome, thanks!

Michael


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

network not starting at boot
 

michael:
>
> I've had a quick look around but can't see why my network's not starting
> at boot, but works okay if I run 'sudo dhclient'... this is with
> 2.6.25-2-amd64 kernel from backports (build by debootstrap and then
> apt-get from backports)... I've copied over various /etc files such that
> I have a /etc/hosts and /etc/network/interfaces

Plaese post the contents of the interfaces file.

J.
--
I start many things but I have yet to finish a single one.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>

network not starting at boot
 

On Thu, 2008-07-17 at 17:37 +0200, Jochen Schulz wrote:
> michael:
> >
> > I've had a quick look around but can't see why my network's not starting
> > at boot, but works okay if I run 'sudo dhclient'... this is with
> > 2.6.25-2-amd64 kernel from backports (build by debootstrap and then
> > apt-get from backports)... I've copied over various /etc files such that
> > I have a /etc/hosts and /etc/network/interfaces
>
> Plaese post the contents of the interfaces file.
>
> J.

mkb2@veri:/etc/network$ cat interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp
pre-up /etc/network/if-pre-up.d/iptables-firewall.sh




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

network not starting at boot
 

michael:
> On Thu, 2008-07-17 at 17:37 +0200, Jochen Schulz wrote:
>>
>> Plaese post the contents of the interfaces file.
>
> mkb2@veri:/etc/network$ cat interfaces
> # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> # /usr/share/doc/ifupdown/examples for more information.
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet dhcp
> pre-up /etc/network/if-pre-up.d/iptables-firewall.sh

If eth0 is the interface you want to use and which you give as an
argument to dhclient when manually running it, this should be fine.

Are you using Gnome? If yes, do you have Network Manager installed
(package network-manager). This has messed up a lot of users' networking
setups.

J.
--
My drug of choice is self-pity.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>

network not starting at boot
 

On Thu, 2008-07-17 at 18:32 +0200, Jochen Schulz wrote:
> michael:
> > On Thu, 2008-07-17 at 17:37 +0200, Jochen Schulz wrote:
> >>
> >> Plaese post the contents of the interfaces file.
> >
> > mkb2@veri:/etc/network$ cat interfaces
> > # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
> > # /usr/share/doc/ifupdown/examples for more information.
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > auto eth0
> > iface eth0 inet dhcp
> > pre-up /etc/network/if-pre-up.d/iptables-firewall.sh
>
> If eth0 is the interface you want to use and which you give as an
> argument to dhclient when manually running it, this should be fine.

yes (although I just run 'dhclient' without an argument):

mkb2@veri:~$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:D1:E5:06:2F
inet addr:130.88.15.180 Bcast:130.88.255.255
Mask:255.255.0.0
inet6 addr: fe80::219:d1ff:fee5:62f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:190862 errors:0 dropped:0 overruns:0 frame:0
TX packets:5961 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:28320647 (27.0 MiB) TX bytes:470522 (459.4 KiB)
Memory:e1300000-e1320000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)




> Are you using Gnome? If yes, do you have Network Manager installed
> (package network-manager). This has messed up a lot of users' networking
> setups.

I'm trying xcfe

By comparing with another box I see that the working version has
(/var/log/messages)

Jul 17 19:49:25 amd64 kernel: NET: Registered protocol family 10
Jul 17 19:49:25 amd64 kernel: lo: Disabled Privacy Extensions
Jul 17 19:49:25 amd64 kernel: IPv6 over IPv4 tunneling driver
Jul 17 19:49:28 amd64 dhcdbd: Started up.


whereas non-working has only

Jul 17 14:49:27 (none) kernel: [ 8.120950] NET: Registered protocol
family 10
Jul 17 14:49:27 (none) kernel: [ 8.121367] lo: Disabled Privacy
Extensions

Does that mean anything?

thanks again, michael


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

network not starting at boot
 

michael:
> On Thu, 2008-07-17 at 18:32 +0200, Jochen Schulz wrote:
>
>> Are you using Gnome? If yes, do you have Network Manager installed
>> (package network-manager). This has messed up a lot of users' networking
>> setups.
>
> I'm trying xcfe

Network Manager may be running anyway because IIRC it is run as a
daemon at boot time.

> By comparing with another box I see that the working version has
> (/var/log/messages)
>
> Jul 17 19:49:25 amd64 kernel: NET: Registered protocol family 10
> Jul 17 19:49:25 amd64 kernel: lo: Disabled Privacy Extensions
> Jul 17 19:49:25 amd64 kernel: IPv6 over IPv4 tunneling driver
> Jul 17 19:49:28 amd64 dhcdbd: Started up.
>
> whereas non-working has only
>
> Jul 17 14:49:27 (none) kernel: [ 8.120950] NET: Registered protocol family 10
> Jul 17 14:49:27 (none) kernel: [ 8.121367] lo: Disabled Privacy Extensions
>
> Does that mean anything?

I don't think so. The first machine just appears to have IPv6 support
whereas the other one doesn't. Since I strongly suspect you only want to
use IPv4 (if it was different, you would know) this difference shouldn't
matter.

J.
--
All participation is a myth.
[Agree] [Disagree]
<http://www.slowlydownward.com/NODATA/data_enter2.html>

network not starting at boot
 

On 18 Jul 2008, at 08:40, Jochen Schulz wrote:


michael:

On Thu, 2008-07-17 at 18:32 +0200, Jochen Schulz wrote:


Are you using Gnome? If yes, do you have Network Manager installed
(package network-manager). This has messed up a lot of users'
networking

setups.


I'm trying xcfe


Network Manager may be running anyway because IIRC it is run as a
daemon at boot time.


By comparing with another box I see that the working version has
(/var/log/messages)

Jul 17 19:49:25 amd64 kernel: NET: Registered protocol family 10
Jul 17 19:49:25 amd64 kernel: lo: Disabled Privacy Extensions
Jul 17 19:49:25 amd64 kernel: IPv6 over IPv4 tunneling driver
Jul 17 19:49:28 amd64 dhcdbd: Started up.

whereas non-working has only

Jul 17 14:49:27 (none) kernel: [ 8.120950] NET: Registered
protocol family 10
Jul 17 14:49:27 (none) kernel: [ 8.121367] lo: Disabled Privacy
Extensions


Does that mean anything?


I don't think so. The first machine just appears to have IPv6 support
whereas the other one doesn't. Since I strongly suspect you only
want to
use IPv4 (if it was different, you would know) this difference
shouldn't

matter.


I've just realised that I hadn't the iptables firewall script in the
correct place so



# The primary network interface
auto eth0
iface eth0 inet dhcp
pre-up /etc/network/if-pre-up.d/iptables-firewall.sh


was probably falling over because of that.

M


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org