On Wed, 18 Jun 2008 23:14:53 Nico Sabbi wrote:
On Monday 16 June 2008 15:59:09 Rodney Baker wrote:
[...] Nico, How exactly do you want it to work? If you want to use DHCP for both network cards then each card must have access to a DHCP server for the network that they will talk to.
it's exactly what I need. Actually they are both in the same network for long and boring reasons that I'd better avoid explaining (thus there's only 1 default gateway) , but the issue remains: multi-homing
Multi-homing is not (as I understand it) having both network cards on the same network; a multi-homed host is one that exists simultaneously on more than one network (e.g. a server with 2 or more network interfaces, each talking to a different subnet or network and not bridging the networks together (that is the job of a router).
[...] thanks for your detailed explanation, but unfortunately the main issue remains: I can't find a way to assign a name specific for the network interface rather than global :( Is a multi-homed configuration impossible in Suse?
As mentioned (or at least implied) above, multi-homed does not mean having multiple host names for a single machine. In fact, the host name configured in the local machine is not that relevant in the overall networking scheme of things. If you need to connect to the different IP addresses using different host names, that is where /etc/hosts and/or dns come into play. If you run a dns server on your local network, you can assign as many names as you like to a given IP address. If you have a wireless and/or dsl router on your network they often include a dns server and/or proxy. Otherwise, try reading up on bind (the Berkeley Internet Name Daemon).
Well, maybe not: settting DHCLIENT_HOSTNAME_OPTION=myname2 in /etc/sysconfig/network-scripts/ifcfg-eth0 and disabling
DHCLIENT_HOSTNAME_OPTION and DHCLIENT_CLIENT_ID
in /etc/sysconfig/network-scripts/dhcp
seems to work as expected, at least with a single network interface, but then why isn't it possible to specify a configuration like that in yast?
YaST seems to be mainly designed at basic, dare I say "lowest common denominator" setups in many cases, which is fair enough for the average user who does not need to do more advanced stuff. Those users who do need advanced features or configurations will usually either a) know enough to manually hack the configuration files or b) know where to go to get the information to allow them to learn how to hack the config files :-).
Where's a specification of the valid settings for the ifcfg-ethN files? Thanks, Nico
Try man ifcfg... -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== The grand leap of the whale up the Fall of Niagara is esteemed, by all who have seen it, as one of the finest spectacles in nature. -- Benjamin Franklin.