From owner-freebsd-questions@FreeBSD.ORG Tue Apr 5 20:16:52 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 879D816A4CE for ; Tue, 5 Apr 2005 20:16:52 +0000 (GMT) Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F4D943D5E for ; Tue, 5 Apr 2005 20:16:51 +0000 (GMT) (envelope-from mark.cullen@dsl.pipex.com) Received: from [10.0.0.251] (81-179-228-238.dsl.pipex.com [81.179.228.238]) by galaxy.systems.pipex.net (Postfix) with ESMTP id 9396DE0001CF for ; Tue, 5 Apr 2005 21:16:50 +0100 (BST) Message-ID: <4252FFF1.507@dsl.pipex.com> Date: Tue, 05 Apr 2005 22:15:29 +0100 From: Mark Cullen User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: dhclient oddness? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 20:16:52 -0000 Right, I have this weird annoying issue with my modem which I have finally got around to looking in to. Basically, it's all good and works fine (obviously, otherwise I wouldn't be here!), except when I reboot the internet computer the IP will change, the connection DOESN'T drop, but the IP does change. I have just now narrowed this down to some sort of problem with dhcp I think. The modem has a dhcpd server built in, which sends out the internet IP address to the computers network card. It seems, whenever the dhcp client, dhclient in this case, gets restarted it'll get the old ip address (the first chunk of the quote below, before the ), natd will update itself, but then the connection will just stall until dhclient does the next DHCPREQUEST thing (47 seconds in this case?) .. then the modem sends back a DHCPNAK and I get a different IP address. Any ideas why this might be happening? ------------- Apr 5 17:45:01 bone dhclient: DHCPDISCOVER on fxp1 to 255.255.255.255 port 67 interval 6 Apr 5 17:45:01 bone dhclient: DHCPOFFER from 192.168.0.1 Apr 5 17:45:01 bone dhclient: DHCPREQUEST on fxp1 to 255.255.255.255 port 67 Apr 5 17:45:01 bone dhclient: DHCPACK from 192.168.0.1 Apr 5 17:45:01 bone dhclient: Old IP Address (fxp1): 81.179.214.216 Apr 5 17:45:01 bone dhclient: New IP Address (fxp1): 81.179.214.216 Apr 5 17:45:01 bone dhclient: New Subnet Mask (fxp1): 255.255.255.0 Apr 5 17:45:01 bone dhclient: New Broadcast Address (fxp1): 255.255.255.255 Apr 5 17:45:01 bone dhclient: New Routers: 81.179.214.216 Apr 5 17:45:01 bone dhclient: bound to 81.179.214.216 -- renewal in 47 seconds. Apr 5 17:45:08 bone natd[432]: Aliasing to 81.179.214.216, mtu 1500 bytes Apr 5 17:45:48 bone dhclient: DHCPREQUEST on fxp1 to 192.168.0.1 port 67 Apr 5 17:45:48 bone dhclient: DHCPNAK from 192.168.0.1 Apr 5 17:45:48 bone dhclient: DHCPDISCOVER on fxp1 to 255.255.255.255 port 67 interval 7 Apr 5 17:45:48 bone dhclient: DHCPOFFER from 192.168.0.1 Apr 5 17:45:48 bone dhclient: DHCPREQUEST on fxp1 to 255.255.255.255 port 67 Apr 5 17:45:48 bone dhclient: DHCPACK from 192.168.0.1 Apr 5 17:45:48 bone dhclient: Old IP Address (fxp1): Apr 5 17:45:48 bone dhclient: New IP Address (fxp1): 81.178.94.190 Apr 5 17:45:48 bone dhclient: New Subnet Mask (fxp1): 255.255.255.0 Apr 5 17:45:48 bone dhclient: New Broadcast Address (fxp1): 255.255.255.255 Apr 5 17:45:48 bone dhclient: New Routers: 81.178.94.190 Apr 5 17:45:48 bone dhclient: bound to 81.178.94.190 -- renewal in 53 seconds.