>
> Just out of curiosity, does anyone on this list use a Macintosh when
> they're not using Linux? Specifically, Mac OS 8.5 or later.
I dont use a mac, however i can point you in the direction you want to go.
>
> For example [and this is a real question here :)], on my Mac I use the
> "TCP/IP Control Panel" to tell my Mac to connect to the LAN using
> Ethernet, and configure my network access using the DHCP server. When I
> make an Internet connection, the DHCP server politely assigns my Mac
> its own IP address and tells it everything it needs to know. I need to
> do the same thing on my RedHat 5.2 Linux box.
I use Redhat-6.0 with dhcp-2.0.tar.gz (BTW i also have a configuered windows
box which does the same).
A standly installed kernel from a Redhat distro is all thats needed as far
as kernel options go, everything is either compiled into the kernel of
loadable as a module.
I dont think there would be any differance between redhat-5.2 and 6.0 its a
question of kernel version in use, i use 2.2.5 with dhcp-2.0.tar.gz.
5.2 has glibc so there should be no compile problems for dhcp. DONT use a
dhcp version other than 2.0 i could not get any other version to work other
than 2.0 and that is very simple to do;
Obtain dhcp-2.0.tar.gz from ftp://ftp.isc.org/isc/dhcp/
Place it in /usr/local/src
tar xzf dhcp-2.0.tar.gz
./configure
make
You can also do make install to install the binarys in /sbin
edit /etc/rc.d/rc.local
add a line
/usr/local/src/dhcp-2.0/client/dhclient eth0
or if you did a make install
/sbin/dhclient eth0 # I tanke it you only have one card, if its a second
card then use eth1.
That takes care of getting an IP at bootime, there is no need to reboot to
start dhclient simply type;
/sbin/ifconfig eth0 up # I take it its not configured or initalised.
/sbin/dhclient eth0
That should result in eth0 getting a IP number, thats it, no need to
configure any files at all.
Possable problems;
dhclient complaing about CONFIG_FILTER and CONFIG_PACKET
You have a custom kernel and did not include support for the above.
As far as i can remember thats just about it.
Take a look at the README it has some hints for problems which could crop
up.
Of course this list also has other dhcp-2.0 users so requests for help are
suited here also.
There is a dhcp-client mailing list;
Ha, i seem to have misplaced its address but it should be retiveable at;
http://www.mail-archive.com/lists.html
>
> Now, under X (fvwm) I found that clicking the Network Configuration
> button on the Control Panel starts a handy utility to setup all this
> network info. My problem is that this Network Configurator seems to use
> terminology that differs from the Mac TCP/IP control panel. Also, it
> _appears_ to want me to keep entering the same IPs in several different
> locations. Using the Network Configurator, I've clicked the
> "Interfaces" tab and found the menu to specify DHCP. That done, do I
> still need to enter IPs left and right in the other fields? Or, having
> selected "DHCP", will I be able to plug my Ethernet cable into the
> Linux box, boot up, activate the DHCP interface and then connect to the
> LAN?
I did not use any of the above, but my card is the second card, i have 2
networks here, so i use the init scripts to configure my first card.
You can of course manualy edit /etc/sysconfig/network and
/etc/sysconfig/network-scripts/ifcfg-eth0 to do the work for you, however
considering its just 2 lines of commands i do it via /etc/rc.d/rc.local
as shown above.
>
> Any advice greatly appreciated!
> ===
> Rik Osborne
> [EMAIL PROTECTED]
> http://members.xoom.com/phase42/
> _____________________________________________________________
> Do You Yahoo!?
> Free instant messaging and more at http://messenger.yahoo.com
>
--
Regards Richard.
[EMAIL PROTECTED]
