What creates eth0:avahi interface?
I've configured a VPN connection and it created foo interface listed with ifconfig. Its IP is assigned via dhclient foo.
From time to time, my connection drops. When I list the available interfaces with ifconfig, there is foo without an IP and foo:avahi with a random IP.
If I request an IP with dhclient foo, an IP (generally same IP) is immediately fetched, my internet connection is fixed and the foo:avahi interface is disappeared.
What is this ...:avahi interface and how can I prevent this connection drops from happening?
linux networking
asked Feb 24 at 14:49
ceremcemceremcem
208314
add a comment |
I've configured a VPN connection and it created foo interface listed with ifconfig. Its IP is assigned via dhclient foo.
From time to time, my connection drops. When I list the available interfaces with ifconfig, there is foo without an IP and foo:avahi with a random IP.
If I request an IP with dhclient foo, an IP (generally same IP) is immediately fetched, my internet connection is fixed and the foo:avahi interface is disappeared.
What is this ...:avahi interface and how can I prevent this connection drops from happening?
linux networking
asked Feb 24 at 14:49
ceremcemceremcem
208314
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32
add a comment |
I've configured a VPN connection and it created foo interface listed with ifconfig. Its IP is assigned via dhclient foo.
From time to time, my connection drops. When I list the available interfaces with ifconfig, there is foo without an IP and foo:avahi with a random IP.
If I request an IP with dhclient foo, an IP (generally same IP) is immediately fetched, my internet connection is fixed and the foo:avahi interface is disappeared.
What is this ...:avahi interface and how can I prevent this connection drops from happening?
linux networking
asked Feb 24 at 14:49
ceremcemceremcem
208314
I've configured a VPN connection and it created foo interface listed with ifconfig. Its IP is assigned via dhclient foo.
From time to time, my connection drops. When I list the available interfaces with ifconfig, there is foo without an IP and foo:avahi with a random IP.
If I request an IP with dhclient foo, an IP (generally same IP) is immediately fetched, my internet connection is fixed and the foo:avahi interface is disappeared.
What is this ...:avahi interface and how can I prevent this connection drops from happening?
linux networking
linux networking
asked Feb 24 at 14:49
ceremcemceremcem
208314
asked Feb 24 at 14:49
ceremcemceremcem
208314
asked Feb 24 at 14:49
ceremcemceremcem
208314
asked Feb 24 at 14:49
ceremcemceremcem
208314
asked Feb 24 at 14:49
ceremcemceremcem
208314
208314
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32
add a comment |
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32
add a comment |
1 Answer
1
active
oldest
votes
This isn't an interface; this is how old tools, namely ifconfig, show additional IP addresses on the eth0 interface (the kernel emulates an "interface alias" for every extra address).
The address/alias marked with "avahi" is created by avahi-autoipd, which implements RFC 3927 IPv4 link-local address autoconfiguration (also known as zeroconf or APIPA). The IP address isn't random; it's chosen from the reserved link-local prefix 169.254.0.0/16.
As for why this appears on its own, you'll need to actually check the system logs to find out; autoipd could be both the cause of the problems or it could be just the result of external problems.
It could be that some component in your system thinks no connection profile is active yet – because you've configured the IP address externally – so it deliberately switches into a "link-local only" profile and starts avahi-autoipd.
It could be that you first lose the connection, the DHCP client loses its address lease and is unable to obtain a new one, and some component on your system switches to "link-local mode" as a last resort only.
answered Feb 24 at 15:55
grawitygrawity
242k37510567
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issuedhclient footo get a new IP or is it only a workaround for a different problem?
– ceremcem
Feb 24 at 16:19
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
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%2fsuperuser.com%2fquestions%2f1408998%2fwhat-creates-eth0avahi-interface%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
This isn't an interface; this is how old tools, namely ifconfig, show additional IP addresses on the eth0 interface (the kernel emulates an "interface alias" for every extra address).
The address/alias marked with "avahi" is created by avahi-autoipd, which implements RFC 3927 IPv4 link-local address autoconfiguration (also known as zeroconf or APIPA). The IP address isn't random; it's chosen from the reserved link-local prefix 169.254.0.0/16.
As for why this appears on its own, you'll need to actually check the system logs to find out; autoipd could be both the cause of the problems or it could be just the result of external problems.
It could be that some component in your system thinks no connection profile is active yet – because you've configured the IP address externally – so it deliberately switches into a "link-local only" profile and starts avahi-autoipd.
It could be that you first lose the connection, the DHCP client loses its address lease and is unable to obtain a new one, and some component on your system switches to "link-local mode" as a last resort only.
answered Feb 24 at 15:55
grawitygrawity
242k37510567
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issuedhclient footo get a new IP or is it only a workaround for a different problem?
– ceremcem
Feb 24 at 16:19
add a comment |
This isn't an interface; this is how old tools, namely ifconfig, show additional IP addresses on the eth0 interface (the kernel emulates an "interface alias" for every extra address).
The address/alias marked with "avahi" is created by avahi-autoipd, which implements RFC 3927 IPv4 link-local address autoconfiguration (also known as zeroconf or APIPA). The IP address isn't random; it's chosen from the reserved link-local prefix 169.254.0.0/16.
As for why this appears on its own, you'll need to actually check the system logs to find out; autoipd could be both the cause of the problems or it could be just the result of external problems.
It could be that some component in your system thinks no connection profile is active yet – because you've configured the IP address externally – so it deliberately switches into a "link-local only" profile and starts avahi-autoipd.
It could be that you first lose the connection, the DHCP client loses its address lease and is unable to obtain a new one, and some component on your system switches to "link-local mode" as a last resort only.
answered Feb 24 at 15:55
grawitygrawity
242k37510567
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issuedhclient footo get a new IP or is it only a workaround for a different problem?
– ceremcem
Feb 24 at 16:19
add a comment |
This isn't an interface; this is how old tools, namely ifconfig, show additional IP addresses on the eth0 interface (the kernel emulates an "interface alias" for every extra address).
The address/alias marked with "avahi" is created by avahi-autoipd, which implements RFC 3927 IPv4 link-local address autoconfiguration (also known as zeroconf or APIPA). The IP address isn't random; it's chosen from the reserved link-local prefix 169.254.0.0/16.
As for why this appears on its own, you'll need to actually check the system logs to find out; autoipd could be both the cause of the problems or it could be just the result of external problems.
It could be that some component in your system thinks no connection profile is active yet – because you've configured the IP address externally – so it deliberately switches into a "link-local only" profile and starts avahi-autoipd.
It could be that you first lose the connection, the DHCP client loses its address lease and is unable to obtain a new one, and some component on your system switches to "link-local mode" as a last resort only.
answered Feb 24 at 15:55
grawitygrawity
242k37510567
This isn't an interface; this is how old tools, namely ifconfig, show additional IP addresses on the eth0 interface (the kernel emulates an "interface alias" for every extra address).
The address/alias marked with "avahi" is created by avahi-autoipd, which implements RFC 3927 IPv4 link-local address autoconfiguration (also known as zeroconf or APIPA). The IP address isn't random; it's chosen from the reserved link-local prefix 169.254.0.0/16.
As for why this appears on its own, you'll need to actually check the system logs to find out; autoipd could be both the cause of the problems or it could be just the result of external problems.
It could be that some component in your system thinks no connection profile is active yet – because you've configured the IP address externally – so it deliberately switches into a "link-local only" profile and starts avahi-autoipd.
It could be that you first lose the connection, the DHCP client loses its address lease and is unable to obtain a new one, and some component on your system switches to "link-local mode" as a last resort only.
answered Feb 24 at 15:55
grawitygrawity
242k37510567
answered Feb 24 at 15:55
grawitygrawity
242k37510567
answered Feb 24 at 15:55
grawitygrawity
242k37510567
answered Feb 24 at 15:55
grawitygrawity
242k37510567
242k37510567
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issuedhclient footo get a new IP or is it only a workaround for a different problem?
– ceremcem
Feb 24 at 16:19
add a comment |
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issuedhclient footo get a new IP or is it only a workaround for a different problem?
– ceremcem
Feb 24 at 16:19
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issue
dhclient foo to get a new IP or is it only a workaround for a different problem?– ceremcem
Feb 24 at 16:19
If the reason was loosing the connection first, then could the "link-local mode" be interpreted as "Currently we have no IP"? If so, is it correct to re-issue
dhclient foo to get a new IP or is it only a workaround for a different problem?– ceremcem
Feb 24 at 16:19
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1408998%2fwhat-creates-eth0avahi-interface%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
Is other network configuration software, such as NetworkManager, running on your system?
– grawity
Feb 24 at 15:20
No, NetworkManager is totally uninstalled. I'm using my own network manager.
– ceremcem
Feb 24 at 15:32