Ubuntu 16.04 Unknown interface

I have an issue when configuring a second nic for my ubuntu server. Look at this:

root@ubuntubox01:~# lshw -short | grep network

/0/100/15/0          ens160      network    VMXNET3 Ethernet Controller

/0/100/16/0          ens192      network    VMXNET3 Ethernet Controller

When I look at the IP Addresses:

root@ubuntubox01:~# ip addr sh

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host 

   valid_lft forever preferred_lft forever

2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff

inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160

   valid_lft forever preferred_lft forever

inet6 fe80::250:56ff:feb6:5289/64 scope link 

   valid_lft forever preferred_lft forever

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff

inet6 fe80::250:56ff:feb6:e22d/64 scope link 

   valid_lft forever preferred_lft forever

But if I do:

root@ubuntubox01:~# ifup ens192

Unknown interface ens192

Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?

I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.

Greetings,

asked Oct 30 '17 at 12:00

Carlos Bravo

112

bumped to the homepage by Community♦ 2 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

I have an issue when configuring a second nic for my ubuntu server. Look at this:

root@ubuntubox01:~# lshw -short | grep network

/0/100/15/0          ens160      network    VMXNET3 Ethernet Controller

/0/100/16/0          ens192      network    VMXNET3 Ethernet Controller

When I look at the IP Addresses:

root@ubuntubox01:~# ip addr sh

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host 

   valid_lft forever preferred_lft forever

2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff

inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160

   valid_lft forever preferred_lft forever

inet6 fe80::250:56ff:feb6:5289/64 scope link 

   valid_lft forever preferred_lft forever

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff

inet6 fe80::250:56ff:feb6:e22d/64 scope link 

   valid_lft forever preferred_lft forever

But if I do:

root@ubuntubox01:~# ifup ens192

Unknown interface ens192

Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?

I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.

Greetings,

asked Oct 30 '17 at 12:00

Carlos Bravo

112

bumped to the homepage by Community♦ 2 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

I have an issue when configuring a second nic for my ubuntu server. Look at this:

root@ubuntubox01:~# lshw -short | grep network

/0/100/15/0          ens160      network    VMXNET3 Ethernet Controller

/0/100/16/0          ens192      network    VMXNET3 Ethernet Controller

When I look at the IP Addresses:

root@ubuntubox01:~# ip addr sh

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host 

   valid_lft forever preferred_lft forever

2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff

inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160

   valid_lft forever preferred_lft forever

inet6 fe80::250:56ff:feb6:5289/64 scope link 

   valid_lft forever preferred_lft forever

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff

inet6 fe80::250:56ff:feb6:e22d/64 scope link 

   valid_lft forever preferred_lft forever

But if I do:

root@ubuntubox01:~# ifup ens192

Unknown interface ens192

Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?

I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.

Greetings,

asked Oct 30 '17 at 12:00

Carlos Bravo

112

I have an issue when configuring a second nic for my ubuntu server. Look at this:

root@ubuntubox01:~# lshw -short | grep network

/0/100/15/0          ens160      network    VMXNET3 Ethernet Controller

/0/100/16/0          ens192      network    VMXNET3 Ethernet Controller

When I look at the IP Addresses:

root@ubuntubox01:~# ip addr sh

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host 

   valid_lft forever preferred_lft forever

2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:52:89 brd ff:ff:ff:ff:ff:ff

inet XXX.XXX.XXX.XXX/24 brd XXX.XXX.XXX.XXX scope global ens160

   valid_lft forever preferred_lft forever

inet6 fe80::250:56ff:feb6:5289/64 scope link 

   valid_lft forever preferred_lft forever

3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

link/ether 00:50:56:b6:e2:2d brd ff:ff:ff:ff:ff:ff

inet6 fe80::250:56ff:feb6:e22d/64 scope link 

   valid_lft forever preferred_lft forever

But if I do:

root@ubuntubox01:~# ifup ens192

Unknown interface ens192

Same thing happens when I try to use the interfaces file. Any ideas as to why ubuntu sees the physical interface but refuses to bring it up saying the interface is unknown?

I am using ubuntu 16.04 Server 64 bits. It is a virtual environment by the way.

Greetings,

16.04 networking server network-bridge

asked Oct 30 '17 at 12:00

Carlos Bravo

112

asked Oct 30 '17 at 12:00

Carlos Bravo

112

asked Oct 30 '17 at 12:00

Carlos Bravo

112

asked Oct 30 '17 at 12:00

Carlos Bravo

112

asked Oct 30 '17 at 12:00

Carlos Bravo

112

bumped to the homepage by Community♦ 2 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

bumped to the homepage by Community♦ 2 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment |

2 Answers
2

active

oldest

votes

Check your /etc/network/interfaces file,
it should contain:

auto ens192 

iface ens192 inet dhcp

or for static:

auto ens192 

iface ens192 inet static

#params

answered Nov 21 '17 at 4:46

Николай Регулярный

add a comment |

you can do:

sudo ip link set dev eth0 down

sudo dhclient eth0

replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f970878%2fubuntu-16-04-unknown-interface%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

Check your /etc/network/interfaces file,
it should contain:

auto ens192 

iface ens192 inet dhcp

or for static:

auto ens192 

iface ens192 inet static

#params

answered Nov 21 '17 at 4:46

Николай Регулярный

add a comment |

Check your /etc/network/interfaces file,
it should contain:

auto ens192 

iface ens192 inet dhcp

or for static:

auto ens192 

iface ens192 inet static

#params

answered Nov 21 '17 at 4:46

Николай Регулярный

add a comment |

Check your /etc/network/interfaces file,
it should contain:

auto ens192 

iface ens192 inet dhcp

or for static:

auto ens192 

iface ens192 inet static

#params

answered Nov 21 '17 at 4:46

Николай Регулярный

Check your /etc/network/interfaces file,
it should contain:

auto ens192 

iface ens192 inet dhcp

or for static:

auto ens192 

iface ens192 inet static

#params

answered Nov 21 '17 at 4:46

Николай Регулярный

answered Nov 21 '17 at 4:46

Николай Регулярный

answered Nov 21 '17 at 4:46

Николай Регулярный

answered Nov 21 '17 at 4:46

Николай Регулярный

add a comment |

you can do:

sudo ip link set dev eth0 down

sudo dhclient eth0

replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

add a comment |

you can do:

sudo ip link set dev eth0 down

sudo dhclient eth0

replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

add a comment |

you can do:

sudo ip link set dev eth0 down

sudo dhclient eth0

replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

you can do:

sudo ip link set dev eth0 down

sudo dhclient eth0

replace eth0 with the interface name. The snippet is taken from https://help.ubuntu.com/community/NetworkConfigurationCommandLine/Automatic

Also, check the spelling of everything in /etc/network/interfaces. I had the same issue as you described, because the iface name was misspelled.

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

edited Jun 17 '18 at 7:17

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

answered Jun 17 '18 at 6:55

Victor Piousbox

1013

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Ask Ubuntu!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Jtdcftul