[4643] in RedHat Linux List
RE: SIOCADDRT: Invalid arguement error
daemon@ATHENA.MIT.EDU (Aviram Carmi)
Fri Nov 15 19:09:22 1996
Date: Fri, 15 Nov 1996 15:52:55 -0800
To: Steve Jardine <jardine@goodnet.com>
From: Aviram Carmi <avi@otn.com>
Cc: redhat-list@redhat.com, ewt@redhat.com
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
At 14:01 on 11/15/96, Steve Jardine wrote:
> On 15-Nov-96 Aviram Carmi wrote:
> >>Hi all,
> >
> >just finished installing the latest initscript. now the SIOCADDRT: Network
> >unreachable, has changed to Invalid argument error.
> >
>
> The SIOCADDRT surely makes things look like the ethernet card is not being
> recognized. Did you recompile the kernel lately? Does your initscript
> alter which ethernet modules you load?
The thing is that all network related stuff seems to be functioning
properly, apache is happy, I can send mail, ftp, and telnet.
I try to keep up with all the upgrades, I am now upto kernel 2.0.25 and all
the RedHat updates to date. I never had any problems with kernel
compilation, though I always got the SIOCADDRT errors. Initially I did not
notice them since they were issued only for the "real" interface, now that
I've added virtual if, I see a message for each virtual, for the main eth0
and for lo.
I did compile the 3C590 support into the kernel, not as a module. Would
this be a problem???
>
> >I have multiple virtual domains set up with
> >/etc/sysconfig/network-scripts/ifup-eth0:xx scripts.
> >
> >I used to get the SIOCADDRT: Network unreachable for the main eth0 and for
> >each virtual one.
> >
> >Now, after installing the latest ifup script, I am getting an "SIOCADDRT:
> >Invalid arguement" error for each.
> >
> >I am using a 3C590 PCI TP card (vortex chipset?) essentially a stock system
> >(Intel Advanced/EV, P5/133, 32MB EDO, 1.7 IDE no SCSI, 3C590) and a 3.04
> >upgraded to kernel 2.0 and then to 4.0 with all the updates installed.
> >
> >Any ideas???
> >
>
> If you recompiled the kernel, check the configuration again and try the
> compilation again. If not, look for errors in your initscript where it
> could affect module loading. Look at dmesg and see if the ethernet card
> is being recognized.
>
>
> >How do I trace or debug this stuff? It seems that these error messages are
> >only printed to the screen, they are not kept in a file anywhere....
> >
>
> DMESG | more might help.. Dunno for sure though..
The last two lines are:
eth0: vortex_open() InternalConfig 00020012.
eth0: vortex_open() irq 11 media status 8800
I have no idea what these mean....
I get the SIOCADDRT errors just after these messages...
From Erik:
At 13:53 on 11/15/96, Erik Troan wrote:
> On Fri, 15 Nov 1996, Aviram Carmi wrote:
>
> > How do I trace or debug this stuff? It seems that these error messages are
> > only printed to the screen, they are not kept in a file anywhere....
>
> Try running "cd /etc/sysconfig/network-scripts; sh -x ./ifup ifcfg-eth0"
>
OK I tried it (hopfully it does not mess up my configuration...):
the SIOCADDRT error is generated as a result of calling
+ route add default gw 204.176.255.254 eth0
SIOCADDRT: Invalid argument
executing the same command directly from the shell DOES NOT give the error.
Does this mean anything to anybody?
Thanks for your help,
-avi
--
Aviram Carmi +---------------+ tm
| O v e r |
Executive Vice President, Technology | ----------- |
(805) 384-1144 Voice | T h e N e t |
(805) 384-9111 FAX +---------------+
We'll Make You Known Worldwide
PO Box 1499 http://www.otn.com/
Camarillo, CA 93011-1499
(c) Copyright 1996, Over TheNet. All rights reserved.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
