Yeah, I have to agree with Steve here, there is no sense in a script asking for the address of a dhcp server, I haven't seen a program that asks for such a thing yet. When a dhcp client wants to contact a dhcp server to obtain an ip address, it broadcasts a pac request on I believe 255.255.255.255 on udp port 67, and the dhcp server for the network to which the client is connected responds. The address reported as the inet addr for your network interface by ifconfig is your address (the one the rest of the world contacts you by, and the one you use when contacting the rest of the world). Greg On Sun, Jan 11, 2004 at 07:24:25PM -0700, Steve Holmes wrote: > I didn't have to specify an IP address at all for my DHCP server at > Cox. "They" claim the modem does it or the "modem knows what to do." > What I think happens is we broadcast network wide to request an IP and > their DHCP responds. My IP gets assigned and is seen under the addr > field of ifconfig eth1. On my box, eth0 is my local network and has > an address of 192.168.1.1 and my IP on eth1 is assigned from Cox and > is currently something like 68.129.something.something:). I can't > emagine why a firewall script would be concerned about a DHCP server > address unless it is trying to block sensative addresses or something. > -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org
