For some reason I thought that the version of YaST1 with 6.3 had the auto IP on an interface by interface basis. Are your two cards the same? If so that's probably the issue. I think YaST can get confused if you have two of the same card. One thing to do is make the DHCP interface eth0 if possible. I know on 6.2 that made life a lot easier. eth0 came up on boot with the dhclient and then I stuck the following in the init stream as seteth1. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ #! /bin/bash /sbin/ifconfig eth1 inet netmask 255.255.255.0 up 192.168.1.1 /sbin/route add -net jack-net ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ This brought up my internal network card and added the route for my internal network. I functioned for the better part of a year in Duluth using this method. I hope this helps. Let me know if you have more questions. Good Luck, Jack On Monday 26 March 2001 21:17, you wrote: > 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