This change over to dynamic IP's has been anything but easy. It has taken me several days to get this straightened out. So, I'll pass it along.
I was using @HOME with a static IP. I use register.com to maintain my domain hammershome.com, which points to my static ip. With comcast, there are no static ip's, so, here is what happened. First, to get the dynamic ip from comcast, you need to include a -h parameter. I used my old @HOME name, but I don't think it matters. Any name might do. You can't use the -H parameter. So: dhcpcd -d -h somehostname eth1 Works. This puts your parameters into /var/run/dhcpcd-eth1.info. It creates a /etc/resolv.conf.dhcp which contains your new domain name and name servers. And it saves your old /etc/resolv.conf in /etc/resolv.conf.dhcp.sv. This is all you can count on dhcpcd doing. It doesn't: 1. Change /etc/resolv.conf. 2. It doesn't configure your card. 3. It doesn't set up routes. 4. It doesn't change your host name. For example, my new /etc/resolv.conf.dhcp contains the following: # # Generated by dhcpcd from DHCP server information. # domain towson01.md.pvcomcast.net nameserver 68.34.76.5 nameserver 68.34.76.6 This might work for some, but since I run a local name server, I had to change the domain name and add my own name server, like so: domain hammershome.com nameserver 192.168.0.2 nameserver 68.34.76.5 nameserver 68.34.76.6 Now, dhcpcd is supposed to keep running, keeping up a communication with the dhcp server and maybe even configuring your route. However, comcast gives an infinite lease (see more below) and so dhcpcd exits after getting the lease. So, you have to configure your card and set up your own default route in your network startup script, like so: . /var/run/dhcpcd-eth1.info /sbin/ifconfig eth1 down /sbin/ifconfig eth1 $IPADDR netmask $NETMASK broadcast $BROADCAST /sbin/route add -net default gw $GATEWAY eth1 This all was easy. The hard part was the host name. I thought my computer should have a host name recognized by comcast, so, running host against my new ip number like so: host 68.33.14.228 228.14.33.68.IN-ADDR.ARPA domain name pointer pcp364928pcs.towson01.md.pvcomcast.net I got the huge host name starting with pcp above. Now, with @HOME, this huge host name (static) was resolvable on the internet. (cc8846558-a was my old @HOME name. Boy, I sure miss it.) I used it for my host name. I assumed this new name would be resolvable, too, and changed all occurences of cc884558-a to the new name. Bad choice. This new name is NOT resolvable on the internet, and many bad things happen to your email, when your host name cannot be resolved. So, I redid my hostname to hammershome.com, and, for now, things seem to be working. Now, about those infinite leases. I am not sure what that means. After I got my first lease using my old cc846 name, I tried getting another lease with my new pcp... name, and got a new ip number. So, I just don't know what their servers are doing. Maybe if you always use the same host name you will get the same lease ip. I haven't got the energy to test this right now. It takes about 8 hours for register.com to update my ip, so I don't feel like trying out various names and seeing what I get. Joel Joel Joel _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
