On 6/4/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
You could hard-code this to a fixed address, and then not use DHCP to get an address, if you wanted to fixed address. Here is an example that can make a hard-coded address: [EMAIL PROTECTED]: ~ > cat /etc/sysconfig/network-devices/ifconfig.eth0/ipv4 ONBOOT=yes SERVICE=ipv4-static IP=192.168.0.232 GATEWAY=192.168.0.1 PREFIX=24 BROADCAST=192.168.0.255 So, notice that the 192.168.0.1 address is my gateway. This address is of a router that talks to another router, which handles traffic to the broadband vendor.
I'm kind of shooting from the hip, but you can also control the router DHCP to do these kind of things. For a while I've had one PC, but back when I was living with a bunch of people we used a Linksys router. On that router, you could open a browser to http://192.168.1.1 and a simple web interface was there for control. Most of the interesting parameters such as fixed IP addresses and port forwarding were under an advanced tab. Then you could specify that certain network cards always receive specific IP addresses. I'm not a DHCP expert, but this is the way it's set up at my work for a cluster of Linux servers with one master. Also, the DHCP server can send you a domain name. I'm not sure under what circumstances it's used, but look at /etc/resolv.conf to see what info your router is giving you. Mine sends me a domain, but apparently the one I set up at DynDNS is preferred as returned by `dnsdomainname'. As you can see, I'm not the networking expert, but it might be worth your time to try to figure out more about the router's DHCP server.
Keep up the good work, Randy!
I thought you were referring to yourself in the third person. :) -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
