What does ebtables.service do?
On Fedora, the firewalld
package requires ebtables
. Installing firewalld
on Debian also installs ebtables
by default, although it is a recommendation and not a hard requirement.
Fedora does not enable all services by default. It enables the systemd service for firewalld
, but not ebtables
.
Debian enables all services by default. So it enables the systemd service for both firewalld
and ebtables
.
- What does
ebtables.service
do? - Assume I am only interested in the features of
firewalld
specifically. Then does enablingebtables.service
do anything useful?
- Would disabling
ebtables.service
on Debian disable any feature offirewalld
? - Does enabling
ebtables.service
on Fedora enable any feature offirewalld
? - Is there any possible conflict between
ebtables.service
andfirewalld.service
?
- Would disabling
- What does
firewalld
useebtables
for?
Software versions
- Debian: 9
- firewalld: 0.4.4.2-1
- ebtables: 2.0.10.4-3.5+b1
- Fedora: 28
- firewalld: 0.5.5-1.fc28.noarch
- ebtables: 2.0.10-25.fc28.x86_64
debian firewalld
add a comment |
On Fedora, the firewalld
package requires ebtables
. Installing firewalld
on Debian also installs ebtables
by default, although it is a recommendation and not a hard requirement.
Fedora does not enable all services by default. It enables the systemd service for firewalld
, but not ebtables
.
Debian enables all services by default. So it enables the systemd service for both firewalld
and ebtables
.
- What does
ebtables.service
do? - Assume I am only interested in the features of
firewalld
specifically. Then does enablingebtables.service
do anything useful?
- Would disabling
ebtables.service
on Debian disable any feature offirewalld
? - Does enabling
ebtables.service
on Fedora enable any feature offirewalld
? - Is there any possible conflict between
ebtables.service
andfirewalld.service
?
- Would disabling
- What does
firewalld
useebtables
for?
Software versions
- Debian: 9
- firewalld: 0.4.4.2-1
- ebtables: 2.0.10.4-3.5+b1
- Fedora: 28
- firewalld: 0.5.5-1.fc28.noarch
- ebtables: 2.0.10-25.fc28.x86_64
debian firewalld
add a comment |
On Fedora, the firewalld
package requires ebtables
. Installing firewalld
on Debian also installs ebtables
by default, although it is a recommendation and not a hard requirement.
Fedora does not enable all services by default. It enables the systemd service for firewalld
, but not ebtables
.
Debian enables all services by default. So it enables the systemd service for both firewalld
and ebtables
.
- What does
ebtables.service
do? - Assume I am only interested in the features of
firewalld
specifically. Then does enablingebtables.service
do anything useful?
- Would disabling
ebtables.service
on Debian disable any feature offirewalld
? - Does enabling
ebtables.service
on Fedora enable any feature offirewalld
? - Is there any possible conflict between
ebtables.service
andfirewalld.service
?
- Would disabling
- What does
firewalld
useebtables
for?
Software versions
- Debian: 9
- firewalld: 0.4.4.2-1
- ebtables: 2.0.10.4-3.5+b1
- Fedora: 28
- firewalld: 0.5.5-1.fc28.noarch
- ebtables: 2.0.10-25.fc28.x86_64
debian firewalld
On Fedora, the firewalld
package requires ebtables
. Installing firewalld
on Debian also installs ebtables
by default, although it is a recommendation and not a hard requirement.
Fedora does not enable all services by default. It enables the systemd service for firewalld
, but not ebtables
.
Debian enables all services by default. So it enables the systemd service for both firewalld
and ebtables
.
- What does
ebtables.service
do? - Assume I am only interested in the features of
firewalld
specifically. Then does enablingebtables.service
do anything useful?
- Would disabling
ebtables.service
on Debian disable any feature offirewalld
? - Does enabling
ebtables.service
on Fedora enable any feature offirewalld
? - Is there any possible conflict between
ebtables.service
andfirewalld.service
?
- Would disabling
- What does
firewalld
useebtables
for?
Software versions
- Debian: 9
- firewalld: 0.4.4.2-1
- ebtables: 2.0.10.4-3.5+b1
- Fedora: 28
- firewalld: 0.5.5-1.fc28.noarch
- ebtables: 2.0.10-25.fc28.x86_64
debian firewalld
debian firewalld
asked Dec 31 '18 at 10:32
sourcejedisourcejedi
23.2k437102
23.2k437102
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I don't know what firewalld
uses ebtables
for.
Is there any possible conflict between ebtables.service and firewalld.service?
Yes. firewalld.service
is defined as Conflicts=ebtables.service
.
I believe this works and provides the desired result, both during boot, and immediately after the install. See: systemd service A has `Conflicts=B`. Both A and B are enabled. Can you tell which service will be allowed to start at boot, if any, or is it random?
I find this potentially confusing. I would consider explicitly disabling ebtables.service
.
Comparing the ebtables.service
on Debian 9 and Fedora 28, they work slightly differently.
They both have similar code, which can save ebtables rulesets when the service is stopped, and restore them when it is started.
On my Debian system, ebtables.service
reads options from /etc/default/ebtables
, which say to do almost nothing by default. It does however clear the ebtables rulesets when stopped or restarted.
On my Fedora system, ebtables.service
provides similar features. There is an options file at /etc/sysconfig/ebtables-config
which looks the same as the Debian one, but AFAICT it is not referenced by ebtables.service. Instead, all the features are fully enabled once you enable ebtables.service
.
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%2f491733%2fwhat-does-ebtables-service-do%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
I don't know what firewalld
uses ebtables
for.
Is there any possible conflict between ebtables.service and firewalld.service?
Yes. firewalld.service
is defined as Conflicts=ebtables.service
.
I believe this works and provides the desired result, both during boot, and immediately after the install. See: systemd service A has `Conflicts=B`. Both A and B are enabled. Can you tell which service will be allowed to start at boot, if any, or is it random?
I find this potentially confusing. I would consider explicitly disabling ebtables.service
.
Comparing the ebtables.service
on Debian 9 and Fedora 28, they work slightly differently.
They both have similar code, which can save ebtables rulesets when the service is stopped, and restore them when it is started.
On my Debian system, ebtables.service
reads options from /etc/default/ebtables
, which say to do almost nothing by default. It does however clear the ebtables rulesets when stopped or restarted.
On my Fedora system, ebtables.service
provides similar features. There is an options file at /etc/sysconfig/ebtables-config
which looks the same as the Debian one, but AFAICT it is not referenced by ebtables.service. Instead, all the features are fully enabled once you enable ebtables.service
.
add a comment |
I don't know what firewalld
uses ebtables
for.
Is there any possible conflict between ebtables.service and firewalld.service?
Yes. firewalld.service
is defined as Conflicts=ebtables.service
.
I believe this works and provides the desired result, both during boot, and immediately after the install. See: systemd service A has `Conflicts=B`. Both A and B are enabled. Can you tell which service will be allowed to start at boot, if any, or is it random?
I find this potentially confusing. I would consider explicitly disabling ebtables.service
.
Comparing the ebtables.service
on Debian 9 and Fedora 28, they work slightly differently.
They both have similar code, which can save ebtables rulesets when the service is stopped, and restore them when it is started.
On my Debian system, ebtables.service
reads options from /etc/default/ebtables
, which say to do almost nothing by default. It does however clear the ebtables rulesets when stopped or restarted.
On my Fedora system, ebtables.service
provides similar features. There is an options file at /etc/sysconfig/ebtables-config
which looks the same as the Debian one, but AFAICT it is not referenced by ebtables.service. Instead, all the features are fully enabled once you enable ebtables.service
.
add a comment |
I don't know what firewalld
uses ebtables
for.
Is there any possible conflict between ebtables.service and firewalld.service?
Yes. firewalld.service
is defined as Conflicts=ebtables.service
.
I believe this works and provides the desired result, both during boot, and immediately after the install. See: systemd service A has `Conflicts=B`. Both A and B are enabled. Can you tell which service will be allowed to start at boot, if any, or is it random?
I find this potentially confusing. I would consider explicitly disabling ebtables.service
.
Comparing the ebtables.service
on Debian 9 and Fedora 28, they work slightly differently.
They both have similar code, which can save ebtables rulesets when the service is stopped, and restore them when it is started.
On my Debian system, ebtables.service
reads options from /etc/default/ebtables
, which say to do almost nothing by default. It does however clear the ebtables rulesets when stopped or restarted.
On my Fedora system, ebtables.service
provides similar features. There is an options file at /etc/sysconfig/ebtables-config
which looks the same as the Debian one, but AFAICT it is not referenced by ebtables.service. Instead, all the features are fully enabled once you enable ebtables.service
.
I don't know what firewalld
uses ebtables
for.
Is there any possible conflict between ebtables.service and firewalld.service?
Yes. firewalld.service
is defined as Conflicts=ebtables.service
.
I believe this works and provides the desired result, both during boot, and immediately after the install. See: systemd service A has `Conflicts=B`. Both A and B are enabled. Can you tell which service will be allowed to start at boot, if any, or is it random?
I find this potentially confusing. I would consider explicitly disabling ebtables.service
.
Comparing the ebtables.service
on Debian 9 and Fedora 28, they work slightly differently.
They both have similar code, which can save ebtables rulesets when the service is stopped, and restore them when it is started.
On my Debian system, ebtables.service
reads options from /etc/default/ebtables
, which say to do almost nothing by default. It does however clear the ebtables rulesets when stopped or restarted.
On my Fedora system, ebtables.service
provides similar features. There is an options file at /etc/sysconfig/ebtables-config
which looks the same as the Debian one, but AFAICT it is not referenced by ebtables.service. Instead, all the features are fully enabled once you enable ebtables.service
.
edited Dec 31 '18 at 11:41
answered Dec 31 '18 at 11:18
sourcejedisourcejedi
23.2k437102
23.2k437102
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%2f491733%2fwhat-does-ebtables-service-do%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