SuSE 6.3, with YAST1. The box is not big enough for X. No I can't bring up the second card (eth1 is the external interface), partly because I can't find decent documentation on how to do that. How do you do that with dhclient? I can find all kinds of stuff on dhcpcd, but since I don't do much with the box, I'd prefer to keep all mgmt within Yast if I can (avoiding editing scripts if I can help it). If not, then for as often as I boot the box, I don't care if Yast/SuSE can never bring up the interface on boot, I just need it working. I know it's doable, and with static IP, it's cake, but I'm losing my static IP in a few days and going with RR. It looks like it's supposed to work, but my bash skills are light, so I don't know if I'm reading the scripts correctly. Would you be able to give me an example of bringing up the interface manually? Thanks for any help, - Dave On 2001.03.26 14:04:49 -0600 jack at jacku.com wrote: > Which version of SuSE are you using? I've got DHCP working with an > AT&T Broadband Cable Modem and SuSE 7.0 Pro. > > Are you managing with YAST1 or YAST2? If you're not using YAST1 I > recommend that. Can you manually bring up the second ethernet card? On > the older SuSE versions (Pre 6.3) if you opted for DHCP it only > allowed you to configure the one card in YAST. On my current system I > took a manual activation of the second ethernet card before YAST found > it and now it restarts on bootup just fine. (Of course its been up > since November so I think that's right. ;-) > > FWIW what you want to do is doable. > > Jack > > On Sun, 25 March 2001, Dave Kleist wrote: -- Dave Kleist dkleist at acm.org "The covers of this book are too far apart." - Ambrose Bierce