Date: Wed, 07 Sep 2005 14:11:25 -0400 From: Gary Corcoran <gcorcoran@rcn.com> To: micko <micko@micko.net> Cc: freebsd-net@freebsd.org Subject: Re: dhcp problem Message-ID: <431F2D4D.7070705@rcn.com> In-Reply-To: <20050907163533.GA6860@micko.net> References: <20050907163533.GA6860@micko.net>
next in thread | previous in thread | raw e-mail | index | archive | help
micko wrote: > I am having trouble obtaining a dhcp address from a cable modem (comcast). > I tried using different NICs and even switch to openbsd to ruleout any > incompatibility issues, but no luck, as soon as I plug in the cheap linksys > gw everything works peachy. I tried modifying the send/request/receive values > for dhclient but that didn't change anything, bug plugging the device behind > the linksys or on a network with isc-dhcpd it works ok. Anybody on the list > using comcast, or maybe can direct me to a right place? Attached is trace > from dhclient. I don't know why you sent all that crap to the list, but... I used to be on Comcast (before I moved). As I recall, the only thing I had to do was punch a hole in my firewall to allow the DHCP server, a 172.x.x.x type IP address, to get through, and then it "just worked". Sorry, I don't know any more details, as it was long ago when I had to do the one-time setup. Oh, the other thing that bit me was once or twice a year, they would change their network, without telling us, of course, and that might result in a new netmask requirement, and always resulted in a new IP address, and sometimes new DNS server addresses. Clients directly connected would simply get the new network information via DHCP. But having an IPFW firewall script with "fixed" IP addresses, I would suddenly get nowhere on the network until I found out the new values and reconfigured my firewall. Hope this helps, Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?431F2D4D.7070705>