From owner-freebsd-questions Sat Aug 31 14:25:44 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA13784 for questions-outgoing; Sat, 31 Aug 1996 14:25:44 -0700 (PDT) Received: from river.streamwave.com (windchime-03.synapse.net [199.84.52.251]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13747 for ; Sat, 31 Aug 1996 14:25:38 -0700 (PDT) Received: from brook.streamwave (brook.streamwave.com [206.123.23.2]) by river.streamwave.com (8.6.12/8.6.12) with SMTP id RAA07909 for ; Sat, 31 Aug 1996 17:31:31 -0400 Date: Sat, 31 Aug 1996 17:31:31 -0400 Message-Id: <199608312131.RAA07909@river.streamwave.com> X-Sender: yves@pop.streamwave.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: questions@freebsd.org From: Yves Dagenais Subject: routing trouble with v.2.1.0 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've got a server running FreeBSD 2.1.0. The problem is when we connect through the dial-in lines and hangup, sometimes that users IP stays stuck in the routing table and never expires. This becomes a problem when you try to log back on using that IP since the entry is already there, the server doesn't seem to reassign it. Therefore you don't get any routing... The only way I can fix that is once that user is offline, I must manually delete his route. Does anyone have any ideas on what is causing the IP's to stay stuck? Is it my ppp software on ther server? Is it the name daemon control interface? Any suggestions or ideas would be appreciated. Thanks in advance, Yves Dagenais yves@streamwave.com