Can't start virhs network: iptables: No chain/target/match by that name
I am installing Minishift and part of the installation requires to configure virsh network.
The status is inactive:
root@ubuntu-aws:~# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default inactive yes yes
I tried to start it but I received an error:
root@ubuntu-aws:~# virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name.
I am running ubuntu on AWS and all the external traffic is currently open.
root@ubuntu-aws:~# uname -a && lsb_release -a
Linux ip-172-31-27-9 4.4.0-1057-aws #66-Ubuntu SMP Thu May 3 12:49:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
EDIT:
root@ubuntu-aws:~# iptables -L -t filter
Chain INPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain DOCKER (1 references)
target prot opt source destination
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain KUBE-FIREWALL (2 references)
target prot opt source destination
DROP all -- anywhere anywhere /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000
networking iptables firewall
add a comment |
I am installing Minishift and part of the installation requires to configure virsh network.
The status is inactive:
root@ubuntu-aws:~# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default inactive yes yes
I tried to start it but I received an error:
root@ubuntu-aws:~# virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name.
I am running ubuntu on AWS and all the external traffic is currently open.
root@ubuntu-aws:~# uname -a && lsb_release -a
Linux ip-172-31-27-9 4.4.0-1057-aws #66-Ubuntu SMP Thu May 3 12:49:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
EDIT:
root@ubuntu-aws:~# iptables -L -t filter
Chain INPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain DOCKER (1 references)
target prot opt source destination
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain KUBE-FIREWALL (2 references)
target prot opt source destination
DROP all -- anywhere anywhere /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000
networking iptables firewall
Hello and welcome to AskUbuntu! Can you edit your question and post the output ofiptables -L -t filter?
– Mr Shunz
Mar 19 at 11:06
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
Maybe it because I don't have interface namedvirbr0?
– E235
Mar 19 at 12:13
add a comment |
I am installing Minishift and part of the installation requires to configure virsh network.
The status is inactive:
root@ubuntu-aws:~# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default inactive yes yes
I tried to start it but I received an error:
root@ubuntu-aws:~# virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name.
I am running ubuntu on AWS and all the external traffic is currently open.
root@ubuntu-aws:~# uname -a && lsb_release -a
Linux ip-172-31-27-9 4.4.0-1057-aws #66-Ubuntu SMP Thu May 3 12:49:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
EDIT:
root@ubuntu-aws:~# iptables -L -t filter
Chain INPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain DOCKER (1 references)
target prot opt source destination
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain KUBE-FIREWALL (2 references)
target prot opt source destination
DROP all -- anywhere anywhere /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000
networking iptables firewall
I am installing Minishift and part of the installation requires to configure virsh network.
The status is inactive:
root@ubuntu-aws:~# virsh net-list --all
Name State Autostart Persistent
----------------------------------------------------------
default inactive yes yes
I tried to start it but I received an error:
root@ubuntu-aws:~# virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert INPUT --in-interface virbr0 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name.
I am running ubuntu on AWS and all the external traffic is currently open.
root@ubuntu-aws:~# uname -a && lsb_release -a
Linux ip-172-31-27-9 4.4.0-1057-aws #66-Ubuntu SMP Thu May 3 12:49:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
EDIT:
root@ubuntu-aws:~# iptables -L -t filter
Chain INPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain FORWARD (policy DROP)
target prot opt source destination
DOCKER-USER all -- anywhere anywhere
DOCKER-ISOLATION-STAGE-1 all -- anywhere anywhere
ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED
DOCKER all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
KUBE-FIREWALL all -- anywhere anywhere
Chain DOCKER (1 references)
target prot opt source destination
Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target prot opt source destination
DOCKER-ISOLATION-STAGE-2 all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target prot opt source destination
DROP all -- anywhere anywhere
RETURN all -- anywhere anywhere
Chain DOCKER-USER (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
Chain KUBE-FIREWALL (2 references)
target prot opt source destination
DROP all -- anywhere anywhere /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000
networking iptables firewall
networking iptables firewall
edited Mar 19 at 11:37
E235
asked Mar 19 at 10:51
E235E235
1134
1134
Hello and welcome to AskUbuntu! Can you edit your question and post the output ofiptables -L -t filter?
– Mr Shunz
Mar 19 at 11:06
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
Maybe it because I don't have interface namedvirbr0?
– E235
Mar 19 at 12:13
add a comment |
Hello and welcome to AskUbuntu! Can you edit your question and post the output ofiptables -L -t filter?
– Mr Shunz
Mar 19 at 11:06
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
Maybe it because I don't have interface namedvirbr0?
– E235
Mar 19 at 12:13
Hello and welcome to AskUbuntu! Can you edit your question and post the output of
iptables -L -t filter?– Mr Shunz
Mar 19 at 11:06
Hello and welcome to AskUbuntu! Can you edit your question and post the output of
iptables -L -t filter?– Mr Shunz
Mar 19 at 11:06
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
Maybe it because I don't have interface named
virbr0 ?– E235
Mar 19 at 12:13
Maybe it because I don't have interface named
virbr0 ?– E235
Mar 19 at 12:13
add a comment |
1 Answer
1
active
oldest
votes
It seems that the Amazon EC2 I was using doesn't support nested VM.
I tried to install the virsh network on my ubuntu VMware and enabled the Virtualize Intel VT-x/EPT or AMD-V/RVI field in the CPU properties and I was able to do so.
I also needed to fix some networking issues I had so I added my interface ens33 to the /etc/network/interfaces:
root@ubuntu:~/minishift-1.32.0-linux-amd64# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto ens33
iface ens33 inet dhcp
And disabled the Network manager because it was erasing the resolv.conf file each time:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
add a comment |
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1126907%2fcant-start-virhs-network-iptables-no-chain-target-match-by-that-name%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
It seems that the Amazon EC2 I was using doesn't support nested VM.
I tried to install the virsh network on my ubuntu VMware and enabled the Virtualize Intel VT-x/EPT or AMD-V/RVI field in the CPU properties and I was able to do so.
I also needed to fix some networking issues I had so I added my interface ens33 to the /etc/network/interfaces:
root@ubuntu:~/minishift-1.32.0-linux-amd64# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto ens33
iface ens33 inet dhcp
And disabled the Network manager because it was erasing the resolv.conf file each time:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
add a comment |
It seems that the Amazon EC2 I was using doesn't support nested VM.
I tried to install the virsh network on my ubuntu VMware and enabled the Virtualize Intel VT-x/EPT or AMD-V/RVI field in the CPU properties and I was able to do so.
I also needed to fix some networking issues I had so I added my interface ens33 to the /etc/network/interfaces:
root@ubuntu:~/minishift-1.32.0-linux-amd64# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto ens33
iface ens33 inet dhcp
And disabled the Network manager because it was erasing the resolv.conf file each time:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
add a comment |
It seems that the Amazon EC2 I was using doesn't support nested VM.
I tried to install the virsh network on my ubuntu VMware and enabled the Virtualize Intel VT-x/EPT or AMD-V/RVI field in the CPU properties and I was able to do so.
I also needed to fix some networking issues I had so I added my interface ens33 to the /etc/network/interfaces:
root@ubuntu:~/minishift-1.32.0-linux-amd64# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto ens33
iface ens33 inet dhcp
And disabled the Network manager because it was erasing the resolv.conf file each time:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
It seems that the Amazon EC2 I was using doesn't support nested VM.
I tried to install the virsh network on my ubuntu VMware and enabled the Virtualize Intel VT-x/EPT or AMD-V/RVI field in the CPU properties and I was able to do so.
I also needed to fix some networking issues I had so I added my interface ens33 to the /etc/network/interfaces:
root@ubuntu:~/minishift-1.32.0-linux-amd64# cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
auto ens33
iface ens33 inet dhcp
And disabled the Network manager because it was erasing the resolv.conf file each time:
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
edited Mar 20 at 7:28
answered Mar 19 at 13:54
E235E235
1134
1134
add a comment |
add a comment |
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.
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%2faskubuntu.com%2fquestions%2f1126907%2fcant-start-virhs-network-iptables-no-chain-target-match-by-that-name%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

Hello and welcome to AskUbuntu! Can you edit your question and post the output of
iptables -L -t filter?– Mr Shunz
Mar 19 at 11:06
@MrShunz The answer is updated
– E235
Mar 19 at 11:37
Maybe it because I don't have interface named
virbr0?– E235
Mar 19 at 12:13