Hi DU Admins
Thanks to James Sainsbury, Mike Matthews, Arnaud Valeix and
paulo_at_gateway.dexel.co.za.
The question conerned warning messages which began appearing on
the console during bootup after we switched to static routing.
The original question is included at the end of the summary.
We're not running routed or gated. Some suggested that this might
be the cause of the messages.
James correctly diagnosed the problem. The routing tables aren't
flushed on entering other run levels. The warning messages are
just saying that the tables already exist. In other words they're
nothing to worry about.
James also asked if we needed explicit routes other than the default
route? The extra routes are for other small networks that the default
router isn't supposed to know about. However I tried some experiments
and those networks can be reached without the extra entries in the
routing tables. It looks like I don't need them after all.
Another suggestion from James was that if the warning messages are
a problem a "route flush -inet" command could be added to
/sbin/init.d/route under the 'stop' selector
Three of the replies asked if we were running routed or gated
but we're not so that is not the problem.
Thanks all
Ian
Original question:
We were forced recently to switch to static routing tables.
Now when I boot my DEC 3000-M400 running OSF1 3.2 I get these
messages (from /sbin/init.d/route start) on the console :
add net default: gateway 130.102.120.30
writing to routing socket: File exists
add net 130.102.120.0: gateway 130.102.120.147: ioctl returns 17
File exists
add net 130.102.136.0: gateway 130.102.120.50: ioctl returns 17
File exists
add net 130.102.172.0: gateway 130.102.120.133: ioctl returns 17
File exists
(BTW I discovered that "ioctl returns 17" just means "File exists".)
/etc/routes looks like:
default 130.102.120.30 -hopcount 1
-net 130.102.120.0 130.102.120.147
-net 130.102.136.0 130.102.120.50 -hopcount 1
-net 130.102.172.0 130.102.120.133 -hopcount 1
netstat -rn shows:
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.255.0
Route Tree for Protocol Family 2:
default 130.102.120.30 UG 0 82 ln0
127.0.0.1 127.0.0.1 UH 4 6384 lo0
130.102.120 130.102.120.147 U 22 20228 ln0
130.102.136 130.102.120.50 UG 0 0 ln0
130.102.172 130.102.120.133 UG 0 0 ln0
So everything looks okay and the network seems to be working perfectly.
Can anyone tell me what those error messages are about? Should I be
worried by them?
Thanks
Ian
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/ Ian Mortimer _/
_/ Department of Physics Tel : +61 7 3365 3416 _/
_/ University of Queensland Email: mortimer_at_physics.uq.edu.au _/
_/ St. Lucia, Brisbane Fax : +61 7 3365 1242 _/
_/ Queensland, Australia. 4072. _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Disclaimer: Any opinions expressed are my own and do not represent those
of the University of Queensland or the Department of Physics.
Received on Fri Feb 14 1997 - 01:53:23 NZDT