Azzz
Sent from my iPhoneapp.pp0-0--
warning:
''SIOCADDRT: Invalid argument''
Now the network does not work.
The same three steps under debian3.0 work fine, but I
rather cannot
update from debian2.2 to debian3.0 because debian2.2
runs on very
old computer so debian3.0 is too heavy for that
computer.
Could you please someone help
/network/interfaces'
3step 'ifup --all'
after the 3step i got the following warning:
''SIOCADDRT: Invalid argument''
Now the network does not work.
SNIP
Could you please someone help me?
I think you'll have to give us more info...
What exactly are the new values for all those things you
warning:
''SIOCADDRT: Invalid argument''
Now the network does not work.
The same three steps under debian3.0 work fine, but I
rather cannot
update from debian2.2 to debian3.0 because debian2.2
runs on very
old computer so debian3.0 is too heavy for that
computer.
Could you please someone help
Hola !
Alguien puede decirme que es?
Sale este mensaje junto despues de cargarse el modulo de la ethernet
textual : SIOCADDRT Network is unreachable.
done
Gracias.
On Wed, May 21, 2003 at 06:58:47PM +0200, francisco wrote:
Hola !
Alguien puede decirme que es?
Sale este mensaje junto despues de cargarse el modulo de la ethernet
textual : SIOCADDRT Network is unreachable.
done
A mi eso me pasó en ocasiones de:
* no corresponde el módulo al nic
: SIOCADDRT
Hola !
Alguien puede decirme que es?
Sale este mensaje junto despues de cargarse el modulo de la ethernet textual
: SIOCADDRT Network is unreachable.
done
Gracias.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL
Donde estan las tablas de ruteo? he de mirar los scripts que levantan la eth
en el directorio network o me sugieres algun otro sitio? alli he mirado y no
he visto nada anormal
gracias de nuevo
Fijate,
Seguro esta tratando de levantar una ethx bajo una red que no
corresponde..
A mi eso me pasó en ocasiones de:
* no corresponde el módulo al nic
* está mal configurada
* algún problema de hard o red
mandá mas datos asi te ayudamos más:
que placa es?
que kernel?
que modulo le cargas?
Creo que esta solucionado, almenos no me sigue dando ese error
pero tengo muchas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hola!,
estoy respondón hoy,
Loading I2O Core - (c) Copyright 1999 Red Hat Software
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
[..]
Creo que no uso nada de eso y no se como se ha metido dentro del kernel !!
me fijé
saf wrote:
melanie:/etc/network# ifconfig eth1 80.236.0.66 netmask 255.255.255.0
melanie:/etc/network# route del default
melanie:/etc/network# route add default gw 192.168.100.1
SIOCADDRT: Network is unreachable
Und wo definierst du das Gateway zwischen 80.236.0.66 und 192.168.100.1
mangels Kompetenz um Murks handelt.
melanie:/etc/network# route add default gw 192.168.100.1
SIOCADDRT: Network is unreachable
Schaue Dir vor diesem Befehl mit route -n die aktuelle Routingtabelle
an. Wo er Recht hat, hat er Recht. Es gibt keine Route zu 192.168.100.1
in Deiner Tabelle. Diese
:/etc/network# route del default
melanie:/etc/network# route add default gw 192.168.100.1
SIOCADDRT: Network is unreachable
Ich schaffe es einfach nicht diese route einzustellen, unter Windows XP geht
es aber! Warum nicht unter Linux?
--
saf at xy1.org
Internet Service Provider Help
http://xy1.org
calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to routing system */
The SIOCADDRT is what operation is reporting the error.
When you
doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to routing system */
The SIOCADDRT is what
or not a NIC is noticed by
the kernel. You said that you insmod'ed them - did you receive any
report that this may have not worked while doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C
while doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to routing system */
The SIOCADDRT is what
Thanks ,
Could someone help in how to add network drivers for debian.
The network card seems to be RTL8129.
Thanks and Regards
Deepak
Hi,
What an ifconfig give you ?
Did you compile it in the kernel ?
Did you configure your /etc/network/interfaces file ?
Give us more informations...
is noticed by
the kernel. You said that you insmod'ed them - did you receive any
report that this may have not worked while doing it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C
Hi,
What an ifconfig give you ?
ifconfig eth0
eth0: error fetching interface information: Device not found
Did you compile it in the kernel ?
I did it, and boot with the new kernel.
I have both 2.2.19 installed from CD and also 2.4.18 (source from
kernel.org).
When I do uname -a, I can
[EMAIL PROTECTED] writes:
Also, when I do make config, I select all default. How do I know,
what card, I have.
Depends on your machine's bus. For pci, use lspci. It has
a verbose option which can be increased with more v's, as in
lspci -vv
With an ISA bus (and PNP devices), use
pnpdump
--
On Thu, 2 May 2002 19:36:00
dkotian3 wrote:
Hi,
What an ifconfig give you ?
ifconfig eth0
eth0: error fetching interface information: Device not found
Hi,
Can you also mail the output of cat /proc/interrupts.
I have a weird feeling that your eth0 will not be listed there,
Thanks
Kapil
: Elizabeth Barham [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Thursday, May 02, 2002 7:53 PM
Subject: Re: SIOCADDRT : No such device
[EMAIL PROTECTED] writes:
Also, when I do make config, I select all default. How do I know,
what card, I have.
Depends on your machine's bus
Hi,
When you configured your kernel (with 'make menuconfig' or 'make
xconfig'), did you select the rtl8139 driver? This is under the
Network Devices options, 10/100 MBPS. I personally suggest compiling
it as a module so that an M shows up next to it in the square
brackets.
For compiling the
' ?
The problem which I am having while setting up route is :
route add -net 192.168.2.0 netmask 255.255.255.0 eth0
SIOCADDRT : No such device
route add default gw 192.168.2.1 eth0
Network unreachable
192.168.2.1 is my gateway to the world and all the computers on the LAN have to
be assigned IP
it?
sockios.h:
/* Routing table calls. */
#define SIOCADDRT 0x890B /* add routing table entry */
#define SIOCDELRT 0x890C /* delete routing table entry */
#define SIOCRTMSG 0x890D /* call to routing system */
The SIOCADDRT is what operation
0.0.0.0 metric 1
When I try this in debian 2.2.3 with kernel 2.4.9 and my card 3com509
configured in the kernel, then I get the message
SIOCADDRT: Network is unreachable
This I get with Debian, Progeny and Demolinux 3.0, but not with Mandrake8.0.
With Mandrake I have no problem getting online
Are you sure that you card is up before you try to connect? Before
you type the dhcpd command, what do you see when you type ifconfig?
Is the module loaded (lsmod)?
Britton wrote:
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas what is going on would be mose welcome.
You have a `route add -net ...` in one of your init scripts (most likely
in /etc/init.d/network). This was needed by the 2.0 kernel
Britton wrote:
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas what is going on would be mose welcome.
IIRC i was having something like that on boot when i've upgraded from slink to
potato, try looking in your /etc/network but don't
On Wed, Jun 20, 2001 at 06:36:24PM +0200, Andrea Vettorello wrote:
Britton wrote:
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas what is going on would be mose welcome.
Hi There,
Don't know if I can be of
Subject: another strange bootup message: SIOCADDRT: Invalid argument
Date: Tue, Jun 19, 2001 at 01:26:51PM -0800
In reply to:Britton
Quoting Britton([EMAIL PROTECTED]):
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas
Oddly, this one does't show up in dmesg. It happens a couple of times
during bootup and thats it. Ideas what is going on would be mose welcome.
Britton Kerin
__
GNU GPL: The Source will be with you... always.
I use my Debian 2.2r2 as a router, but it always shows the message
SIOCADDRT: File exists at boot every time.
I use the kernel 2.2.17 that come with the debian 2.2.
That's because your using the old /etc/init.d/network file, what you can
do is edit that file and comment:
#route add
Hi,
I use my Debian 2.2r2 as a router, but it always shows the message
SIOCADDRT: File exists at boot every time. I use the kernel 2.2.17 that come
with the debian 2.2.
Best regard
u-land
== Mailed via Openfind ==-
http://mail2000.com.tw/ ´£¨Ñ§K¶O¹q¤l¶l¥ó«H½c
Lo del kernel resulta logico... aunque si lo piensas bien el diskette de
instalacion no va leeento.
El error de SIOCADDRT tan solo aparece una vez al arrancar (pero aparece el
100% de las veces).
En fin, gracias por la ayuda y seguire curioseando
pregunta (que no tiene nada que ver con esto)... tengo mi Slink/Corel
1.0 (trozos de ambos lados) al que le recompile el Kernel. Desde que lo he
hecho me da un error SIOCADDRT no encontrado (en ingles) al arrancar. Por lo
que yo se SIOCADDRT forma parte de protocolos de red (hice un grep en las
Hola
Re: Disquette de arranque lento y SIOCADDRT error
A mi tambienm me sucedido lo del arranque lento con disquete ya
hace un tiempo, pero si mal no recuerdo fue en el paso en que se
trata de reconocer los dispositivos Scsi, por lo que supuse que el
Kernel que esta en disquete tiene muchos
On boot up, when my system executes the network init script, it gives the
error:
SIOCADDRT: Invalid Parameters
the network script contains:
ifconfig lo 127.0.0.1
route add -net 127.0.0.1 lo
It's crashing on the route add bit. Shouldn't it be route add -host
instead of -net?
--
Mark
http://members.dingoblue.net.au/~pancreas
Work Email: [EMAIL PROTECTED]
On Mon, 12 Jun 2000, Mark wrote:
On boot up, when my system executes the network init script, it gives the
error:
SIOCADDRT: Invalid Parameters
the network script contains:
ifconfig lo 127.0.0.1
route add -net
says 127.0.0.0 but don't take that for gospel.
Cheers,
Corey Popelier
http://members.dingoblue.net.au/~pancreas
Work Email: [EMAIL PROTECTED]
On Mon, 12 Jun 2000, Mark wrote:
On boot up, when my system executes the network init script, it gives
the
error:
SIOCADDRT: Invalid Parameters
Mark wrote:
Hmm, ok, but the networks file is stock, set up by the debian install. I
have upgraded the kernel from 2.0.38 to 2.2.15 - would this be the route
of the problem?
:) Yup.
If I am not entirely mistaken, the 2.2.x kernel doesn't need the route
entry as it sets routes automatically.
BTW, somebody mentioned problems with disk performance under 2.2.15 and that
I should stay with 2.2.14.
I am interested in getting LVM working on my system and the only 2.2.x
system that will be patched will be 2.2.15+.
Does anybody know if this person was using the wrong orifice to communicate?
On 12 Jun 2000, Jason Quigley wrote:
BTW, somebody mentioned problems with disk performance under 2.2.15 and that
I should stay with 2.2.14.
I am interested in getting LVM working on my system and the only 2.2.x
system that will be patched will be 2.2.15+.
Does anybody know if this person
John wrote:
on 05 Jan 100, Howard Mann wrote...
2. For some time now when booting, I get the message
'SIOCADDRT - invalid argument'. It appears to cause
no problem - nevertheless, I'd like to understand exactly
what is referred to and make any correction needed
John wrote:
I have only just seen your message. The error is in the email program
made available to me by my ISP when I signed on some 20 months ago.
I had noted the problem with incoming mail, but did not think it would
affect outgoing mail onto other machines. If I've caused any
: debian-user@lists.debian.org
Precedence: list
Resent-sender: [EMAIL PROTECTED]
To: debian-user@lists.debian.org
From: John [EMAIL PROTECTED]
Subject: Vera and SIOCADDRT - separate subjects
Date: Wed, 5 Jan 100 20:23:07 GMT
^^^
I use sendmail as SMTP transport
: Vera and SIOCADDRT - separate subjects
Date: Wed, 5 Jan 100 20:23:07 GMT
^^^
I use sendmail as SMTP transport, procmail for internal distribution, and
exmh as the MUA.
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight
John [EMAIL PROTECTED] writes:
1. I found and installed a program, Vera 1.4a-1, which is
stated to list acronyms. There was no problem with
dselect and 'dpkg -l' shows it as installed, however, I
am neither able to locate any file of that name nor to
access the list. Anyone
Precedence: list
Resent-sender: [EMAIL PROTECTED]
To: debian-user@lists.debian.org
From: John [EMAIL PROTECTED]
Subject: Vera and SIOCADDRT - separate subjects
Date: Wed, 5 Jan 100 20:23:07 GMT
^^^
Cheers,
--
Email: [EMAIL PROTECTED] Tel: +44 1908 653 739
on 05 Jan 100, Howard Mann wrote...
2. For some time now when booting, I get the message
'SIOCADDRT - invalid argument'. It appears to cause
no problem - nevertheless, I'd like to understand exactly
what is referred to and make any correction needed.
So far I've found
]
To: debian-user@lists.debian.org
From: John [EMAIL PROTECTED]
Subject: Vera and SIOCADDRT - separate subjects
Date: Wed, 5 Jan 100 20:23:07 GMT
^^^
I use sendmail as SMTP transport, procmail for internal distribution, and
exmh as the MUA.
--
Oliver Elphick
now when booting, I get the message
'SIOCADDRT - invalid argument'. It appears to cause
no problem - nevertheless, I'd like to understand exactly
what is referred to and make any correction needed.
So far I've found no reference to meaning - there have
been postings recently
2. For some time now when booting, I get the message
'SIOCADDRT - invalid argument'. It appears to cause
no problem - nevertheless, I'd like to understand exactly
what is referred to and make any correction needed.
So far I've found no reference to meaning - there have
I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and
when I use the command route, for example route add -net 127.0.0.0 I get
the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and
it works fine, even when I get that message. The configuration of the
Kernel is OK
of the file gives the proper information.
Sebastian Canagaratna
Department of Chemistry
Ohio NOrthern University
Ada, OH 45810.
I use Debian 2.1 and I have changed my Kernel 2.0.36 to 2.2.4 and
when I use the command route, for example route add -net 127.0.0.0 I get
the message SIOCADDRT
route add -host 127.0.0.1 lo
is added automatically by kernel. You don't need to do it again. If you want to
overwrite it with some other options - use it with full syntax.
goto /usr/src/linux/Documentation
On Wed, Dec 29, 1999 at 03:34:29PM -0500, Sebastian Canagaratna wrote:
Try from the
I use the command route, for example route add -net 127.0.0.0 I get
danito the message SIOCADDRT: Invalid argument. I use an ethernet SMC ultra and
danito it works fine, even when I get that message. The configuration of the
danito Kernel is OK. I would like to know what is going on.
danito
danito
I had the same problem upgrading from kernel 2.0.x to 2.2.13:
SIOCADDRT: Invalid argument
I solved the SIOCADDRT error message updating the
/etc/init.d/network script. Just to be safe I installed also the
netbase_3.12-2 package for Slink
(http://www.debian.org/~rcw/2.2/warnings.html).
BTW, just
Yep. Looks like the 2.2.x series is smart enought not to
need them. Course, I still include them for completion's
sake.
Bryan
On 20-Oct-99 Colin Marquardt wrote:
* Charles Lewis [EMAIL PROTECTED] writes:
The way we solved the SIOCADDRT problem (in potato) was to just comment out
Charles Lewis ([EMAIL PROTECTED]) wrote:
The way we solved the SIOCADDRT problem (in potato) was to just comment out
the route add lines. Apparently they are not needed. Although why they were
needed in slink and not potato I don't know.
It's a kernel issue. Linux 2.2.x automatically adds
didn't need/want. I ended up
commenting everything out. Is there any reason not to delete the file?
Richard Weil
Hans Gubitz wrote:
On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
route add
) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
route add -net 127.0.0.0
to:
route add -net 127.0.0.0 netmask 255.255.255.0 lo
I had the same problem (2.0.36-2.2.12) in my /etc/init.d/network:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0 netmask 255.255.255.0
The way we solved the SIOCADDRT problem (in potato) was to just comment out
the route add lines. Apparently they are not needed. Although why they were
needed in slink and not potato I don't know.
===
Charles Lewis, Director of Administrative Computing
* Charles Lewis [EMAIL PROTECTED] writes:
The way we solved the SIOCADDRT problem (in potato) was to just comment out
the route add lines. Apparently they are not needed. Although why they were
needed in slink and not potato I don't know.
--^^^-^^--
--kernel
approach, but
it works for me.
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
file has a line to add a route for local network traffic through
the loopback interface. As of Kernel 2.2.0, you need to have
a netmask on that line. Debian Slink is designed for 2.0.x
approach, but
it works for me.
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
file has a line to add a route for local network traffic through
the loopback interface. As of Kernel 2.2.0, you need to have
a netmask on that line. Debian Slink is designed for 2.0.x
On Mon, Oct 18, 1999 at 09:31:54PM -0400, Bryan Scaringe wrote:
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
route add -net 127.0.0.0
to:
route add -net 127.0.0.0 netmask 255.255.255.0 lo
I had the same problem (2.0.36-2.2.12) in my /etc/init.d/network
:31:54PM -0400, Bryan Scaringe wrote:
2) As for SIOCADDRT: your /etc/init.d/network (or is it networks)
route add -net 127.0.0.0
to:
route add -net 127.0.0.0 netmask 255.255.255.0 lo
I had the same problem (2.0.36-2.2.12) in my /etc/init.d/network:
#! /bin/sh
ifconfig
El Thu, Sep 23, 1999 at 10:01:27AM +0200, Francisco José Avila Bermejo dijo:
Jon Noble wrote:
Desde entonces me aparece en los mensajes de arranque, después del fsck
esto:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT
Hue-Bond wrote:
El jueves 23 de septiembre de 1999 a la(s) 10:01:27 +0200, Francisco José
Avila Bermejo contaba:
Pues si yo comento esa línea del citado fichero, me desaparece un
SIOCADDRT, pero aún me queda el otro. ¿hay algo más que no se?
Es que si tienes tarjeta de LAN
El viernes 24 de septiembre de 1999 a la(s) 23:23:03 +0200, Francisco José
Avila Bermejo contaba:
Es que si tienes tarjeta de LAN, hay dos routes :^)
¿Pero es que el comando 'route' ha caido el desuso con el nuevo kernel?
Sip. Por lo visto el núcleo averigua las rutas
Hola
* [990925 11:43] Francisco José Avila Bermejo ([EMAIL PROTECTED]) decia:
Hue-Bond wrote:
El jueves 23 de septiembre de 1999 a la(s) 10:01:27 +0200, Francisco José
Avila Bermejo contaba:
Pues si yo comento esa línea del citado fichero, me desaparece un
SIOCADDRT, pero aún me
El jueves 23 de septiembre de 1999 a la(s) 10:01:27 +0200, Francisco José Avila
Bermejo contaba:
Pues si yo comento esa línea del citado fichero, me desaparece un
SIOCADDRT, pero aún me queda el otro. ¿hay algo más que no se?
Es que si tienes tarjeta de LAN, hay dos routes
Jon Noble wrote:
Desde entonces me aparece en los mensajes de arranque, después del fsck
esto:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Para evitar ese mensaje tienes que eliminar en el fichero /etc/init.d
On Wed, Sep 15, 1999 at 10:23:02PM +0200, Joaquín García wrote:
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Mi PC tiene AMD K6-2 a 350, 64M, tarjetas: vídeo, sonido, red y modem
Pues si, el problemo parece ser que es por el reconocimiento de la tarjeta de
red, al menos es lo que
KDE y alguna de sus aplicaciones, ¡bien!
He compilado el kernel 2.2.4 para soporte de la tarjeta de sonido etc.
Desde entonces me aparece en los mensajes de arranque, después del fsck
esto:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument
KDE y alguna de sus aplicaciones, ¡bien!
He compilado el kernel 2.2.4 para soporte de la tarjeta de sonido etc.
Desde entonces me aparece en los mensajes de arranque, después del fsck
esto:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Local time...
[...]
El archivo /etc/init.d/network tiene la culpa. Comenta la(s) línea(s)
que lleven el comando route add -net Por lo que tengo entendido,
la serie de kernels 2.2.x añaden automáticamente la ruta.
Por otro
...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Local time...
...
Mi PC tiene AMD K6-2 a 350, 64M, tarjetas: vídeo, sonido, red y modem
interno.
¿Podríais decirme qué es eso de SIOCADDRT: invalid argument? ¿He añadido
algo mal al kernel?
Para evitar ese mensaje
:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Local time...
...
Mi PC tiene AMD K6-2 a 350, 64M, tarjetas: vídeo, sonido, red y modem
interno.
¿Podríais decirme qué es eso de SIOCADDRT: invalid argument? ¿He añadido
algo
:
...
Mounting local file system...
not mounted anything
SIOCADDRT: invalid argument
SIOCADDRT: invalid argument.
Local time...
...
¿Podríais decirme qué es eso de SIOCADDRT: invalid argument? ¿He añadido
algo mal al kernel?
puede que sea que en el arranque se invoque al comando route, que con
Kai == Kai Rascher [EMAIL PROTECTED] writes:
Kai Hi experts, I installed kernel 2.2.11 (Debian 2.1) and
Kai everything seem all right. But there are two messages
Kai ´SIOCADDRT invalid argument´ during boot process I don´t
Kai understand. I´m pretty sure that this messages have
Hi again,
When I try to restart /etc/init.d/network or set the route from the
cli, I get an SIOCADDRT: Invalid argument error. I searched through
the archives, and the only thing I found was a reference to 2.2.*
kernels and upgrade netbase to the one in potato.
The kernel on this machine
Hi,
Booting Slink with Linux 2.2.5 kernel I get the message
SIOCADDRT: Invalid argument
after mounting the file systems. What does this mean? Looks like an error,
doesn't it?
Armin
:
Hi,
Booting Slink with Linux 2.2.5 kernel I get the message
SIOCADDRT: Invalid argument
after mounting the file systems. What does this mean? Looks like an error,
doesn't it?
Armin
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
. From
there, you find the April 1999 debian-user, and search for SIOCADDRT (using
alt-f in netscape or / in lynx). You'll find it in the third page of
debian-user for this month. You can find two specific fixes on that page,
mine (http://www.debian.org/Lists-Archives/debian-user-9904/msg01303.html
Greetings,
I'm cleaning up the boot messages of a system we're moving to
another location, and I ran into a funny message. When the system
boots everything looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice, and then it moves
of a system we're moving to
another location, and I ran into a funny message. When the system
boots everything looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice, and then it moves on. I've looked at the
/etc/init.d/mountall.sh script
we're moving to
another location, and I ran into a funny message. When the system
boots everything looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice, and then it moves on. I've looked at the
/etc/init.d/mountall.sh script
everything looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice, and then it moves on. I've looked at the
/etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems
and I still don't have a clue. What do I need
looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice, and then it moves on. I've looked at the
/etc/init.d/mountall.sh script, /etc/fstab, and /proc/filesystems
and I still don't have a clue. What do I need to change
:
Greetings,
I'm cleaning up the boot messages of a system we're moving to
another location, and I ran into a funny message. When the system
boots everything looks OK until It mounts the local filesystems. I
get this weird error,
SIOCADDRT: Invalid argument
twice
On Sat, 17 Apr 1999, Chad A. Adlawan wrote:
hi Vaidhy,
i also got the same error as u guys did, that is, i got it after i
upgraded from 2.0.36 to 2.2.4. do u think that same fix'll still work for
me ? i dont feel too comfortable removing some lines from my init.d/network
because though i
Subject: Help for error: SIOCADDRT: Invalid argument.
Date: Sat, Apr 10, 1999 at 07:58:40PM +0200
In reply to:Norbert Nemec
Quoting Norbert Nemec([EMAIL PROTECTED]):
Hi out there,
I've been trying to compile kernel 2.2.1 for several machines in our small
network. Now, some
James Mastros wrote:
On Sat, Apr 10, 1999 at 07:58:40PM +0200, Norbert Nemec wrote:
I've been trying to compile kernel 2.2.1 for several machines in our small
network. Now, some computers bring the message above during bootup at
the command:
route add -net 127.0.0.0
(in
Hi out there,
I've been trying to compile kernel 2.2.1 for several machines in our small
network. Now, some computers bring the message above during bootup at
the command:
route add -net 127.0.0.0
(in /etc/init.d/network)
After that, the IP-network is not working fully. (Parts, like nfs
On Sat, Apr 10, 1999 at 07:58:40PM +0200, Norbert Nemec wrote:
I've been trying to compile kernel 2.2.1 for several machines in our small
network. Now, some computers bring the message above during bootup at
the command:
route add -net 127.0.0.0
(in /etc/init.d/network)
The simple fix
On Thu, 18 Mar 1999, Asokan P wrote:
My machine has suddenly started displaying this message
SIOCADDRT - invalid argument.
You would have noticed this message after putting the kernel 2.2.X.In
these kernels the route add command is not needed.So remove this line from
/etc/networks
My machine has suddenly started displaying this message
SIOCADDRT - invalid argument.
The network card is dtected and while booting up it shows up correctly
I traced it to the two route commands in /etc/inet.d/network
They are correct - as per the man, ifconfig looks alright
ping 192.168.3.208
1 - 100 of 118 matches
Mail list logo
