How to set network manualy?

English Network/Internet
#1

Good day! I have next situation: OpenSuse 13.1 terminal which installed on Virtual machine, wrote to me that: “icmp open sockets: Operation not permitted” when I try to ping some address without root rights; But when I use root rights, ping have no answer from any internet address, only 127.0.0.1, unlike if I ping this machine from another ip address. My question is: What is all possible methods to set network in OpenSuse 13.1 ? and How can I fix my problem?

#2

What do you exactly need?
You can configure your network with yast -> network manually. Or configure a static address with the network manager.

And for the icmp/ping thing. After you have successfully configured your network update you OS and the problem disappears.

#3

What exactly I need to do to configure network? I had tried to change network configurations files, now it’s look like this:

BOOTPROTO=‘static’
IPADDR=‘80.78.194.93/28’
NETMASK=‘255.255.255.240’
ONBOOT=‘ON’
GATEWAY=‘80.78.194.81’
NETWORK=‘random’

#4

On 2014-02-12 13:56, kartashevVladimir wrote:
>
> seilerphilipp;2624161 Wrote:
>> After you have successfully configured your network update you OS and
>> the problem disappears.
>
> What exactly I need to do to configure network? I had tried to change
> network configurations files, now it’s look like this:

in openSUSE, you use the administrative tool YaST to do things like
configuring Network. Just start YaST, locate the network configuration
section, and set it up there.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#5

If your openSUSE is a “minimal server” text only,

Then su to root, then

# yast

Use arrow keys, tabs and ALT-key commands to navigate.

If you have a Desktop installed like KDE/Gnome/LXDE/XFCE/others
Then just launch YAST from your Application Launcher, (green orb bottom left corner).

HTH,
TSU

#6

I had used YaST. The settings which I had entered into the files is applied, and I can see it in YaST, but my problem still unsolved.
If somebody can list for me all possible methods to change settings of the network, or sequence of files which system apply to setup network - It will be great.

Here is one more question, in settings of my virtual machine is selected only one network card, but SuSE create two bunches of settings for different cards:
one named “ens32” another one “eth0” why is it so?

#7

On 2014-02-13 06:46, kartashevVladimir wrote:
>
> I had used YaST. The settings which I had entered into the files is
> applied, and I can see it in YaST, but my problem still unsolved.
> If somebody can list for me all possible methods to change settings of
> the network, or sequence of files which system apply to setup network -
> It will be great.

Again, we do not change “files”. We simply use YaST. I do not really
care what files it changes.

Maybe you tried to change “the files” manually and broke things.

>
> Here is one more question, in settings of my virtual machine is selected
> only one network card, but SuSE create two bunches of settings for
> different cards:
> one named “ens32” another one “eth0” why is it so?

It is explained in the release notes.

One is bad, and it is causing your network to fail completely. You have
to use YaST to remove one, probably the eth0 one.

It is a known issue, but it is strange you have it. Is this an upgrade
of a previous machine?

Or perhaps you created, by fiddling with files directly, entries for
eth0, instead of the correct new name openSUSE now uses.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

#8

I also have a need to edit networking settings. I use a commercial application, Maple 17, which requires net access on startup to validate the product key before it will open the actual application. The problem is, that the licence manager expects to find a network interface named eth0 and simply fails, when it can’t find this. I am adviced by the Maple support to rename my current device, enp2s0, to eth0; however when I open Yast Networking Settings and try to edit enp2s0, the Configuration Name field is non-editable. Is there a way to rename enp2s0 to eth0, and is it safe to do so?