Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 Feb 2003 16:33:22 -0500
From:      "Doug Reynolds" <mav@wastegate.net>
To:        "Juhani Reissell" <reissell@cc.helsinki.fi>, "questions@FreeBSD.ORG" <questions@FreeBSD.ORG>
Subject:   Re: dhclient scwewiness
Message-ID:  <20030202213336.0B9D648463@wastegate.net>
In-Reply-To: <200301282231.h0SMVip26821@sirppi.helsinki.fi>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Jan 2003 00:31:44 +0200 (EET), Juhani Reissell wrote:

>Ok, got a new cable modem. Pretty good so far. Now, I just need to get
>the DHCP client working. Haven't gotten too lucky with that so far.
>
>First, I just put the line 
>ifconfig_xl0="DHCP"
>in rc.conf.
>
>That did something. Resolv.conf looked good and the leases file in
>/var/db looked tremendous. But routing didn't work. Couldn't ping
>anything: nameservers, the supposed default routers or anything.
>
>Then, to get something in the log files, I tried starting the dhclient
>manually. Now, I see this:
>mursu dhclient: New Network Number: 213.243.154.0
>mursu dhclient: New Broadcast Address: 213.243.155.255
>mursu dhclient: New IP Address (xl0): 213.243.155.19
>mursu dhclient: New Subnet Mask (xl0): 255.255.254.0
>mursu dhclient: New Broadcast Address (xl0):213.243.155.255
>mursu dhclient: New Routers: 213.243.154.1
>in /var/log/messages.

I don't know who your Cable provider is; however, I use AT&T boardband.
 I know you have to register your NIC if you change NICs (ie update the
MAC address).  I am pretty sure they do this with the MAC address on
the cable modem as well.

---
doug reynolds | the maverick | mav@wastegate.net



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030202213336.0B9D648463>