Date: Tue, 21 Nov 2006 10:27:56 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: UNIX - Questions <freebsd-questions@freebsd.org> Subject: Re: Totally stumped - very long post Message-ID: <556BBD73A562FFF4DCEC1E21@utd59514.utdallas.edu> In-Reply-To: <45632057.2080706@joeholden.co.uk> References: <BFE16982B9EB3D6BADF911A8@paul-schmehls-powerbook59.local> <B0018098-1130-4D89-9774-1B241737D6FD@dpcsys.com> <2A97A175E0A3D7A039D1AA98@paul-schmehls-powerbook59.local> <456297CE.9030103@joeholden.co.uk> <3974ECF15478CC1AAEE19789@utd59514.utdallas.edu> <45632057.2080706@joeholden.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========52477ECA6C82E750CDF9========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, November 21, 2006 15:50:47 +0000 Joe Holden=20 <joe@joeholden.co.uk> wrote: >>> >> Care to give me a bigger hint? I'm not a routing guru. >> >> I tried this with no luck: >> route delete 66 >> route: writing to routing socket: No such process >> delete host 66: not in table >> Thanks, Joe. I'll keep this in mind for next time. I ended up logging in=20 through the console (using DRAC) and flushing the routing table. Then I=20 restarted networking, and everything looked normal, but I couldn't access=20 remotely, so I rebooted the box. Now everything is normal again. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========52477ECA6C82E750CDF9==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?556BBD73A562FFF4DCEC1E21>