From owner-freebsd-questions Sun Sep 30 21: 8:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.netizen.co.za (situs.netizen.co.za [209.61.189.116]) by hub.freebsd.org (Postfix) with ESMTP id E449537B40A for ; Sun, 30 Sep 2001 21:08:33 -0700 (PDT) Received: from localhost.netizen.co.za ([127.0.0.1] helo=localhost) by mail.netizen.co.za with smtp (Exim 3.30 #1) id 15nuNk-000C4n-00 for questions@freebsd.org; Sun, 30 Sep 2001 23:08:40 -0500 From: To: Reply-To: Subject: DHCP lease problems X-Originating-Ip: [4.34.188.214] X-Mailer: NOCC v0.9.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: Date: Sun, 30 Sep 2001 23:08:40 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all After having the firmware upgrade on my D-Link wireless access point/firewall/DSL router go awry yesterday, I have rapidly turned my FreeBSD print/mail server into a firewall for my DSL connection, using ipfw and natd. However, I am experiencing a nasty problem, which I only seem to be able to fix (so far) by power cycling my DSL modem and rebooting the FreeBSD box. The problem seems to be that if the machine is idle for a while (not very long), it loses the DHCP lease and thus also the default route. Once this happens, I cannot get it to renew unless I go through the process above. IIRC, Verizon's DHCP issues leases with a lifetime of 24 hours, so the lease is not expiring on their side (I think that is part of the problem - the only way to get their end to respnd to DHCP requests again is to power cycle their modem). Something else I have tried is rebooting - but when the FreeBSD box comes up it fails to get a lease. It does try to reuse the old values, but cannot ping the remote gateway. Possibly complicating matters is the fact that I am running a DHCP server (for 192.168/16) on my internal interface (rl0), but I don't think that is the problem. The DHCP service on the inside seems to work fine, and should not be interfering with anything on the outside interface (dc0), AFAIK. The logs don't show much - when the problem starts, natd starts complaining about being unable to send packets back as there is no route. Other than that, I don't see anything that reveals the cause. The dhclient.conf file is very simple: interface "dc0" { request subnet-mask, broadcast-address, routers, domain-name, domain-name-servers, host-name; } The relevant lines from rc.conf are: ifconfig_dc0="DHCP" natd_interface="dc0" natd_flags="-u -m -dynamic -log_denied" Any help will be appreciated! TIA gram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message