shenkin@cunixf.cc.columbia.edu (Peter S. Shenkin) (06/25/91)
You may recall my query of a few weeks ago: after upgrading to 3.3 from 3.2 (on a 4d25tg), I couldn't access any but the local net. Several kind souls responded with advice to write a network.local file in /etc/init.d containing an "add default..." line, and to create symbolic links to it as described in the file "network" in the same directory. I did this and all was well... until I upgraded to 3.3.2, then 3.3.3 (in a single installation pass) today. When the machine came up, I once again could not access any but the local network, and netstat -r did not show a "default" setting. Adding the default manually, by issuing "/usr/etc/route add default..." as superuser, fixed the problem. But I want this to happen automatically at boot time. So I rebooted as a double check. An immediate "netstat -r" slowly printed a seemingly endless list of addresses, all using the correct default gateway, with flags "UGH", but the net (except for the local net) could not be reached. A little later the same netstat command just showed the localhost, 224, and 128.59 (local net) entries, and no line showed the gateway. Adding a default manually as superuser does add a default line to "netstat -r" output, with the correct gateway and flags "UG", and then the outside world is accessible. What's going on, and how can I get the default line added automatically at boot time? By the way, the network.local file and the symbolic links to it in /etc/rc*.d all seem to be intact. -P. ************************f*u*cn*rd*ths*u*cn*gt*a*gd*jb************************** Peter S. Shenkin, Department of Chemistry, Barnard College, New York, NY 10027 (212)854-1418 shenkin@cunixf.cc.columbia.edu(Internet) shenkin@cunixf(Bitnet) ***"In scenic New York... where the third world is only a subway ride away."***