/etc/init.d/network vs /etc/init.d/networking (Debian Guide?)
Long story short, as I've told it before, a friend began the setup of a debian box for me (i'm a little overbusy with work and a very long commute), wasn't familiar with debian, never seemed to get it, eventually gave up in frustration. So, i'm now trying to decipher the setup of a box with stable r 6 installed. I need to add a correct route command. I assume I'd add it to an init.d script. grep route /etc/init.d/* turns up nothing. I have a /etc/init.d/networking file (se list of all init.d files below) but no /etc/init.d/network. The debian-guide certainly makes it sound as if i should have a /etc/init.d/network file. I've discovered the /etc/network/interfaces file -- I think I should fix things there. Side Note: If /etc/init.d/network has been discontinued and the functionality moved to /etc/network/interfaces, perhaps someone should update Debian Guide. The Debian Guide I'm referring to is Debian GNU/Linux: Guide to Installation and Usage, John Goerzen and Ossama Othman, (c) 1998, 1999 Software in the Public Interest, Inc. which my friend installed with stable r 6 -- I've no idea which package or where it came from. It doesn't seem mentioned on http://www.debian.org/doc/user-manuals. Cheers, judith For my reference: http://lists.debian.org/debian-user/2002/debian-user-200203/msg04568.html has a /etc/init.d/network script from 2.2 r5 file://localhost/usr/doc/debian-guide/html/noframes/node83.html points to /etc/init.d/network http://lists.debian.org/debian-user/2002/debian-user-200201/msg04032.html points to /etc/network/interfaces -rwxr-xr-x1 root root 375 May 5 19:38 anacron* -rwxr-xr-x1 root root 1074 May 5 19:38 atd* -rwxr-xr-x1 root root 648 May 5 19:38 bind* -rwxr-xr-x1 root root 1909 Dec 4 2002 bootmisc.sh* -rwxr-xr-x1 root root 731 Dec 4 2002 checkfs.sh* -rwxr-xr-x1 root root 3165 May 5 19:38 checkroot.sh* -rwxr-xr-x1 root root 2757 Dec 4 2002 console-screen.sh* -rwxr-xr-x1 root root 835 May 5 19:38 cron* -rwxr-xr-x1 root root 756 Jan 9 06:50 devpts.sh* -rwxr-xr-x1 root root 2966 May 5 19:38 diald* -rwxr-xr-x1 root root 511 Dec 4 2002 dns-clean* -rwxr-xr-x1 root root 1078 May 5 19:38 exim* -rwxr-xr-x1 root root 1205 May 5 19:38 gpm* -rwxr-xr-x1 root root 281 May 5 19:38 halt* -rwxr-xr-x1 root root 132 Dec 4 2002 hostname.sh* -rwxr-xr-x1 root root 3019 May 5 19:38 hwclock.sh* -rwxr-xr-x1 root root 1516 May 5 19:38 inetd* -rwxr-xr-x1 root root 731 May 5 19:38 inn2* -rwxr-xr-x1 root root 395 Dec 4 2002 isapnp* -rwxr-xr-x1 root root 646 May 5 19:38 junkbuster* -rwxr-xr-x1 root root 1007 May 5 19:38 kerneld* -rwxr-xr-x1 root root 794 May 5 19:38 keymaps-lct.sh* -rwxr-xr-x1 root root 1056 May 5 19:38 logoutd* -rwxr-xr-x1 root root 911 May 5 19:38 lpd* -rwxr-xr-x1 root root 362 May 5 19:38 makedev* -rwxr-xr-x1 root root 1048 Dec 4 2002 modutils* -rwxr-xr-x1 root root 601 Dec 4 2002 mountall.sh* -rwxr-xr-x1 root root 1478 Dec 4 2002 mountnfs.sh* -rwxr-xr-x1 root root 826 Jan 12 2000 nethack* -rwxr-xr-x1 root root 4045 May 5 19:38 networking* -rwxr-xr-x1 root root 1482 May 5 19:38 nfs-common* -rwxr-xr-x1 root root 1278 May 5 19:38 nfs-server* -rwxr-xr-x1 root root 1882 Oct 20 2001 nviboot* -rwxr-xr-x1 root root 1070 May 5 19:38 portmap* -rwxr-xr-x1 root root 929 May 5 19:38 postgresql* -rwxr-xr-x1 root root 927 May 5 19:38 ppp* -rwxr-xr-x1 root root 1013 Dec 4 2002 procps.sh* -rwxr-xr-x1 root root 1987 May 5 19:38 proftpd* -rwxr-xr-x1 root root 1811 Dec 4 2002 pump* -rwxr-xr-x1 root root 2213 Dec 4 2002 rc* -rwxr-xr-x1 root root 1190 Dec 4 2002 rcS* -rwxr-xr-x1 root root 197 May 5 19:38 reboot* -rwxr-xr-x1 root root 252 May 5 19:38 rmnologin* -rwxr-xr-x1 root root 2626 May 5 19:38 samba* -rwxr-xr-x1 root root 349 May 5 19:38 sendsigs* -rwxr-xr-x1 root root 3649 May 5 19:38 setserial* -rwxr-xr-x1 root root 476 May 5 19:38 single* -rwxr-xr-x1 root root 1753 May 5 19:38 skeleton* -rwxr-xr-x1 root root 1448 Dec 4 11:41 ssh* -rwxr-xr-x1 root root 1471 May 5 19:38 sysklogd* -rwxr-xr-x1 root root 430 May 5 19:38 umountfs* -rwxr-xr-x1 root root 420 May 5 19
Re: /etc/init.d/network vs /etc/init.d/networking (Debian Guide?
I've discovered the /etc/network/interfaces file -- I think I should fix things there. yes, that is the correct location now Side Note: If /etc/init.d/network has been discontinued and the functionality moved to /etc/network/interfaces, perhaps someone should update Debian Guide. The Debian Guide I'm referring to is Debian GNU/Linux: Guide to Installation and Usage, John Goerzen and Ossama Othman, (c) 1998, 1999 Software in the Public Interest, Inc. which my friend installed with stable r 6 -- I've no idea which package or where it came from. It doesn't seem mentioned on http://www.debian.org/doc/user-manuals. their addresses are: John Goerzen [EMAIL PROTECTED] and Ossama Othman [EMAIL PROTECTED] the book is maintained in the Debian package 'debian-guide' which is maintained by John. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: /etc/route.conf oder /etc/init.d/network ?
Hallo Johannes, Hallo Listies ... Ich möchte meinen Woody jetzt auch als DHCP-Server einsetzen. ... Um sich händische Aufrufen zu ersparen, könne man auch in die /etc/route.conf folgendes dazuschreiben: 255.255.255.255 0.0.0.0 255.255.255.255 eth0 Uuups, die /etc/route.conf gibts bei mir nicht, auch keine /etc/init.d/network die IMHO bei Debian doch die /etc/route.conf ersetzen sollte! Oder hab ich da etwa was falsch verstanden? hmm - es gibt /etc/networks (Datei: Inhalt bei mir localnet 192.168.0.0) und auch /etc/network (Ordner) und in /etc/init.d habe ich mit network /etc/init.d/networking (Woody) vielleicht hilft dir das ja weiter ;) Zuerst mal, Danke aber ... ... hat mir leider auch nicht weitergeholfen! Diese Dateien und Ordner kannte ich, hab Da aber nix gfunden, was so ausgschaut hätt, als wärs das Richtige ... dhcp an sich funktioniert ja auch ohne diesen Eintrag, aber nicht im Zusammenhang mit WinDoof-Clients, die lauschen einfach nur auf 255.255.255.255 welche IP-Adresse usw sie selber annehmen sollen, und ohne diesen Eintrag kommts eben auf 192.168.0.255 daher (oder?)... Hat irgendwer noch einen Tip? -- Liebe Grüße aus Wien Karin http://gerbrich.at/ http://blue-danube-cup.org/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP: /etc/route.conf oder /etc/init.d/network ?
Hi, -Ursprüngliche Nachricht- Von: Karin Gerbrich [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. Februar 2002 20:55 An: Debian-User-De Betreff: DHCP: /etc/route.conf oder /etc/init.d/network ? Hallo Liste! Ich möchte meinen Woody jetzt auch als DHCP-Server einsetzen. In verschiedenen HowTo's lese ich, dass vor Start von dhcp unbedingt die Route gesetzt werden muss: route add -host 255.255.255.255 dev eth0 Stand da auch, wofür das gut sein soll ? Bei mir läuft ein DHCP-Server mit Windows 2000 Clients prima zusammen (ohne zusätzlicher route). Gruß Micha -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP: /etc/route.conf oder /etc/init.d/network ?
Michael Tuschik schrieb: -Ursprüngliche Nachricht- Von: Karin Gerbrich [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 21. Februar 2002 20:55 An: Debian-User-De Betreff: DHCP: /etc/route.conf oder /etc/init.d/network ? Kann deine komische Software keine Einleitungszeile erzeugen? Vielleicht hilft ja ein Update. :-/ route add -host 255.255.255.255 dev eth0 Stand da auch, wofür das gut sein soll ? Bei mir läuft ein DHCP-Server mit Windows 2000 Clients prima zusammen (ohne zusätzlicher route). Hmm, kann eigentlich nur sein, wenn die dhcp-clients von Windoze die Broadcast-Adresse ignorieren. Also wenn's denn unbedingt sein muss, kann ein zusätzliche Route in /etc/network/interfaces eingebaut werden. | iface eth0 inet static | address 10.20.0.3 | netmask 255.255.0.0 | up route add -host 255.255.255.255 eth0 RTFM interfaces Ciao Walter -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: DHCP: /etc/route.conf oder /etc/init.d/network ?
Kann deine komische Software keine Einleitungszeile erzeugen? Vielleicht hilft ja ein Update. :-/ Wenn Du mit komischer Software mein Outlook meinst, da hilft nix, nur deinstallieren ... ... und genau das hab ich vor ;o) Stand da auch, wofür das gut sein soll ? Bei mir läuft ein DHCP-Server mit Windows 2000 Clients prima zusammen (ohne zusätzlicher route). Bei mir nicht ... ... habs ausprobiert! Hmm, kann eigentlich nur sein, wenn die dhcp-clients von Windoze die Broadcast-Adresse ignorieren. genau das tun sie, sie ignorieren vorerst alles bis auf 255.255.255.255, erst wenn sie mit dhcp konfiguriert sind akzeptieren sie die normale Broadcast-Adresse! Also wenn's denn unbedingt sein muss, kann ein zusätzliche Route in /etc/network/interfaces eingebaut werden. | iface eth0 inet static | address 10.20.0.3 | netmask 255.255.0.0 | up route add -host 255.255.255.255 eth0 DANKE! -- Liebe Grüße aus Wien Karin http://gerbrich.at/ http://blue-danube-cup.org/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
AW: DHCP: /etc/route.conf oder /etc/init.d/network ?
Kann deine komische Software keine Einleitungszeile
erzeugen? Vielleicht
hilft ja ein Update. :-/
Wenn Du mit komischer Software mein Outlook meinst, da hilft nix, nur
deinstallieren ...
Damit war ich wohl gemeint. 8|
Stand da auch, wofür das gut sein soll ? Bei mir läuft ein
DHCP-Server
mit Windows 2000 Clients prima zusammen (ohne zusätzlicher route).
Bei mir nicht ...
... habs ausprobiert!
Hier ein Auszug aus meiner dhcpd.conf:
shared-network XXX-XXX {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.2.255;
option routers .xxx-xxx.xx;
option domain-name xxx-xxx.xx;
option domain-name-servers xx.xxx-xxx.xx;
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.200 192.168.2.250;
}
}
Und auf dem Client sieht das dann so aus:
Windows 2000-IP-Konfiguration
Ethernetadapter LAN-Verbindung 2:
Verbindungsspezifisches DNS-Suffix: xxx-xxx.xx
IP-Adresse. . . . . . . . . . . . : 192.168.2.203
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.2.1
Viele Grüße,
Micha
--
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: DHCP: /etc/route.conf oder /etc/init.d/network ?
- Original Message - From: Karin Gerbrich [EMAIL PROTECTED] To: Walter Saner [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, February 22, 2002 5:08 PM Subject: RE: DHCP: /etc/route.conf oder /etc/init.d/network ? Stand da auch, wofür das gut sein soll ? Bei mir läuft ein DHCP-Server mit Windows 2000 Clients prima zusammen (ohne zusätzlicher route). Bei mir nicht ... ... habs ausprobiert! Hmm, kann eigentlich nur sein, wenn die dhcp-clients von Windoze die Broadcast-Adresse ignorieren. genau das tun sie, sie ignorieren vorerst alles bis auf 255.255.255.255, erst wenn sie mit dhcp konfiguriert sind akzeptieren sie die normale Broadcast-Adresse! Das ist auch richtig so. Woher sollen die WindowsClients auch wissen, welche Broadcast-Adresse sie beachten sollen, wenn sie das Netz nicht kennen. Bis eine IP-Adresse ausgemacht ist, wird 0.0.0.0 als Quelle und 255.255.255.255 als Ziel verwendet. Bzw. über MAC-Adressierung. Wieso hält sich Dein dhcp-Server nicht daran? Eine route sollte dazu nicht notwendig sein. Ist mir ehrlich unverständlich. -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: DHCP: /etc/route.conf oder /etc/init.d/network ?
Hallo Michael! !SORRY! ^ -Original Message- From: Michael Tuschik [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 5:36 PM To: [EMAIL PROTECTED] Subject: AW: DHCP: /etc/route.conf oder /etc/init.d/network ? Kann deine komische Software keine Einleitungszeile erzeugen? Vielleicht hilft ja ein Update. :-/ Wenn Du mit komischer Software mein Outlook meinst, da hilft nix, nur deinstallieren ... Damit war ich wohl gemeint. 8| Ja, damit warst Du gemeint ... Mittlerweile bin ich auch draufgekommen, was ich da falsch gemacht habe, dass keine Einleitungszeile mitgekommen ist! Bitte um Entschuldigung dafür! Outlook war gar schuld dran, sondern ich selbst! Aber Outlook werd ich doch deinstallieren, denn unter Debian wirds wahrscheinlich eh nicht mehr laufen ;o) -- Liebe Grüße aus Wien Karin http://gerbrich.at/ http://blue-danube-cup.org/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: /etc/route.conf oder /etc/init.d/network ?
Hallo Karin, hallo Johannes, Ich möchte meinen Woody jetzt auch als DHCP-Server einsetzen. ich habe in meinem Netz nur statische IPs, aber... hmm - es gibt /etc/networks (Datei: Inhalt bei mir localnet 192.168.0.0) und auch /etc/network (Ordner) und in /etc/init.d habe ich mit network /etc/init.d/networking (Woody) vielleicht hilft dir das ja weiter ;) vielleicht hilft dir das ja weiter: - Notebook mit woody als Client im Netz - /etc/gateways -leer - /etc/hosts 127.0.0.1 localhost 192.168.0.38ufgnb.jg-computing.localufgnb (das ist das Notebook) 192.168.0.9 printserver.jg-computing.local printserver - /etc/networks localnet 192.168.0.0 - /etc/resolv.conf search jg-computing.local nameserver 194.120.12.245 (sap-Nameserver) - /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static adress 192.168.0.38 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 Gruß Ulrich -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: /etc/route.conf oder /etc/init.d/network ?
Hallo Karin, Hallo Liste, ich benutze kein dhcp für die Adressvergabe, habe aber trozdem eine Idee wie Du Dein Problem schnell und unkompliziert lösen kannst: Du könntest einfach ein eigens script erstellen was den Befehl: route add -host 255.255.255.255 dev eth0 ausführt, und dieses dann in /etc/init.d platzieren und es dann mit einer höheren Priorität als /etc/init.d/dhcp ausstatten, so das es vor dem dhcp script aufgerufen wird, somit wäre sichergestellt das die route vor der dhcp Adressvergabe gesetzt wird. Gruß andreas well -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: /etc/route.conf oder /etc/init.d/network ?
ein fröhliches 'Hallo Andreas'! -Original Message- From: andreas well [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 8:45 PM To: Karin Gerbrich Cc: [EMAIL PROTECTED] Subject: Re: /etc/route.conf oder /etc/init.d/network ? Du könntest einfach ein eigens script erstellen was den Befehl: route add -host 255.255.255.255 dev eth0 ölsfbm knrok6ijhrtjecv öelsor porf ork üojr wopjrc woirj csh coihrkuhc ithr Was diesen Buchstabensalat eine Zeile höher erzeugt hat, war mein Gesicht, das mehrmals auf die Tastatur aufgeschlagen hat! Das man auf die einfachsten Lösungen nicht selber draufkommt! Erledigt, neugestartet, funktioniert (na klar) Danke! Danke an alle, die mir in diesem Thread geholfen haben!! Und liebe Grüße aus Wien nach Deutschland Karin -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: /etc/route.conf oder /etc/init.d/network ?
- Original Message - From: Karin Gerbrich [EMAIL PROTECTED] To: andreas well [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 22, 2002 9:03 PM Subject: RE: /etc/route.conf oder /etc/init.d/network ? -Original Message- From: andreas well [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 8:45 PM To: Karin Gerbrich Cc: [EMAIL PROTECTED] Subject: Re: /etc/route.conf oder /etc/init.d/network ? Du könntest einfach ein eigens script erstellen was den Befehl: route add -host 255.255.255.255 dev eth0 Das man auf die einfachsten Lösungen nicht selber draufkommt! Erledigt, neugestartet, funktioniert (na klar) Mmh, mich würde aber trotzdem interessieren, wieso nun manche diese route brauchen und andere nicht. Haengt das von Kernelversionen ab? -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
RE: /etc/route.conf oder /etc/init.d/network ?
Hi Markus -Original Message- From: Markus Kolb [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 9:41 PM To: [EMAIL PROTECTED] Subject: Re: /etc/route.conf oder /etc/init.d/network ? Mmh, mich würde aber trotzdem interessieren, wieso nun manche diese route brauchen und andere nicht. Haengt das von Kernelversionen ab? Bei mir läuft Woody mit 2.4.17, also dem aktuellsten stabilen Kernel ... Ich glaube, es hängt irgendwie mit der Konfiguration des WinDoof-Clients ab, denn das Prob tritt AFAIK nur im Zusammenhang mit WinDoof-Clients auf! Linux-Clients brauchen diese route nicht! -- Liebe Grüße aus Wien Karin http://gerbrich.at/ http://blue-danube-cup.org/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
DHCP: /etc/route.conf oder /etc/init.d/network ?
Hallo Liste! Ich möchte meinen Woody jetzt auch als DHCP-Server einsetzen. In verschiedenen HowTo's lese ich, dass vor Start von dhcp unbedingt die Route gesetzt werden muss: route add -host 255.255.255.255 dev eth0 Um sich händische Aufrufen zu ersparen, könne man auch in die /etc/route.conf folgendes dazuschreiben: 255.255.255.255 0.0.0.0 255.255.255.255 eth0 Uuups, die /etc/route.conf gibts bei mir nicht, auch keine /etc/init.d/network die IMHO bei Debian doch die /etc/route.conf ersetzen sollte! Oder hab ich da etwa was falsch verstanden? -- Liebe Grüße aus Wien Karin http://gerbrich.at/ http://blue-danube-cup.org/ -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: /etc/init.d/network v. /etc/network/*
On Thu, Sep 21, 2000 at 03:01:05PM -0500, will trillich ([EMAIL PROTECTED]) wrote: On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote: Could someone set me straight on the distinction between /etc/init.d/network and the definition files under /etc/network: interfaces, options, and spoof-protect. We've got a balky server which doesn't like coming on-line (and occasionally likes going off) when it boots. I suspect multiple network config upfsckage. Docs I've been able to find are less than crystal on the distinction between these files. what i've seen says that /etc/init.d/* are SCRIPTS that are run when entering various runlevels (rcS at startup, rc2 when entering runlevel 2...) and /etc/network/* are the CONFIGURATION files for various network facilities. % man interfaces will tell you about the /etc/network/interfaces file. I'd pretty much worked that much out. The standard (or old-style) /etc/init.d/network script isn't a typical init.d script, however. It doesn't have the typical start | stop | reload | restart | status switches. What /etc/init.d/network *does* say is: # In new Debian installations, this file is deprecated in favour of # the ifup/ifdown commands (invoked from /etc/init.d/networking), # which can be configured from the file /etc/network/interfaces. So -- should I configure /etc/network/interfaces, delete /etc/init.d/network, and pray everything works from /etc/init.d/networking? That seems to be the plan. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgp6kFt7ZrDI0.pgp Description: PGP signature
Re: /etc/init.d/network v. /etc/network/*
Quoth kmself@ix.netcom.com, So -- should I configure /etc/network/interfaces, delete /etc/init.d/network, and pray everything works from /etc/init.d/networking? I had a machine which somehow managed to get assigned a wrong default gateway, which was causing me all sorts of grief. I eventually worked out (through the suggestion of someone on the list) that I hadn't deleted my old /etc/init.d/network file, which was also trying to set network parameters. Deleting this file solved my problem. The moral of the story is that if you just stick with the debian-approved (and quite simple and powerful) networking and interfaces file, life can be easier. Might not fix your problem, but it should make it easier for you troubleshoot. cheers, damon -- Damon Muller | Did a large procession wave their torches Criminologist/Linux Geek | As my head fell in the basket, http://killfilter.com | And was everybody dancing on the casket... PGP (GnuPG): A136E829 | - TBMG, Dead pgph0Mqycj0DN.pgp Description: PGP signature
Re: /etc/init.d/network v. /etc/network/*
On Mon, Sep 18, 2000 at 06:26:47PM -0700, kmself@ix.netcom.com wrote: Could someone set me straight on the distinction between /etc/init.d/network and the definition files under /etc/network: interfaces, options, and spoof-protect. We've got a balky server which doesn't like coming on-line (and occasionally likes going off) when it boots. I suspect multiple network config upfsckage. Docs I've been able to find are less than crystal on the distinction between these files. what i've seen says that /etc/init.d/* are SCRIPTS that are run when entering various runlevels (rcS at startup, rc2 when entering runlevel 2...) and /etc/network/* are the CONFIGURATION files for various network facilities. % man interfaces will tell you about the /etc/network/interfaces file.
/etc/init.d/network v. /etc/network/*
Could someone set me straight on the distinction between /etc/init.d/network and the definition files under /etc/network: interfaces, options, and spoof-protect. We've got a balky server which doesn't like coming on-line (and occasionally likes going off) when it boots. I suspect multiple network config upfsckage. Docs I've been able to find are less than crystal on the distinction between these files. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgprZxZiQKpnb.pgp Description: PGP signature
/etc/init.d/networking vs. /etc/init.d/network
In potato's netbase, the network script has been replaced by networking. In an upgrade from slink the old script and its symlinks in /etc/rc*.d are retained, however. While this still works, is it likely to cause compatibility problems in the future (woody and beyond)? Bob -- Bob Nielsen, N7XY [EMAIL PROTECTED] Bainbridge Island, WA http://www.oz.net/~nielsen
Re: /etc/init.d/networking vs. /etc/init.d/network
On Wed, Aug 09, 2000 at 11:18:06AM -0700, Bob Nielsen wrote: In potato's netbase, the network script has been replaced by networking. In an upgrade from slink the old script and its symlinks in /etc/rc*.d are retained, however. While this still works, is it likely to cause compatibility problems in the future (woody and beyond)? Bob Hi Bob. As I understand it, some of the semantics will change when you go from a 2.0.3x kernel to a 2.2.x and the new networking scripts will help work through that. There was a thread a couple months back about this. You'll get an SIOC error at boot with a 2.2.x kernel and the Slink network script. Anyhow, it is documented in the list archives and if I recall, that was sometime back aroun May. Switching to the new format is rather painless with a straightforward network configuration. man interfaces is a good resource. 73, de Nate -- Wireless | Amateur Radio Station N0NB | None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license. http://www.qsl.net/n0nb/ | -- John Milton
Re: MUAs (was Re: Help with the /etc/init.d/network)
On Thu, May 18, 2000 at 08:04:26PM -0700, Karl M. Hegbloom wrote: I didn't like Netscrape for mail - Nor do I, however ... it word wraps in the wrong places and to put mail in separate folders you've either got to monkey around with `procmail' or endlessly drag and drop from Inbox to your sort folders. ... this is not true. Netscape does indeed have filtering / sorting capability. It's not as easy to use as exim's, nor is it as flexible. But it does exist. Also as I remember the word wrap is configurable. It's been long enough since I used it that I'd have to go back and check as to where the menus for each were hidden away. But they most assuredly were there last time I used them. -- Mike Werner KA8YSD | Where do you want to go today? | As far from Redmond as possible! '91 GS500E| Morgantown WV | Only dead fish go with the flow.
Re: MUAs (was Re: Help with the /etc/init.d/network)
Actually it's not hard in netscape to perform filtering. If whateverbitofmsg (eg to, sender etc) contains blah then move to folder (or whatever action you want.) Word wrap is in Edit/Preferences/Mail and Newsgroups/Messages/Message Wrapping Peter. Mike Werner wrote: ... this is not true. Netscape does indeed have filtering / sorting capability. It's not as easy to use as exim's, nor is it as flexible. But it does exist. Also as I remember the word wrap is configurable. It's been long enough since I used it that I'd have to go back and check as to where the menus for each were hidden away. But they most assuredly were there last time I used them. -- Mike Werner KA8YSD | Where do you want to go today? | As far from Redmond as possible! '91 GS500E| Morgantown WV | Only dead fish go with the flow. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- In the beginning, the universe was created. This made a lot of people very angry, and has been widely regarded as a bad idea. *** *Peter GoodEmail: [EMAIL PROTECTED] *Pete's Internet Services Sales: [EMAIL PROTECTED] * *http://www.petesinternet.net Phone: 0401 283 482* *Morayfield QLD Australia * ***
Re: MUAs (was Re: Help with the /etc/init.d/network)
[EMAIL PROTECTED] (Ethan Benson) writes: [...] the only MUA for *nix that includes an MTA is bloatscape communicator. Or you can look at xfmail. I've used it a long time (but now I'm using gnus), and it's easy to setup. Inlucdes code for POP3 and IMAP, can talk SMTP. Burkhard
RE: MUAs (was Re: Help with the /etc/init.d/network)
Thanks to all for the MUA advice. I can see that I'm going to have to learn some new things (again), like MTAs. Linux has an amazing ability to laugh at your years as a computer professional make you feel like an idiot. But that's what's so [EMAIL PROTECTED] great about it. A. Scott White Director of Information Systems and Product Strategy Healthcare Solutions Group Affiliated Computer Services, Inc. [EMAIL PROTECTED]
Re[2]: MUAs (was Re: Help with the /etc/init.d/network)
Friday, May 19, 2000, 9:04:17 AM, A. wrote: Thanks to all for the MUA advice. I can see that I'm going to have to learn some new things (again), like MTAs. Linux has an amazing ability to laugh at your years as a computer professional make you feel like an idiot. Actually I'd not do that. This is the one area where I think the unix community gets it backwards. They proudly proclaim that there are three separate processes involved with mail. The MTA, MDA and MUA. They say all three should be separate at all times. However, look at it another way. The email client is the /only/ client that doesn't transfer its own data! We don't have the Web User Agent that relies upon the Web Transfer Agent to retrieve web pages, do we? No. We don't have the FTP User Agent relying upon the FTP Transfer Agent to make the actual transfer of data possible, do we? No. We don't have a News Users Agent relying upon a News Transport Agent to send to a News Delivery Agent to score/filter the news so we can read it, do we? No. We have web proxies, FTP proxies and leaf news servers. However, in each case they are not /required/ for operation of the client software, they can just be added to the software for more robust operation /if needed/. They the hell, then, do we make a glaring exception that email is the only /client/ that requires a proxy-like operation to be considered normal. Just like the other services it should be able to pull/filter and send its own data /as well as/ make allowances for more robust, external programs to perform those functions. -- Steve C. Lamb | I'm your priest, I'm your shrink, I'm your ICQ: 5107343 | main connection to the switchboard of souls. ---+-
Re: Help with the /etc/init.d/network
Ethan == Ethan Benson [EMAIL PROTECTED] writes: Pardon my ignorance. I had no idea that any mechanism for tracking threads existed other than the subject line. I'll keep that in mind. =20 Incidentally, how exactly does thread tracking work? I assume there is a header of some kind. Maybe I'll hack it out. Interesting. Ethan most non-broken mailers include a reference header, i see you use MS Ethan Worm+Virus Develop... er Outlook. i am quite impressed they actually Ethan bothered to implement this feature correctly... Is that what does all that weird line splitting with the equal signs and stuff? -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom)
Re: Help with the /etc/init.d/network
On Wed, May 17, 2000 at 10:13:51PM -0700, Karl M. Hegbloom wrote: Ethan == Ethan Benson [EMAIL PROTECTED] writes: Pardon my ignorance. I had no idea that any mechanism for tracking threads existed other than the subject line. I'll keep that in mind. =20 Incidentally, how exactly does thread tracking work? I assume there is a header of some kind. Maybe I'll hack it out. Interesting. Ethan most non-broken mailers include a reference header, i see you use MS Ethan Worm+Virus Develop... er Outlook. i am quite impressed they actually Ethan bothered to implement this feature correctly... Is that what does all that weird line splitting with the equal signs and stuff? that is because outlook is broken and does not understand RFC2015. -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) -- Ethan Benson http://www.alaska.net/~erbenson/ pgpGaPnChar3y.pgp Description: PGP signature
RE: Help with the /etc/init.d/network
Ethan Benson wrote: that is because outlook is broken and does not understand RFC2015. What Linux MUA should I use. I'd like one that has a complete feature set and doesn't rely on X (I don't like X). Also, most of the MUA's I've looked at don't clearly define a way to specify checking a corporate SMTP server. They all seem to want to check the mail on the Linux box itself. I'm really not interested in using this Linux box as a mail server, as I already have an SMTP server. I just want to use it to check mail. Thanks. A. Scott White Director of Information Systems and Product Strategy Healthcare Solutions Group Affiliated Computer Services, Inc. [EMAIL PROTECTED]
MUAs (was Re: Help with the /etc/init.d/network)
On Thu, May 18, 2000 at 11:28:15AM -0500, A. Scott White wrote: Ethan Benson wrote: that is because outlook is broken and does not understand RFC2015. What Linux MUA should I use. I'd like one that has a complete feature set and doesn't rely on X (I don't like X). if you don't like X you must really hate windows :P for MUAs mutt is very nice, and is console based. Also, most of the MUA's I've looked at don't clearly define a way to specify checking a corporate SMTP server. They all seem to want to check the mail on the Linux box itself. I'm really not interested in using this Linux box as a mail server, as I already have an SMTP server. I just want to use it to check mail. the only MUA for *nix that includes an MTA is bloatscape communicator. the reason is in un*x the philosophy is for a tool to do one job and do that job very well, which means you have many small tools that you put together to do powerful and useful things. the reason MUAs under un*x do not support SMTP is because it is not thier job. MS is the one who `innovated' snicker the idea of making bloated MUAs that include an entire MTA. for your situation you should run an MTA that relays all mail (except local mail) to your corporate SMTP server for delivery, and use fetchmail to fetch your mail from the corporate server and deliver to your local MTA, this is really quite easy to set up (especially if you are not cursed with a NAT setup) postfix will allow you to setup the smtp daemon to only listen on certian interfaces iirc, so you could have it listen only on localhost and not worry about having a smpt port open. the fact that MUAs don't inlcude MTAs (ie support smpt) is a FEATURE not a flaw, it makes them smaller and faster. if you are absolutly unwilling to setup the MTA on your system then i would have to suggest that you just stay with your win* mailer as your options will be very limited for a *nix MUA. IMHO nothing compares to mutt as a MUA, but it is not bloated by including a Mail transport agent. -- Ethan Benson http://www.alaska.net/~erbenson/
Re: Help with the /etc/init.d/network
A == A Scott White [EMAIL PROTECTED] writes: A Ethan Benson wrote: that is because outlook is broken and does not understand RFC2015. A What Linux MUA should I use. I'd like one that has a complete feature set A and doesn't rely on X (I don't like X). Gnus in XEmacs is the best there is. Use `nnml' for mail with the `fancy' splitting. RTFM. It's well worth the effort to get it configured. -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom)
Re: MUAs (was Re: Help with the /etc/init.d/network)
Ethan == Ethan Benson [EMAIL PROTECTED] writes: Ethan the only MUA for *nix that includes an MTA is bloatscape Ethan communicator. It's better to install a MTA, like `exim', `postfix', or `sendmail'. You can set it up so it doesn't accept connections from the net if you like. I didn't like Netscrape for mail - it word wraps in the wrong places and to put mail in separate folders you've either got to monkey around with `procmail' or endlessly drag and drop from Inbox to your sort folders. Go with `gnus' if you've got a lot of mail, and with `vm' if you've got not too much. Both work very well in XEmacs, the finest text editor on the planet. (soon to have gtk widgetry!) -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom)
Re: Help with the /etc/init.d/network
On Wed, May 17, 2000 at 01:38:19PM +1000, Matthew Dalton wrote:
A. Scott White wrote:
Can anyone tell me exactly what this line accomplishes:
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
if the $GATEWAY variable has been set, run the command 'route add
default gw ${GATEWAY} metric 1.
The [ and ] are synonyms for the 'test' program. In this case, if
$GATEWAY is set, test returns 1, otherwise it returns 0. The return
you got that backwords, when $GATEWAY is set `test' returns 0 not 1.
0 == success
1 == failure
to the original poster, reply change subject != new message
the former screws up threading in mailing list archives and in MUAs
such as mutt. please always create a new message and paste the list
address in instead of using reply as a shortcut, or if you post often
create an alias/address book entry for the list address. thank you.
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpX7LYsJ2yZn.pgp
Description: PGP signature
RE: Help with the /etc/init.d/network
Ethan: to the original poster, reply change subject != new message ... the former screws up threading in mailing list archives and in MUAs such as mutt. please always create a new message and paste the list address in instead of using reply as a shortcut, or if you post often create an alias/address book entry for the list address. thank you. I always new I was being watched. Pardon my ignorance. I had no idea that any mechanism for tracking threads existed other than the subject line. I'll keep that in mind. Incidentally, how exactly does thread tracking work? I assume there is a header of some kind. Maybe I'll hack it out. Interesting. Well, you learn something new everyday (especially when you don't know much). Thanks. A. Scott White Director of Information Systems and Product Strategy Healthcare Solutions Group Affiliated Computer Services, Inc. [EMAIL PROTECTED]
Re: Help with the /etc/init.d/network
On Wed, May 17, 2000 at 09:14:17AM -0500, A. Scott White wrote: Ethan: to the original poster, reply change subject != new message ... the former screws up threading in mailing list archives and in MUAs such as mutt. please always create a new message and paste the list address in instead of using reply as a shortcut, or if you post often create an alias/address book entry for the list address. thank you. I always new I was being watched. : Pardon my ignorance. I had no idea that any mechanism for tracking threads existed other than the subject line. I'll keep that in mind. Incidentally, how exactly does thread tracking work? I assume there is a header of some kind. Maybe I'll hack it out. Interesting. most non-broken mailers include a reference header, i see you use MS Worm+Virus Develop... er Outlook. i am quite impressed they actually bothered to implement this feature correctly... here is the appropriate header in your message: -- In-Reply-To: [EMAIL PROTECTED] ^^ that is known as the message id, its essentially random_crap@hostname in my case my fake hostname since im on a masqeraded network but thats irrelevant the point is its a reasonably unique string that identifies the message. the other pet peeve of thread lovers is broken clients who don't include that header in which case the thread gets broken... Well, you learn something new everyday (especially when you don't know much). Thanks. np. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpqcNeMTt6Ki.pgp Description: PGP signature
Re: Help with the /etc/init.d/network
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, A. Scott White [EMAIL PROTECTED] writes: Incidentally, how exactly does thread tracking work? I assume there is a header of some kind. Maybe I'll hack it out. Interesting. The In-Reply-To: header field has the message-id of the article you're replying to. Also, some mail readers insert a References: header which has the message-id of previous articles too. - -- Graeme. [EMAIL PROTECTED] Life's not fair, I reply. But the root password helps. - BOFH -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) iD8DBQE5IuJIPjGH3lNt65URAnQeAJ4/RI5QDA6ELrkMSAmXLUgaQKIHxwCgtT2M dMwubAhxoJN9Ablm4wZ+y6o= =YDQ3 -END PGP SIGNATURE-
Help with the /etc/init.d/network
Can anyone tell me exactly what this line accomplishes:
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
I'm pretty sure it adds the default gateway setting for TCP/IP, but I don't
understand what it means, exactly. Could you explain:
1. The script syntax
2. the commands involved
I'd appreciate it. Thanks.
A. Scott White
Director of Information Systems and Product Strategy
Healthcare Solutions Group
Affiliated Computer Services, Inc.
[EMAIL PROTECTED]
Re: Help with the /etc/init.d/network
A. Scott White wrote:
Can anyone tell me exactly what this line accomplishes:
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
if the $GATEWAY variable has been set, run the command 'route add
default gw ${GATEWAY} metric 1.
The [ and ] are synonyms for the 'test' program. In this case, if
$GATEWAY is set, test returns 1, otherwise it returns 0. The return
value from test determines whether the rest of the line is executed,
because of the (logical AND). The commands on this line are executed
left to right. However, if the first (the test) results in 0, then the
result of the logical AND can never be 1, so the second command is not
executed -- it works like an if statement basically.
Matthew
RE: Help with the /etc/init.d/network
`[' (the `test' command) is used to evaluate the GATEWAY environment
variable. `' is a shell control operator to evaluate an AND list. It is
often used like this instead of an if/then construct. The `route' command is
only executed if the test evaluated to zero, i.e., GATEWAY is set.
For details, see the manual pages for `[' (or `test'), `bash' (or your
particular shell) and `route'.
Andreas
-Original Message-
From: A. Scott White [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 17, 2000 11:05
To: debian-user@lists.debian.org
Subject: Help with the /etc/init.d/network
Can anyone tell me exactly what this line accomplishes:
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
I'm pretty sure it adds the default gateway setting for
TCP/IP, but I don't
understand what it means, exactly. Could you explain:
1. The script syntax
2. the commands involved
I'd appreciate it. Thanks.
A. Scott White
Director of Information Systems and Product Strategy
Healthcare Solutions Group
Affiliated Computer Services, Inc.
[EMAIL PROTECTED]
/etc/init.d/network script missing .... help needed please
I just installed a Debian 2.1 stable machine. Since it has a Token Ring adapter I skipped the configure the network step during installation. I have recompiled a kernel 2.2.13 and have tr0. My /etc/init.d is missing the network script ... is there a source from which I could get it/create it ??? What update-rc.d command should I use to place the right links in the right runlevels ??? Thank you very much. Bob Alexander PS I now have an horrible tem. patch : i run the ifconfig and route add in the netstd_init script works but it's not clean
Re: How to edit /etc/init.d/network?
Paul Nathan Puri wrote: So that my computer will apply the ipchains commands, the ipforward command in echo, the ifconfig, etc... at boot? I'm definitely not a networking guru, but I'll take a shot at it. First of all, if you haven't already, take a look at the recently updated IP Masq HOWTO found at the link below. It explains most everything you need to know including what's needed for 2.2.X vs 2.0.X kernels. http://www.tor.shaw.wave.ca/~ambrose/ipmasq-HOWTO.html#toc3 As a simple example, here's my /etc/init.d/network for the gateway machine on a 2 computer home network. I'm using the plip device (parallel port cable) instead of network cards, but it's the same idea. I'm using kernel 2.2.3 now. #! /bin/sh ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.0.0.0 dev lo ifconfig plip0 192.168.1.1 pointopoint 192.168.1.2 up route add -net 192.168.1.0 netmask 255.255.255.0 dev plip0 echo 1 /proc/sys/net/ipv4/ip_forward ipchains -P forward DENY ipchains -A forward -s 192.168.1.0/24 -j MASQ # these were used with kernels 2.0.XX instead of ipchains # ipfwadm -F -p deny # ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0 - You also have to set the default route on the machine(s) that will be using the gateway machine to access the Internet or whatever. Here's how I have the /etc/init.d/network file set up on my other machine: --- #! /bin/sh ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.0.0.0 dev lo ifconfig plip0 192.168.1.2 pointopoint 192.168.1.1 up route add -net 192.168.1.0 netmask 255.255.255.0 dev plip0 route add default gw 192.168.1.1 Tom -- Try Debian GNU/Linux - it's free, it's open source, and it rocks http://www.debian.org
How to edit /etc/init.d/network?
So that my computer will apply the ipchains commands, the ipforward command in echo, the ifconfig, etc... at boot? NatePuri Certified Law Student Debian GNU/Linux Monk McGeorge School of Law [EMAIL PROTECTED] http://ompages.com
What package sets up /etc/init.d/network?
What package sets up /etc/init.d/network ? After a new install on a laptop (for which I might have replied that there was no network for some configuration question), I'm left without even a loopback configured. I could hack it in myself, but... -- Peter Galbraith, research scientist [EMAIL PROTECTED] Maurice Lamontagne Institute, Department of Fisheries and Oceans Canada P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada. 418-775-0852 FAX:418-775-0546 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: What package sets up /etc/init.d/network?
In article [EMAIL PROTECTED], Peter S Galbraith [EMAIL PROTECTED] wrote: What package sets up /etc/init.d/network ? Only a new installation configures it in the setup. After a new install on a laptop (for which I might have replied that there was no network for some configuration question), I'm left without even a loopback configured. I could hack it in myself, but... That's what you're supposed to do. Mike. -- Miquel van Smoorenburg | The dyslexic, agnostic, insomniac lay in his bed [EMAIL PROTECTED] | awake all night wondering if there is a doG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
/etc/init.d/network
Howdy all. I've got one machine that's really got me stumped. I've been with Debian since before 0.91 was released - I've installed Debian on several systems, many times. Yet this one's tough... The systems is running on an AMI Titan III M/B w/ 32MB RAM. Dual Pentium Processors (so I guess they both will choke on that opcode...:) two quantum 3.2GB SCSI drives plus the usual complement of Floppy/CD-ROM/ tape drive. I've had two network cards in this machine: first, an HP 100VG PCI and then an Eagle NE2000 ISA. Both exhibit the same problem. Which is... When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- checked, and even had a friend check that there were no hardware conflicts. Interrupts and IO addresses are all fine. I've tried compiling the drivers into the kernel and as loadable modules - nothing seems to help this problem. Does anyone have any suggestions? I can provide several K bytes worth of files if someone wants to take a look at them. So far everything's fairly straight out of the box on this system. Running the Official Debian CD release 1.3.1, though I've recently started migrating to the libc6 tree. Comments and suggestions welcome. Thanks. Chuck -- Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED] Practical Network DesignVoice: (419) 529-3841 9 Chambers Road FAX:(419) 529-3625 Mansfield, OH 44906-1302 USA -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
Did you try sticking an ifconfig in at the end of /etc/init.d/network to see if the interface is up at that particular moment? Maybe something else is shutting it down somewhere else ??? Later, Kevin -Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: debian-user@lists.debian.org debian-user@lists.debian.org Date: Thursday, November 13, 1997 2:18 PM Subject: /etc/init.d/network Howdy all. I've got one machine that's really got me stumped. I've been with Debian since before 0.91 was released - I've installed Debian on several systems, many times. Yet this one's tough... The systems is running on an AMI Titan III M/B w/ 32MB RAM. Dual Pentium Processors (so I guess they both will choke on that opcode...:) two quantum 3.2GB SCSI drives plus the usual complement of Floppy/CD-ROM/ tape drive. I've had two network cards in this machine: first, an HP 100VG PCI and then an Eagle NE2000 ISA. Both exhibit the same problem. Which is... When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- checked, and even had a friend check that there were no hardware conflicts. Interrupts and IO addresses are all fine. I've tried compiling the drivers into the kernel and as loadable modules - nothing seems to help this problem. Does anyone have any suggestions? I can provide several K bytes worth of files if someone wants to take a look at them. So far everything's fairly straight out of the box on this system. Running the Official Debian CD release 1.3.1, though I've recently started migrating to the libc6 tree. Comments and suggestions welcome. Thanks. Chuck -- Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED] Practical Network Design Voice: (419) 529-3841 9 Chambers Road FAX: (419) 529-3625 Mansfield, OH 44906-1302 USA -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote: I've had two network cards in this machine: first, an HP 100VG PCI and then an Eagle NE2000 ISA. Both exhibit the same problem. Which is... Are you using them as modules or did you compile the drivers in? Just a random guess.. I tried it with them both as modules (one at a time, and both together) and I tried it with each compiled in (also one at a time and together). The symptom did not change in any of those cases. Cheers, Joost -- Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED] Practical Network DesignVoice: (419) 529-3841 9 Chambers Road FAX:(419) 529-3625 Mansfield, OH 44906-1302 USA -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
[EMAIL PROTECTED] wrote: Howdy all. I've had two network cards in this machine: first, an HP 100VG PCI and then an Eagle NE2000 ISA. Both exhibit the same problem. Which is... When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- checked, and even had a friend check that there were no hardware conflicts. Interrupts and IO addresses are all fine. I've tried compiling the drivers into the kernel and as loadable modules - nothing seems to help this problem. Does anyone have any suggestions? I can provide several K bytes worth of files if someone wants to take a look at them. So far everything's fairly straight out of the box on this system. Running the Official Debian CD release 1.3.1, though I've recently started migrating to the libc6 tree. Comments and suggestions welcome. Thanks. Chuck -- Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED] Practical Network DesignVoice: (419) 529-3841 9 Chambers Road FAX:(419) 529-3625 Mansfield, OH 44906-1302 USA Well... in the /etc/init.d/network file is the following lines inserted? /sbin/ifconfig eth0 up /sbin/ifconfig eth0 host_name netmask 255.255.255.0 Add the kernel routing table /sbin/route add -net 198.168.1.0 dev eth0 /sbin/route add -host host_name dev eth0 And finally I display the kernel's routing table # display route table /bin/netstat -rn I have found that by adding items to the display I have found the cause of many hidden problems. Have a good day :-) -- 0 0 http://www.netaxs.com/~ldc/ ___ooO ~ Ooo___ LeRoy D. Cressy /\_/\ [EMAIL PROTECTED] Computer Consulting ( o.o ) (215) 389-5870 ^ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
Hi Chuck, This sort of thing can happen if you have a domain name in .../networks instead of an IP number. Another time it happened to me when I did a tidy-up of /etc/hosts and removed an important domain-IP pairing. When you say .../networks you mean /etc/networks - right? Why is the system sensitive to domain names in that file? Is it because it forces a DNS lookup and named hasn't started yet? How about getting the script to print out all the variables just before it uses them? $GATEWAY and so on. I did that. All of the variables are getting assigned properly. If you still need help I would be happy to take a look at your files. I've found a kludge - added a sym-link from /etc/rc?.d/S99network to /etc/init.d/network. I'm going to try one of the other suggestions I got about adding an ifconfig to the end of /etc/init.d/network to see if the interface is up at that time. Maybe it's as you suggested that an improperly configured file is preventing the interface from loading, maybe it's getting loaded and then brought back down. We'll see later this after noon. Lindsay Thanks for your time. Chuck -- Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED] Practical Network DesignVoice: (419) 529-3841 9 Chambers Road FAX:(419) 529-3625 Mansfield, OH 44906-1302 USA -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
Well...
in the /etc/init.d/network file is the following lines inserted?
/sbin/ifconfig eth0 up
/sbin/ifconfig eth0 host_name netmask 255.255.255.0
Add the kernel routing table
/sbin/route add -net 198.168.1.0 dev eth0
/sbin/route add -host host_name dev eth0
Here's my /etc/init.d/network stripped of comments and some echo statements:
#!/bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=198.187.226.21
NETMASK=255.255.255.0
NETWORK=198.187.226.0
BROADCAST=198.187.226.255
GATEWAY=205.242.10.253
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
route add default gw ${GATEWAY} metric 1
This is the same format that is used on another system (also Debian)
that is working fine. The other system is Debian 1.2.whatever. With
pieces of 1.3.whoknows.
And finally I display the kernel's routing table
# display route table
/bin/netstat -rn
I like this idea! That and adding ifconfig at the end. They both should
be part of the file's default configuration.
I have found that by adding items to the display I have found the
cause of many hidden problems.
We'll see how well those problems can hide now...
Have a good day :-)
LeRoy D. Cressy/\_/\ [EMAIL PROTECTED]
Thanks!
Chuck
--
Chuck Stickelman, Owner E-Mail: [EMAIL PROTECTED]
Practical Network DesignVoice: (419) 529-3841
9 Chambers Road FAX:(419) 529-3625
Mansfield, OH 44906-1302 USA
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
On Thu, 13 Nov 1997 [EMAIL PROTECTED] wrote: When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- Hi, I think it's with a daemon called dhcpd that's causing me problem like that a few months ago. You could try to disable them first. I might be wrong could you give me a listing of your process? (ps -ax would be fine). regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Andre M. Varon Lasaltech Incorporated Technical Head Fax-Tel: (034)435-0836 e-mail : [EMAIL PROTECTED] web page: http://www.lasaltech.com/andre.html =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: /etc/init.d/network
-Original Message- From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: debian-user@lists.debian.org debian-user@lists.debian.org Date: Thursday, November 13, 1997 7:19 AM Subject: /etc/init.d/network Howdy all. I've got one machine that's really got me stumped. I've been with Debian since before 0.91 was released - I've installed Debian on several systems, many times. Yet this one's tough... The systems is running on an AMI Titan III M/B w/ 32MB RAM. Dual Pentium Processors (so I guess they both will choke on that opcode...:) two quantum 3.2GB SCSI drives plus the usual complement of Floppy/CD-ROM/ tape drive. I've had two network cards in this machine: first, an HP 100VG PCI and then an Eagle NE2000 ISA. Both exhibit the same problem. Which is... When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- checked, and even had a friend check that there were no hardware conflicts. Interrupts and IO addresses are all fine. I've tried compiling the drivers into the kernel and as loadable modules - nothing seems to help this problem. Does anyone have any suggestions? I can provide several K bytes worth of files if someone wants to take a look at them. So far everything's fairly straight out of the box on this system. Running the Official Debian CD release 1.3.1, though I've recently started migrating to the libc6 tree. Comments and suggestions welcome. Thanks. Chuck I had this problem for a while. What fixed it was removing dhcpc. IE DHCP Client. Eth0 is brought up. Later during bootup, dhcpc tries to find an ip address from a dhcp server, can't find one, and sets the address to 0.0.0.0. At least that is what fixed it on my end. Adam Heath [EMAIL PROTECTED] http://wwp.mirabilis.com/3375265 -- Page me -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: /etc/init.d/network
On 13-Nov-97 [EMAIL PROTECTED] wrote: snip When the system boots /etc/init.d/network is run (I know this is true because I added some echo statements watched the screen while it booted.) Anyway, after I boot the eth0 interface is not setup. If I run /etc/init.d/ network by hand afterwards, everything is fine. I've checked, double- checked, and even had a friend check that there were no hardware conflicts. Interrupts and IO addresses are all fine. I've tried compiling the drivers into the kernel and as loadable modules - nothing seems to help this problem. Add some more echo to /etc/init.d/network to find out where it's failing. echo $? shows the exit status of things that run. Also echo any $THINGYs that you have in there. Look at where in the sequence of init files network is being run; use: grep initdefault /etc/inittab #to find out your default run-level ls /etc/rc#.d # where the # character is the run-level discovered above That will show the order that the files in /etc/init.d are run. /etc/init.d/network may need to come later in the sequence. HTH Does anyone have any suggestions? I can provide several K bytes worth of files if someone wants to take a look at them. So far everything's fairly straight out of the box on this system. Running the Official Debian CD release 1.3.1, though I've recently started migrating to the libc6 tree. Comments and suggestions welcome. Thanks. Chuck -- Chuck Stickelman, OwnerE-Mail: [EMAIL PROTECTED] Practical Network Design Voice: (419) 529-3841 9 Chambers RoadFAX:(419) 529-3625 Mansfield, OH 44906-1302 USA -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . - Ralph Winslow [EMAIL PROTECTED] The IQ of the group is that of the member whose IQ is lowest divided by the number of members. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
