Plain and simple: Static IP address

Hello all,

This is my first venture into suse of any sort, and it happens to be inside of a VMWare Player for work. Very simply, they need this existing install to become static IP, but I can’t figure out how to make it happen.

linux:/etc/NetworkManager # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0C:29:90:05:25  
          inet addr:10.48.112.182  Bcast:10.48.112.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe90:525/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:189457 errors:0 dropped:21 overruns:0 frame:0
          TX packets:7563 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:38983615 (37.1 Mb)  TX bytes:525170 (512.8 Kb)

10.48 is our DHCP network while 10.1 is a static network. That said, I did all the reading I could and this is what I’ve got for now:

NetworkManager.conf

[main]
plugins=ifcfg-suse,keyfile

/etc/sysconfig/network/ifcfg-eth0

BOOTPROTO='static'
BROADCAST='10.1.1.255'
IPADDR='10.1.1.245'
NETMASK='255.255.255.0'
STARTMODE='auto'
USERCONTROL='no'

I read about keyfiles, but couldn’t figure out what I should be naming them, just that they belong in /etc/NetworkManager/system-connections/. Then, when I either restart the network init script or take eth0 down with either ifconfig or nmcli and bring it back up, the IP is still in the 10.48 network.

But as far as I understand it, even though NetworkManager is managing eth0, the ifcfg-suse plugin is supposed to enable backwards compatability with the ifcfg-* style files, right? Since I couldn’t figure out what to name keyfiles, I didn’t even give that a shot. But, presuming ifcfg-eth0 should be doing its job via that plugin, I figure I must’ve messed up the syntax or something.

Any help would be appreciated. =)

On 2012-06-29 00:36, musasabi wrote:
> Any help would be appreciated. =)

Fire up Yast, select traditional network settings, define your wanted fixed
settings, apply and done.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

This is all Yast shows me:

http://musasabi.h4xful.net/misc/suseyast.jpg

musasabi wrote:
> This is all Yast shows me:
>
> [image: http://musasabi.h4xful.net/misc/suseyast.jpg]

And did you read the manual? Or even press the help key?

Every manual entry / helpful forum post that I read pointed to Yast options that were unavailable. And yes, the help screen just tells me how to navigate, haha. Not very helpful, considering I have to know how to navigate to get to it. :wink:

On 06/29/2012 10:56 AM, musasabi wrote:
>
> Every manual entry / helpful forum post that I read pointed to Yast
> options that were unavailable. And yes, the help screen just tells me
> how to navigate, haha. Not very helpful, considering I have to know how
> to navigate to get to it. :wink:

There is a GUI version that you will probably like more. With KDE, press Kickoff
(like Start), hover over Computer and select YaST. Gnome has a similar way to
get YaST started. If you cannot get that to work, then “sudo yast”. You started
it as an unprivileged user. To do most things, it needs to be run as root.

The GUI I’m working with is IceWM, so I don’t have any QT/GTK options. That’s why I originally asked about the config files, rather than a graphical solution.

Also, I ran that instance of Yast as root. I don’t know what indicated that I didn’t?

On 06/29/2012 01:16 PM, musasabi wrote:
>
> The GUI I’m working with is IceWM, so I don’t have any QT/GTK options.
> That’s why I originally asked about the config files, rather than a
> graphical solution.
>
> Also, I ran that instance of Yast as root. I don’t know what indicated
> that I didn’t?

If you do not run as root, many of the modules do not load. In your case, the
YaST modules are not installed.

The config files you need to modify are in /etc/sysconfig/network/. You will
need to set (at least) ifcfg-<ifname> and routes. Mine are

cat ifcfg-eth0

BOOTPROTO=‘static’
MTU=’’
REMOTE_IPADDR=’’
STARTMODE=‘ifplugd’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IFPLUGD_PRIORITY=‘0’
IPADDR=‘192.168.1.51/24’
NAME=’’
NETWORK=’’
USERCONTROL=‘no’

cat routes

default 192.168.1.1 - -

The only thing missing from this setup is the DNS setting, which is done in
/etc/resolv.conf.

On 2012-06-29 17:16, musasabi wrote:
>
> This is all Yast shows me:
>
> [image: http://musasabi.h4xful.net/misc/suseyast.jpg]

Probably you did not install all yast modules, so do now…


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)