Interface creation via iproute2 resulted to âCannot find deviceâ error
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I'm trying to create additional interface with preconfigured static IP.
So I added configuration into /etc/network/interfaces
auto eth88
iface eth88 inet static
address 10.10.0.1
netmask 255.255.255.0
And trying to up it with:
ip link set dev eth88 up
As a result I've got: "Cannot find device eth88"
In some articles I've read that interfaces represent physical devices (nic?). But I have some docker0 interface created by docker. Should I create somewhere virtual device to enable my interface?
networking network-interface iproute
add a comment |Â
up vote
-1
down vote
favorite
I'm trying to create additional interface with preconfigured static IP.
So I added configuration into /etc/network/interfaces
auto eth88
iface eth88 inet static
address 10.10.0.1
netmask 255.255.255.0
And trying to up it with:
ip link set dev eth88 up
As a result I've got: "Cannot find device eth88"
In some articles I've read that interfaces represent physical devices (nic?). But I have some docker0 interface created by docker. Should I create somewhere virtual device to enable my interface?
networking network-interface iproute
1
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
1
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
1
The first thing to understand is that that is not Linux network interfaces. That is Debian'sinterfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.
â JdeBP
Mar 31 at 19:19
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I'm trying to create additional interface with preconfigured static IP.
So I added configuration into /etc/network/interfaces
auto eth88
iface eth88 inet static
address 10.10.0.1
netmask 255.255.255.0
And trying to up it with:
ip link set dev eth88 up
As a result I've got: "Cannot find device eth88"
In some articles I've read that interfaces represent physical devices (nic?). But I have some docker0 interface created by docker. Should I create somewhere virtual device to enable my interface?
networking network-interface iproute
I'm trying to create additional interface with preconfigured static IP.
So I added configuration into /etc/network/interfaces
auto eth88
iface eth88 inet static
address 10.10.0.1
netmask 255.255.255.0
And trying to up it with:
ip link set dev eth88 up
As a result I've got: "Cannot find device eth88"
In some articles I've read that interfaces represent physical devices (nic?). But I have some docker0 interface created by docker. Should I create somewhere virtual device to enable my interface?
networking network-interface iproute
edited Apr 1 at 23:17
asked Mar 31 at 16:38
Silk0vsky
1336
1336
1
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
1
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
1
The first thing to understand is that that is not Linux network interfaces. That is Debian'sinterfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.
â JdeBP
Mar 31 at 19:19
add a comment |Â
1
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
1
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
1
The first thing to understand is that that is not Linux network interfaces. That is Debian'sinterfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.
â JdeBP
Mar 31 at 19:19
1
1
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
1
1
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
1
1
The first thing to understand is that that is not Linux network interfaces. That is Debian's
interfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.â JdeBP
Mar 31 at 19:19
The first thing to understand is that that is not Linux network interfaces. That is Debian's
interfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.â JdeBP
Mar 31 at 19:19
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
A network interface is always backed by some kernel module or similar part of the kernel that represents something, be it a physical interface, or some virtual interface that in some way talks to other interfaces. There are also dummy
interface that don't do anything; you can assign an IP address to them, but it very likely won't do what you want to achieve.
In general, you can add new interfaces with a variant of ip link add ... type ...
. See man ip-link
for details and a list of types.
You can also add several IP addresses to a single interface. With ip
, you don't need the eth0:1
etc. of ifconfig
anymore.
I suspect this is an XY-question, if you would tell us what you actually want to achieve, and what you need the second IP address for, it will be easier to answer.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
A network interface is always backed by some kernel module or similar part of the kernel that represents something, be it a physical interface, or some virtual interface that in some way talks to other interfaces. There are also dummy
interface that don't do anything; you can assign an IP address to them, but it very likely won't do what you want to achieve.
In general, you can add new interfaces with a variant of ip link add ... type ...
. See man ip-link
for details and a list of types.
You can also add several IP addresses to a single interface. With ip
, you don't need the eth0:1
etc. of ifconfig
anymore.
I suspect this is an XY-question, if you would tell us what you actually want to achieve, and what you need the second IP address for, it will be easier to answer.
add a comment |Â
up vote
3
down vote
accepted
A network interface is always backed by some kernel module or similar part of the kernel that represents something, be it a physical interface, or some virtual interface that in some way talks to other interfaces. There are also dummy
interface that don't do anything; you can assign an IP address to them, but it very likely won't do what you want to achieve.
In general, you can add new interfaces with a variant of ip link add ... type ...
. See man ip-link
for details and a list of types.
You can also add several IP addresses to a single interface. With ip
, you don't need the eth0:1
etc. of ifconfig
anymore.
I suspect this is an XY-question, if you would tell us what you actually want to achieve, and what you need the second IP address for, it will be easier to answer.
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
A network interface is always backed by some kernel module or similar part of the kernel that represents something, be it a physical interface, or some virtual interface that in some way talks to other interfaces. There are also dummy
interface that don't do anything; you can assign an IP address to them, but it very likely won't do what you want to achieve.
In general, you can add new interfaces with a variant of ip link add ... type ...
. See man ip-link
for details and a list of types.
You can also add several IP addresses to a single interface. With ip
, you don't need the eth0:1
etc. of ifconfig
anymore.
I suspect this is an XY-question, if you would tell us what you actually want to achieve, and what you need the second IP address for, it will be easier to answer.
A network interface is always backed by some kernel module or similar part of the kernel that represents something, be it a physical interface, or some virtual interface that in some way talks to other interfaces. There are also dummy
interface that don't do anything; you can assign an IP address to them, but it very likely won't do what you want to achieve.
In general, you can add new interfaces with a variant of ip link add ... type ...
. See man ip-link
for details and a list of types.
You can also add several IP addresses to a single interface. With ip
, you don't need the eth0:1
etc. of ifconfig
anymore.
I suspect this is an XY-question, if you would tell us what you actually want to achieve, and what you need the second IP address for, it will be easier to answer.
answered Mar 31 at 18:50
dirkt
14k2930
14k2930
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f434702%2finterface-creation-via-iproute2-resulted-to-cannot-find-device-error%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
A good explanation can be found here: <br> <unix.stackexchange.com/questions/128439/â¦;
â Shubhendu Yadav
Mar 31 at 16:40
1
linux-blog.anracom.com/2016/02/02/⦠look at the 1st picture. Or just search something like "veth and bridge" on google image, plenty of examples
â A.B
Mar 31 at 18:48
1
The first thing to understand is that that is not Linux network interfaces. That is Debian's
interfaces
system, which not all Linux operating systems share. So this question is not tagged or titled appropriately. Do you want to know about Debian's system, which it even tries to make work on the FreeBSD and Hurd kernels? Or about network interfaces at a basic level that is common to all Linux operating systems but not necessarily other kernels? Please fix your question as appropriate.â JdeBP
Mar 31 at 19:19