Date: Mon, 8 Feb 1999 16:12:06 +1000 From: Stanley.Hopcroft@ipaustralia.gov.au To: questions@FreeBSD.ORG Cc: Paul.Quirk@ipaustralia.gov.au Subject: Wierd routing problem Message-ID: <4A256712.00225B98.00@noteshub01.aipo.gov.au>
next in thread | raw e-mail | index | archive | help
Dear Ladies and Gentlemen, I am writing to ask your opinions about a wierd routing problem. The situation was 1 a server was moved from one location to another and the static route to that server updated in the networks default router (a Cisco with no known vices in this regard) 2 the relocated server was, after some 30 minutes in the new location, restored to its former connection because the the move revealed that futher work was necessary to relocate it 3 Thereafter, vital boxes such as the DNS (FreeBSD-2.2.8-STABLE) could not contact the moved server. Ping from these boxes reported "sendto: no route to host". There were . about 3 hosts - all of which are usually in constant communication with the relocated server - that could no longer contact the server. The OS range from FreeBSD 2.2.2-STABLE to 2.2.8-STABLE. . no obvious problems revealed by netstat -rn. This display showed - the same default gateway as before the move, with the G, U, S and no M flags - no host routes to the server I expected that after the relocation the default router would redirect the hosts to use a new router to access the server. The problem was finally worked around by rebooting the three servers. Perhaps I should have tried netstat -flush from the console ? Thank you, Yours sincerely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A256712.00225B98.00>