the 3step i got the following 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 he
> 2step
> ' I changed the file /etc/network/interfaces'
> 3step 'ifup --all'
>
> after the 3step i got the following warning:
> ''SIOCADDRT: Invalid argument''
>
> Now the network does not work.
> Could you please someone h
the 3step i got the following 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 he
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 kern
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 bootu
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
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 re
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."
ito >when 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 g
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 co
sage 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. I would like to know what is going on.
>
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
>
>
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
>>>>> "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
Ka
, Armin Wegner wrote:
> 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
>
>
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
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 o
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
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
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
0.0.1
> route add -net 127.0.0.0
> I get
> SIOCADDRT: Invalid argument
>
> When I type
> IPADDR=192.168.0.4
> NETMASK=255.255.255.0
> NETWORK=192.168.0.0
> BROADCAST=192.168.0.255
> GATEWAY=192.168.0.4
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROA
On 08-Mar-99 Oz Dror wrote:
> When I type
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
> I get
> SIOCADDRT: Invalid argument
>
2.2.x (and later 2.1.x) kernels do not need route statements. Unless you have
to set a gateway that is non-obvious.
When I type
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
I get
SIOCADDRT: Invalid argument
When I type
IPADDR=192.168.0.4
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
GATEWAY=192.168.0.4
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net
*- On 9 Feb, Ed Cogburn wrote about "[SOLVED] Re: Kernel 2.2.1: SIOCADDRT:
Invalid argument ?"
> "Ralf G. R. Bergs" wrote:
>>
>> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>>
>> > route add -net 127.0.0.0
>> >
>&
"Ralf G. R. Bergs" wrote:
>
> On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
>
> > route add -net 127.0.0.0
> >
> > Its the route command thats generating the "SIOCADDRT: Invalid
> >argument". I'm up to date with potat
On Tue, 09 Feb 1999 15:02:36 -0500, Ed Cogburn wrote:
> route add -net 127.0.0.0
>
> Its the route command thats generating the "SIOCADDRT: Invalid
>argument". I'm up to date with potato, (I got the kernel deb from
>there) so what could this be?
The
*- On 9 Feb, Ed Cogburn wrote about "Kernel 2.2.1: SIOCADDRT: Invalid
argument ?"
>
>
> After upgrading to the 2.2.1 kernel, I now get an error during
> bootup. I narrowed it to /etc/init.d/network:
>
> ifconfig lo 127.0.0.1
> route add -n
After upgrading to the 2.2.1 kernel, I now get an error during
bootup. I narrowed it to /etc/init.d/network:
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
Its the route command thats generating the "SIOCADDRT: Invalid
argument". I'm up to date
hi
i keep on getting the message "SIOCADDRT: Invalid argument" on bootup since
i started using 2.1.x. i traced the message to this line in
/etc/init.d/network:
route add -net 127.0.0.0
now, will commenting out this line have any untoward effects? if so, can i
upgrade to a later
28 matches
Mail list logo
