Interface both up and down?
Clash Royale CLAN TAG#URR8PPP
$ ip link | grep vboxnet
10: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
In the angle brackets, it says UP. What do the angle brackets indicate?
Further in the line, it claims state DOWN. This seems to conflict with the earlier information. Is the interface up or down?
In the manual pages, ip-link, ip, and ip-address, I cannot find what the angle brackets mean.
iproute
asked Jan 31 at 11:02
LucLuc
9601818
add a comment |
$ ip link | grep vboxnet
10: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
In the angle brackets, it says UP. What do the angle brackets indicate?
Further in the line, it claims state DOWN. This seems to conflict with the earlier information. Is the interface up or down?
In the manual pages, ip-link, ip, and ip-address, I cannot find what the angle brackets mean.
iproute
asked Jan 31 at 11:02
LucLuc
9601818
1
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10
add a comment |
$ ip link | grep vboxnet
10: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
In the angle brackets, it says UP. What do the angle brackets indicate?
Further in the line, it claims state DOWN. This seems to conflict with the earlier information. Is the interface up or down?
In the manual pages, ip-link, ip, and ip-address, I cannot find what the angle brackets mean.
iproute
asked Jan 31 at 11:02
LucLuc
9601818
$ ip link | grep vboxnet
10: vboxnet0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
In the angle brackets, it says UP. What do the angle brackets indicate?
Further in the line, it claims state DOWN. This seems to conflict with the earlier information. Is the interface up or down?
In the manual pages, ip-link, ip, and ip-address, I cannot find what the angle brackets mean.
iproute
iproute
asked Jan 31 at 11:02
LucLuc
9601818
asked Jan 31 at 11:02
LucLuc
9601818
asked Jan 31 at 11:02
LucLuc
9601818
asked Jan 31 at 11:02
LucLuc
9601818
asked Jan 31 at 11:02
LucLuc
9601818
9601818
1
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10
add a comment |
1
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10
1
1
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10
add a comment |
1 Answer
1
active
oldest
votes
Within the angle brackets there is a list of flags (= on/off type properties) of the interface. After the flags, other non-binary properties are listed.
There are two concepts you should be aware of:
administrative state: the state you've commanded the network interface to be (i.e. active or not)
operational state: the state the network interface is actually in
If you configure the network interface, its administrative state will be set to UP immediately, but the operational state will change only after the physical interface is successfully powered up, the link pulse from the other end has been detected, autonegotiation has been completed (if applicable) and the interface and the driver are fully ready to pass traffic.
In the ip link output, the UP flag describes the interface's administrative state. There are two other flags: LOWER_UP that gets added when the card is physically ready for traffic, and NO-CARRIER if there is no signal from the other end. These two flags would be considered parts of the operational state.
So, your vboxnet0 interface has been commanded to be up (= active), but currently there are no virtual machines connected to this virtual interface, so the interface is flagged NO-CARRIER and is therefore operationally down, at least until some virtual machine starts using it.
The actual kernel-level flags are called IFF_UP for "interface administratively enabled" and IFF_RUNNING for "interface operationally ready". The old ifconfig command used to just show them directly (without the IFF_ prefix), but the absence of RUNNING was not easy to notice, so ip link command now has this logic:
IF (IFF_UP is set) AND (IFF_RUNNING is not set)
THEN display an extra flag "NO-CARRIER" in the flags field
The kernel-level flags are described in the netdevices(7) man page.
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497907%2finterface-both-up-and-down%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Within the angle brackets there is a list of flags (= on/off type properties) of the interface. After the flags, other non-binary properties are listed.
There are two concepts you should be aware of:
administrative state: the state you've commanded the network interface to be (i.e. active or not)
operational state: the state the network interface is actually in
If you configure the network interface, its administrative state will be set to UP immediately, but the operational state will change only after the physical interface is successfully powered up, the link pulse from the other end has been detected, autonegotiation has been completed (if applicable) and the interface and the driver are fully ready to pass traffic.
In the ip link output, the UP flag describes the interface's administrative state. There are two other flags: LOWER_UP that gets added when the card is physically ready for traffic, and NO-CARRIER if there is no signal from the other end. These two flags would be considered parts of the operational state.
So, your vboxnet0 interface has been commanded to be up (= active), but currently there are no virtual machines connected to this virtual interface, so the interface is flagged NO-CARRIER and is therefore operationally down, at least until some virtual machine starts using it.
The actual kernel-level flags are called IFF_UP for "interface administratively enabled" and IFF_RUNNING for "interface operationally ready". The old ifconfig command used to just show them directly (without the IFF_ prefix), but the absence of RUNNING was not easy to notice, so ip link command now has this logic:
IF (IFF_UP is set) AND (IFF_RUNNING is not set)
THEN display an extra flag "NO-CARRIER" in the flags field
The kernel-level flags are described in the netdevices(7) man page.
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
add a comment |
Within the angle brackets there is a list of flags (= on/off type properties) of the interface. After the flags, other non-binary properties are listed.
There are two concepts you should be aware of:
administrative state: the state you've commanded the network interface to be (i.e. active or not)
operational state: the state the network interface is actually in
If you configure the network interface, its administrative state will be set to UP immediately, but the operational state will change only after the physical interface is successfully powered up, the link pulse from the other end has been detected, autonegotiation has been completed (if applicable) and the interface and the driver are fully ready to pass traffic.
In the ip link output, the UP flag describes the interface's administrative state. There are two other flags: LOWER_UP that gets added when the card is physically ready for traffic, and NO-CARRIER if there is no signal from the other end. These two flags would be considered parts of the operational state.
So, your vboxnet0 interface has been commanded to be up (= active), but currently there are no virtual machines connected to this virtual interface, so the interface is flagged NO-CARRIER and is therefore operationally down, at least until some virtual machine starts using it.
The actual kernel-level flags are called IFF_UP for "interface administratively enabled" and IFF_RUNNING for "interface operationally ready". The old ifconfig command used to just show them directly (without the IFF_ prefix), but the absence of RUNNING was not easy to notice, so ip link command now has this logic:
IF (IFF_UP is set) AND (IFF_RUNNING is not set)
THEN display an extra flag "NO-CARRIER" in the flags field
The kernel-level flags are described in the netdevices(7) man page.
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
add a comment |
Within the angle brackets there is a list of flags (= on/off type properties) of the interface. After the flags, other non-binary properties are listed.
There are two concepts you should be aware of:
administrative state: the state you've commanded the network interface to be (i.e. active or not)
operational state: the state the network interface is actually in
If you configure the network interface, its administrative state will be set to UP immediately, but the operational state will change only after the physical interface is successfully powered up, the link pulse from the other end has been detected, autonegotiation has been completed (if applicable) and the interface and the driver are fully ready to pass traffic.
In the ip link output, the UP flag describes the interface's administrative state. There are two other flags: LOWER_UP that gets added when the card is physically ready for traffic, and NO-CARRIER if there is no signal from the other end. These two flags would be considered parts of the operational state.
So, your vboxnet0 interface has been commanded to be up (= active), but currently there are no virtual machines connected to this virtual interface, so the interface is flagged NO-CARRIER and is therefore operationally down, at least until some virtual machine starts using it.
The actual kernel-level flags are called IFF_UP for "interface administratively enabled" and IFF_RUNNING for "interface operationally ready". The old ifconfig command used to just show them directly (without the IFF_ prefix), but the absence of RUNNING was not easy to notice, so ip link command now has this logic:
IF (IFF_UP is set) AND (IFF_RUNNING is not set)
THEN display an extra flag "NO-CARRIER" in the flags field
The kernel-level flags are described in the netdevices(7) man page.
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
Within the angle brackets there is a list of flags (= on/off type properties) of the interface. After the flags, other non-binary properties are listed.
There are two concepts you should be aware of:
administrative state: the state you've commanded the network interface to be (i.e. active or not)
operational state: the state the network interface is actually in
If you configure the network interface, its administrative state will be set to UP immediately, but the operational state will change only after the physical interface is successfully powered up, the link pulse from the other end has been detected, autonegotiation has been completed (if applicable) and the interface and the driver are fully ready to pass traffic.
In the ip link output, the UP flag describes the interface's administrative state. There are two other flags: LOWER_UP that gets added when the card is physically ready for traffic, and NO-CARRIER if there is no signal from the other end. These two flags would be considered parts of the operational state.
So, your vboxnet0 interface has been commanded to be up (= active), but currently there are no virtual machines connected to this virtual interface, so the interface is flagged NO-CARRIER and is therefore operationally down, at least until some virtual machine starts using it.
The actual kernel-level flags are called IFF_UP for "interface administratively enabled" and IFF_RUNNING for "interface operationally ready". The old ifconfig command used to just show them directly (without the IFF_ prefix), but the absence of RUNNING was not easy to notice, so ip link command now has this logic:
IF (IFF_UP is set) AND (IFF_RUNNING is not set)
THEN display an extra flag "NO-CARRIER" in the flags field
The kernel-level flags are described in the netdevices(7) man page.
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
answered Jan 31 at 15:14
telcoMtelcoM
18k12347
18k12347
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497907%2finterface-both-up-and-down%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Related (about flags in angle brackets): unix.stackexchange.com/q/335077/315749
– fra-san
Jan 31 at 11:10