Re: strange msg in bootup
On Sat, 22 May, Graham Aston wrote: On Friday 21 May, Dan Willard wrote: The route command now requires a netmask. Just add one in to both of the route commands and it should go away. if you read the 2.2 docs in /usr/src/linux/Changes (or whatever it's called) then you should find a bit that tells you that routes for local interfaces are added automatically by the kernel. comment out the route... lines in /etc/init.d/network and the problem should go away. Thanks, the problem is solved now. The correct solution seems to be commenting out the appropriate lines in the file /etc/init.d/network
Re: strange msg in bootup
On Friday 21 May, Dan Willard wrote:
The route command now requires a netmask. Just add one in to both of the
route commands and it should go away.
if you read the 2.2 docs in /usr/src/linux/Changes (or whatever it's
called) then you should find a bit that tells you that routes for local
interfaces are added automatically by the kernel. comment out the
route... lines in /etc/init.d/network and the problem should go away.
Following is a listing of my /etc/rcS.d/S40network file, hope it will
help:
unusually, I was right - they're uncommented - stick a # infront of
the two route... lines (S40network is just a link to the
init.d/network file by the way).
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=144.122.246.42
NETMASK=255.255.252.0
NETWORK=144.122.244.0
BROADCAST=144.122.247.255
GATEWAY=144.122.246.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
--
Graham
Re: strange msg in bootup
Subject: strange msg in bootup
Date: Sat, May 22, 1999 at 12:46:47AM +0300
In reply to:Ali Onur UYAR
Quoting Ali Onur UYAR([EMAIL PROTECTED]):
I have been using Linux for a year. I started with hamm and now I am using
slink.
I was running kernel 2.0.36 until last week.
Then decided it was the time to tackle sound config.
Then I realized it might had been a bit easier if I switched to 2.2 series
kernels.
Read a great deal of docs, installed the kernel 2.2.9 using kernel-package
and
it worked!
Then I configured the sound card, configuring the Soundblaster Vibra16pnp
troubled
me a great deal, but everything was fine in the end.
Now the problem is that I have recognized a strange message during boot up,
and
I am not
exactly sure if it is related to this final upgrade.
Just after the local file systems are mounted, a message is displayed on the
console:
SIOCADDRT: Invalid argument
SIOCADDRT: Invalid argument
Hunted around in /etc/rcS.d for some time and discovered that the message was
displayed while
the file /etc/rcS.d/S40network was being executed.
Placing some echo commands here and there I tracked down the problem to the
invocations of
the route command.
Doesn't seem to be a serious problem, as everything seems to be working, but
what may be the
cause for such an error msg, can anybody help. I do not have any experience
with
routing issues.
Following is a listing of my /etc/rcS.d/S40network file, hope it will help:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=144.122.246.42
NETMASK=255.255.252.0
NETWORK=144.122.244.0
BROADCAST=144.122.247.255
GATEWAY=144.122.246.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
Very good troubleshooting! It is a 'feature' of the 2.2.x kernels.
The kennel now does the routing itself so the route command in the
network script isn't needed.
Here is how I changed my /etc/init.d/network script to handle it
if [ $(uname -r |grep 2.0) ]; then
/sbin/route add -net 127.0.0.0
ifconfig ppp ${IPADDR} netmask ${NETMASK} broadcast
${BROADCAST}
/sbin/route add -net ${NETWORK} netmask ${NETMASK}
else
/sbin/ifconfig lo 127.0.0.1
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
# /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
fi
Hope This Helps
Wayne
--
There are two ways to write error-free programs. Only the third one works.
___
Wayne T. Topa [EMAIL PROTECTED]
strange msg in bootup
I have been using Linux for a year. I started with hamm and now I am using
slink.
I was running kernel 2.0.36 until last week.
Then decided it was the time to tackle sound config.
Then I realized it might had been a bit easier if I switched to 2.2 series
kernels.
Read a great deal of docs, installed the kernel 2.2.9 using kernel-package and
it worked!
Then I configured the sound card, configuring the Soundblaster Vibra16pnp
troubled
me a great deal, but everything was fine in the end.
Now the problem is that I have recognized a strange message during boot up, and
I am not
exactly sure if it is related to this final upgrade.
Just after the local file systems are mounted, a message is displayed on the
console:
SIOCADDRT: Invalid argument
SIOCADDRT: Invalid argument
Hunted around in /etc/rcS.d for some time and discovered that the message was
displayed while
the file /etc/rcS.d/S40network was being executed.
Placing some echo commands here and there I tracked down the problem to the
invocations of
the route command.
Doesn't seem to be a serious problem, as everything seems to be working, but
what may be the
cause for such an error msg, can anybody help. I do not have any experience with
routing issues.
Following is a listing of my /etc/rcS.d/S40network file, hope it will help:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=144.122.246.42
NETMASK=255.255.252.0
NETWORK=144.122.244.0
BROADCAST=144.122.247.255
GATEWAY=144.122.246.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
RE: strange msg in bootup
The route command now requires a netmask. Just add one in to both of the
route commands and it should go away.
--Dano
-Original Message-
From: Ali Onur UYAR [SMTP:[EMAIL PROTECTED]
Sent: Friday, May 21, 1999 5:47 PM
To: debian-user@lists.debian.org
Subject: strange msg in bootup
I have been using Linux for a year. I started with hamm and now I am using
slink.
I was running kernel 2.0.36 until last week.
Then decided it was the time to tackle sound config.
Then I realized it might had been a bit easier if I switched to 2.2 series
kernels.
Read a great deal of docs, installed the kernel 2.2.9 using
kernel-package and
it worked!
Then I configured the sound card, configuring the Soundblaster Vibra16pnp
troubled
me a great deal, but everything was fine in the end.
Now the problem is that I have recognized a strange message during boot
up, and
I am not
exactly sure if it is related to this final upgrade.
Just after the local file systems are mounted, a message is displayed on
the
console:
SIOCADDRT: Invalid argument
SIOCADDRT: Invalid argument
Hunted around in /etc/rcS.d for some time and discovered that the message
was
displayed while
the file /etc/rcS.d/S40network was being executed.
Placing some echo commands here and there I tracked down the problem to
the
invocations of
the route command.
Doesn't seem to be a serious problem, as everything seems to be working,
but
what may be the
cause for such an error msg, can anybody help. I do not have any
experience with
routing issues.
Following is a listing of my /etc/rcS.d/S40network file, hope it will
help:
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=144.122.246.42
NETMASK=255.255.252.0
NETWORK=144.122.244.0
BROADCAST=144.122.247.255
GATEWAY=144.122.246.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED]
/dev/null
