Date: Tue, 9 Mar 2004 01:14:18 -0500 From: "Steve Ireland" <stevei@black-star.net> To: <freebsd-questions@freebsd.org> Subject: Re: DHCP issue with comcast (FreeBSD router). Message-ID: <025201c4059d$c2236380$1a01a8c0@blackstar.net> References: <000a01c40542$57383ba0$50873c44@ruqj09femoiz14><404CF544.3090705@daleco.biz> <404D1CEC.8000601@mux.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Andrew Boothman" <andrew@mux.org.uk> To: "Kevin D. Kinsey, DaleCo, S.P." <kdk@daleco.biz> Cc: <freebsd-questions@freebsd.org>; "Richard Uhlman" <ruhlman@comcast.net> Sent: Monday, March 08, 2004 20:25 Subject: Re: DHCP issue with comcast (FreeBSD router). > Kevin D. Kinsey, DaleCo, S.P. wrote: > > Richard Uhlman wrote: > > > >> Hello, > >> > >> I am new to using FreeBSD, and I am trying to use a FreeBSD box as a > >> firewall/router. I am trying to get the router working correctly first. > >> My issue is that my box will not receive an IP address from Comcast when > >> the dhclient starts. I commented out all of the firewall commands in my > >> rc.conf file, but left the ifconfig_ep0="DHCP". The machine is running > >> 2 NIC's and I have verified that the correct one has the cable plugged > >> into it. I am running release 5.2.1. > > > > No expert answer, just more questions. > > Maybe they'll help? > > Here's another possibility: > > My cable company (in the UK) requires customers to register the MAC > (ethernet) address of your NIC before you're able to get an IP from them > using DHCP. > > Don't know if comcast is the same, but it's a possibility. > > Andrew > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Hello, I believe Andrew may be correct. The company I work for had a customer using a Comcast business account that had to jump thru hoops to get everything working properly. One of the things was, IIRC, registering the MAC. I also remember Comcast insisted on firewalling the IP space themselves. The customer had to call Comcast to open not only outbound ports but _inbound_ ports, as well! Of course, Comcast charged a setup fee for this "service" AND a monthly "maintenance" fee. Hope this isn't the case for you, Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?025201c4059d$c2236380$1a01a8c0>