SIOCADDRT: Invalid argument

[Javier Prieto]

Whenever I try to add a route ("route add -net 127.0.0.1"), I get that error
message: "SIOCADDRT: Invalid argument". Anyway the card seems to work
perfectly.

My NIC is a Kingston EtherX KNE100TX using DE4x5 driver (I should use tulip
driver, but it doesn't work).

Any help?

Javier Prieto
Optima Technologies, Sevilla (Spain)
pri...@optimat.com

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[Brian McCauley]

Javier Prieto <pri...@optimat.com> writes:

> Whenever I try to add a route ("route add -net 127.0.0.1"), I get that error
> message: "SIOCADDRT: Invalid argument".

Yes well that command is nonsensical. "route add -net" attempts to
add a route to a network. By a network we mean a range of 32-bit IP
addresses defined by having a given prefix (which must of course
thereforre be less than 32 bits long). One thing we can be sure about
is that the network prefix can't have a 1 in the least significant bit.

Try:
route add -host 127.0.0.1

Or the preferred command which is:
route add -net 127.0.0.0

> Anyway the card seems to work perfectly.

What card? We're talking about the loopback device here. The
loopback device is a virtual device - there's no hardware.

--
\\ ( ) No male bovine | Email: B.A.Mc...@bham.ac.uk
. _\\__[oo faeces from | Phones: +44 121 471 3789 (home)
.__/ \\ /\@ /~) /~[ /\/[ | +44 121 627 2173 (voice) 2175 (fax)
. l___\\ /~~) /~~[ / [ | PGP-fp: D7 03 2A 4B D8 3A 05 37...
# ll l\\ ~~~~ ~ ~ ~ ~ | http://www.wcl.bham.ac.uk/~bam/
###LL LL\\ (Brian McCauley) |

[Javier Prieto]

In article <u9vhewm...@wcl-l.bham.ac.uk>,
Brian McCauley <B.A.Mc...@bham.ac.uk> wrote:

> > Whenever I try to add a route ("route add -net 127.0.0.1"), I get that error
> > message: "SIOCADDRT: Invalid argument".

> route add -net 127.0.0.0

I've tried that command and I get the same message.

> > Anyway the card seems to work perfectly.
> What card? We're talking about the loopback device here. The
> loopback device is a virtual device - there's no hardware.

Anyway "route add -net 192.168.200.0" gives me the same error.

It seems that any attempt to add a route displays that message.

I'd like to know who in the kernel is giving me that message... I thought it
was the NIC, but even "route add -net 127.0.0.0 lo" displays it.

[inetport.com]

Javier Prieto (pri...@optimat.com) wrote:
: In article <u9vhewm...@wcl-l.bham.ac.uk>,
: Brian McCauley <B.A.Mc...@bham.ac.uk> wrote:

: > > Whenever I try to add a route ("route add -net 127.0.0.1"), I get that error
: > > message: "SIOCADDRT: Invalid argument".
: > route add -net 127.0.0.0

: I've tried that command and I get the same message.

Kernel 2.2.x ? Try

/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

and read the linux/Documentation/Changes file.

--
Clifford Kite <kite@inet% port.com> Not a guru. (tm)
/* Microsoft is a great marketing organization.
* It _has_ to be */

[Gregory Kreymer]

>: > > Whenever I try to add a route ("route add -net 127.0.0.1"), I get
that error
>: > > message: "SIOCADDRT: Invalid argument".
>: > route add -net 127.0.0.0

I'm using RH 5.2 and didn't even have to add a route and I have the
"SIOCADDRT: Invalid argument" come up during a boot. I remember getting it
even after a fresh install using RH's menu installation. I have a hunch
that it's a NIC problem - I have a 3905b.... Do you hapen to also have the
same card?

Greg K.

[Villy Kruse]

In article <7ffjpl$2b8$1...@list.umaryland.edu>,
Gregory Kreymer <gkre...@umaryland.edu> wrote:

>I'm using RH 5.2 and didn't even have to add a route and I have the
>"SIOCADDRT: Invalid argument" come up during a boot. I remember getting it
>even after a fresh install using RH's menu installation. I have a hunch
>that it's a NIC problem - I have a 3905b.... Do you hapen to also have the
>same card?

This usually happens when you don't want to set up a default route
during install and leave the field blank. This will result in the
system trying to add a default route to 0.0.0.0 through eth0 and this
gives the above message.

To fix remove the lines with GATEWAYDEV and GATEWAY from
/etc/sysconfig/network.

::::::::::::::
/etc/sysconfig/network
::::::::::::::
NETWORKING=yes
FORWARD_IPV4=no
HOSTNAME=xx.xx.xx.xxxxxxxx.xxx
GATEWAYDEV=eth1 <<<<< remove these
GATEWAY=0.0.0.0 <<<<< remove these

Villy

[Gary S. Mackay]

I'm using an SMC EtherEZ on my Redhat 5.2 and I have the same message at
boot time also. Wondered were that was coming from ??

Gregory Kreymer wrote:
>
> >: > > Whenever I try to add a route ("route add -net 127.0.0.1"), I get
> that error
> >: > > message: "SIOCADDRT: Invalid argument".
> >: > route add -net 127.0.0.0
>

> I'm using RH 5.2 and didn't even have to add a route and I have the
> "SIOCADDRT: Invalid argument" come up during a boot. I remember getting it
> even after a fresh install using RH's menu installation. I have a hunch
> that it's a NIC problem - I have a 3905b.... Do you hapen to also have the
> same card?
>

> Greg K.

--
Edison Information Technologies
P.O. Box 554
Milan, OH 44846-0554
419.499.7040
Ga...@EdisonInfo.com
--

[Javier Prieto]

In article <7ffgre$2...@inetport.com>,

kite@NoSpam.% inetport.com (Clifford Kite) wrote:

> Kernel 2.2.x ? Try
> /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
> and read the linux/Documentation/Changes file.

Thanks for both advices, now everything works properly :)

[Kelvin Tsang]

I recently bought thirty 3c905b for my company,
and found that my LAN becomes unstable with
them, I still not sure if its caused by the lan driver
or the nic itself. I have three servers on the LAN,
HP9000 HP-UX 10.20, NT Server, and NetWare 3.12
with Win95, Win311, Linux workstations. The
'unstable' crashes my Novell Server quite a lot,
twice a week !

Kelvin