On Monday 16 June 2008 15:59:09 Rodney Baker wrote:
On Mon, 16 Jun 2008 20:20:13 Nico Sabbi wrote:
please, can you explain how you set up the options for each card? I need to set 2 different names, one for each ethernet card that I want to configure via dhcp/ddns, but I can't find a way to make this mechanism work. So far I always thought that the networking setup in openSuse is as broken and undecipherable as in debian (as opposed to the clear one in Fedora), but if you say that I can make it work how I need it I'll be really happy. Thanks, Nico
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
If you can it is usually easier (for a small network) to use static IP's for multiple interfaces though. In my case I have my primary interface via DHCP and the secondary interface with a static IP address.
yes, it's easier, but I'd like to solve this problem using DHCP alone
You can only have *one* default gateway (i.e. the address that all non-local traffic for which their is no route configured will be sent through).
it is only one for the reason I wrote (same network)
With 2 network cards some form of dynamic routing table management makes things much easier; this is what the route daemon (routed) is for. Make sure that it is installed and running (set it to autostart via the runlevel editor) unless you have a good reason not to use it. Provided you have routers on the network that publish routing information via RIP it will then learn which interface to use for what networks.
unneeded in this case, same reason
In the YaST Network Devices/Network Card utility, on the Global Options page make sure you select Traditional Method with ifup as the Network Setup Method. I found it to be much more reliable on all my machines than letting it use NetworkManager.
If you don't have any IPv6 devices on your network you may as well uncheck the Enable IPv6 checkbox on this tab too (although I haven't bothered to). The DHCP Client Options I've left at the default settings.
On the Overview tab select each interface in turn, click the Configure button and ensure that it is set for DHCP or static IP as appropriate. On the General tab of the configuration screen select At Boot Time or On Cable Connection if you want the interface to start automatically. For a wireless connection On Hotplug may be more appropriate but I haven't tested that - YMMV. My laptops are set to enable wireless at boot time and wired ethernet on cable connection. My desktop enables both wired connections at boot time.
After saving the interface-specific settings, on the HostName/DNS tab you can configure whether or not to update the hostname and dns settings via DHCP or set them statically. Mine are static.
but in yast there's only one name entry, not one for interface.
The Routing tab is where you set the default gateway, set up any static routes and turn on IP forwarding (via the Enable IP Forwarding check box). Only enable IP forwarding if you're planning to use the machine as a router or bridge between 2 otherwise unconnected networks.
Incidentally, I don't have a default gateway set on my desktop machine because routed takes care of that for me.
Hope this helps.
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? 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? Where's a specification of the valid settings for the ifcfg-ethN files? Thanks, Nico -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org