root <[EMAIL PROTECTED]> wrote: > > SIOCADDRT: Invalid argument > SIOCADDRT: Invalid argument > SIOCADDRT: Invalid argument > SIOCADDRT: File exists > SIOCADDRT: Invalid argument SIOCADDRT is the "Socket I/O Control ADD RouTe" command to the kernel. It is failing for some reason. These messages are almost useless without knowing the "route" command that was generated by the script. You might try to find out what route commands the network script is trying to run. > I recomplied the kernel and included in all the network options. The 2.1 kernels handle routes slightly differently. In particular, there is no longer any need to set a route on a particular interface. Whereas in 2.0, you would first need to "ifconfig" the interface, then "route add -net" the same address in order to route packets through it, in 2.1, the second "route" step is now performed internally by the kernel, and generates an error like the above, if you attempt to do it yourself. So, possibly some of the messages above are harmless errors, but my guess is that something more insidious is happening, such as that your ethernet interfaces aren't even configuring up at all. Does "ifconfig" show you anything? -- [EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut sometimes known as David DeSimone || butter quite like unrequited love." http://www.dallas.net/~fox/ || -- Charlie Brown --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For daily digest info, email [EMAIL PROTECTED]
