From owner-freebsd-questions Thu Jun 20 11:48:42 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by hub.freebsd.org (Postfix) with ESMTP id 8D5D737B403 for ; Thu, 20 Jun 2002 11:48:35 -0700 (PDT) Received: from TICK ([24.118.217.79]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020620184835.MIBA1024.sccrmhc01.attbi.com@TICK> for ; Thu, 20 Jun 2002 18:48:35 +0000 Message-ID: <006b01c2188a$55b5da90$0b02010a@TICK> From: "Ted Stockwell" To: Subject: dhcp client and AT&T broadband Date: Thu, 20 Jun 2002 13:43:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 I had a problem recently and thought others may be interested in the fix. My FreeBSD box using the ISC dhcp client stopped working with AT&T Broadband. It turns out that AT&T made a change to their infrastructure so that there are now so many hops that the TTL on the DHCP client messages expires before reaching the server. The client set the TTL to 16, and it looks like there are at least 18 hops from my spot on the network. (most of their customers do not have a problem because the Microsoft client uses at TTL of 128). For anyone who is interested, a patch and some notes are available at: http://www.visi.com/~tstockwell/dhcp_ttl.html -- Ted Stockwell, tstockwell@mesabi-tech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message