From owner-freebsd-net@FreeBSD.ORG Fri Sep 2 09:39:06 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 226D116A41F for ; Fri, 2 Sep 2005 09:39:06 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE48143D45 for ; Fri, 2 Sep 2005 09:39:05 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=h311r4z3r) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1EB80N-0005qV-Ub; Fri, 02 Sep 2005 11:38:40 +0200 Date: Fri, 2 Sep 2005 11:39:01 +0200 From: Marcin Jessa To: "Digital Brain" Message-Id: <20050902113901.309a46bc.lists@yazzy.org> In-Reply-To: References: <4316DB17.5000601@freemail.gr> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.8; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.6 (--) Cc: dionch@freemail.gr, freebsd-net@freebsd.org Subject: Re: dhclient and ADSL modem trouble... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 09:39:06 -0000 On Thu, 01 Sep 2005 11:31:20 +0000 "Digital Brain" wrote: > Hi Chris, > > >Linux and freebsd you re trying, running on same hardware (nic) ? > >I'm saying that cause some ISPs lock their "IP-offering" > >with each client's hardware address (which is defined at first use). > > Linux is on my laptop (and works ok), while freebsd is on another machine. > I had thought of that and so I tried the following: > 1. while I had a connection from the laptop with an assigned ip, I pulled > out > the cable and connected it to the freebsd machine. > 2. I changed the IP to the one assigned on the laptop (ed0 interface) > 3. I added the gateway via /sbin/route and modified /etc/resolv.conf. > > --> Now, this works ok, so I know the ISP is not locking the session > based > on the MAC address (since I didn't spoof that on FreeBSD). > > So, the problem remains: dhcp doesn't work from the freebsd machine... > Those are two different things. MAC address can be blocked for new DHCP offer but firewall does not need to block MAC addresses that do not exist in the DHCP lease. The firewall may be blocking an IP which is not existing in the DHCP lease and in your case it's propably there. Check the lease time for your client. Also try to assign an IP to your PC that's not the same one as the one handed you out by DHCP server and see if you can still ping outside. Try to upgrade to 6.0 and see if the new DHCP client works. Cheers Marcin