Traffic from OpenVZ host to container gets redirected to gateway The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsUsing ip addr instead of ifconfig reports “RTNETLINK answers: File exists” on DebianIs it possible for a OpenVZ container to interact with a MySQL database on the host?Setting up OpenVZ container private areaLinux server able to wget but not able to pingOpenvz summary of IO for each containersystemd-timesyncd bug in OpenVZ containerDirect connection Centos7 (loadbalance) to QNAP (trunk)Openvpn issues with routing and config pushingvirtuozzo openvz centos 7 container network not start after updateConfiguring Linux Mint as a Gateway
What was the last x86 CPU that did not have the x87 floating-point unit built in?
What information about me do stores get via my credit card?
Typeface like Times New Roman but with "tied" percent sign
"... to apply for a visa" or "... and applied for a visa"?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
What are these Gizmos at Izaña Atmospheric Research Center in Spain?
How many people can fit inside Mordenkainen's Magnificent Mansion?
How did passengers keep warm on sail ships?
how can a perfect fourth interval be considered either consonant or dissonant?
Hiding Certain Lines on Table
Did the new image of black hole confirm the general theory of relativity?
How to split app screen on my Mac?
Why does the Event Horizon Telescope (EHT) not include telescopes from Africa, Asia or Australia?
does high air pressure throw off wheel balance?
rotate text in posterbox
How to delete random line from file using Unix command?
Sort a list of pairs representing an acyclic, partial automorphism
What's the point in a preamp?
Finding the path in a graph from A to B then back to A with a minimum of shared edges
Match Roman Numerals
Why can't devices on different VLANs, but on the same subnet, communicate?
Am I ethically obligated to go into work on an off day if the reason is sudden?
How can I define good in a religion that claims no moral authority?
Do working physicists consider Newtonian mechanics to be "falsified"?
Traffic from OpenVZ host to container gets redirected to gateway
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election ResultsUsing ip addr instead of ifconfig reports “RTNETLINK answers: File exists” on DebianIs it possible for a OpenVZ container to interact with a MySQL database on the host?Setting up OpenVZ container private areaLinux server able to wget but not able to pingOpenvz summary of IO for each containersystemd-timesyncd bug in OpenVZ containerDirect connection Centos7 (loadbalance) to QNAP (trunk)Openvpn issues with routing and config pushingvirtuozzo openvz centos 7 container network not start after updateConfiguring Linux Mint as a Gateway
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
An OpenVZ host (RHEL 6) is running Debian-based containers. The problem is that network traffic, instead of being routed to a relevant container (10.10.104.1
) via venet0
interface, gets routed to the host network's default gateway (143.215.76.129
). At the same time, traffic to the 192.168.x.x network does not get redirected to the gateway. Relevant output below.
# traceroute 10.10.104.1
traceroute to 10.10.104.1 (10.10.104.1), 30 hops max, 60 byte packets
1 143.215.76.129 (143.215.76.129) 1.349 ms 1.314 ms 1.280 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 *^C
# traceroute 192.168.104.32
traceroute to 192.168.104.32 (192.168.104.32), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth1
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1004 0 0 eth2
0.0.0.0 143.215.76.129 0.0.0.0 UG 0 0 0 eth0
networking openvz
add a comment |
An OpenVZ host (RHEL 6) is running Debian-based containers. The problem is that network traffic, instead of being routed to a relevant container (10.10.104.1
) via venet0
interface, gets routed to the host network's default gateway (143.215.76.129
). At the same time, traffic to the 192.168.x.x network does not get redirected to the gateway. Relevant output below.
# traceroute 10.10.104.1
traceroute to 10.10.104.1 (10.10.104.1), 30 hops max, 60 byte packets
1 143.215.76.129 (143.215.76.129) 1.349 ms 1.314 ms 1.280 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 *^C
# traceroute 192.168.104.32
traceroute to 192.168.104.32 (192.168.104.32), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth1
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1004 0 0 eth2
0.0.0.0 143.215.76.129 0.0.0.0 UG 0 0 0 eth0
networking openvz
add a comment |
An OpenVZ host (RHEL 6) is running Debian-based containers. The problem is that network traffic, instead of being routed to a relevant container (10.10.104.1
) via venet0
interface, gets routed to the host network's default gateway (143.215.76.129
). At the same time, traffic to the 192.168.x.x network does not get redirected to the gateway. Relevant output below.
# traceroute 10.10.104.1
traceroute to 10.10.104.1 (10.10.104.1), 30 hops max, 60 byte packets
1 143.215.76.129 (143.215.76.129) 1.349 ms 1.314 ms 1.280 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 *^C
# traceroute 192.168.104.32
traceroute to 192.168.104.32 (192.168.104.32), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth1
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1004 0 0 eth2
0.0.0.0 143.215.76.129 0.0.0.0 UG 0 0 0 eth0
networking openvz
An OpenVZ host (RHEL 6) is running Debian-based containers. The problem is that network traffic, instead of being routed to a relevant container (10.10.104.1
) via venet0
interface, gets routed to the host network's default gateway (143.215.76.129
). At the same time, traffic to the 192.168.x.x network does not get redirected to the gateway. Relevant output below.
# traceroute 10.10.104.1
traceroute to 10.10.104.1 (10.10.104.1), 30 hops max, 60 byte packets
1 143.215.76.129 (143.215.76.129) 1.349 ms 1.314 ms 1.280 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 *^C
# traceroute 192.168.104.32
traceroute to 192.168.104.32 (192.168.104.32), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.104.1 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth0
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth1
143.215.76.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1004 0 0 eth2
0.0.0.0 143.215.76.129 0.0.0.0 UG 0 0 0 eth0
networking openvz
networking openvz
edited yesterday
Rui F Ribeiro
42.1k1483142
42.1k1483142
asked yesterday
Aleksandr BlekhAleksandr Blekh
1137
1137
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The venet0
interface will always be routed through the host network, that is the design of the venet
network on OpenVZ.
Since it seems you want to route traffic on the host to one of your containers, then you will need to make a proper virtual ethernet device which OpenVZ refers to as veth
. This gives your container's network interface a MAC address and other requirements for proper packet routing.
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize avenet
-only configuration (not aveth
-based one). I will get in touch with relevant people and keep you posted.
– Aleksandr Blekh
yesterday
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%2f512190%2ftraffic-from-openvz-host-to-container-gets-redirected-to-gateway%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
The venet0
interface will always be routed through the host network, that is the design of the venet
network on OpenVZ.
Since it seems you want to route traffic on the host to one of your containers, then you will need to make a proper virtual ethernet device which OpenVZ refers to as veth
. This gives your container's network interface a MAC address and other requirements for proper packet routing.
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize avenet
-only configuration (not aveth
-based one). I will get in touch with relevant people and keep you posted.
– Aleksandr Blekh
yesterday
add a comment |
The venet0
interface will always be routed through the host network, that is the design of the venet
network on OpenVZ.
Since it seems you want to route traffic on the host to one of your containers, then you will need to make a proper virtual ethernet device which OpenVZ refers to as veth
. This gives your container's network interface a MAC address and other requirements for proper packet routing.
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize avenet
-only configuration (not aveth
-based one). I will get in touch with relevant people and keep you posted.
– Aleksandr Blekh
yesterday
add a comment |
The venet0
interface will always be routed through the host network, that is the design of the venet
network on OpenVZ.
Since it seems you want to route traffic on the host to one of your containers, then you will need to make a proper virtual ethernet device which OpenVZ refers to as veth
. This gives your container's network interface a MAC address and other requirements for proper packet routing.
The venet0
interface will always be routed through the host network, that is the design of the venet
network on OpenVZ.
Since it seems you want to route traffic on the host to one of your containers, then you will need to make a proper virtual ethernet device which OpenVZ refers to as veth
. This gives your container's network interface a MAC address and other requirements for proper packet routing.
answered yesterday
GracefulRestartGracefulRestart
1,32937
1,32937
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize avenet
-only configuration (not aveth
-based one). I will get in touch with relevant people and keep you posted.
– Aleksandr Blekh
yesterday
add a comment |
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize avenet
-only configuration (not aveth
-based one). I will get in touch with relevant people and keep you posted.
– Aleksandr Blekh
yesterday
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize a
venet
-only configuration (not a veth
-based one). I will get in touch with relevant people and keep you posted.– Aleksandr Blekh
yesterday
Much appreciate your prompt and helpful advice. However, based on my knowledge, the (overarching) system that we use is designed to utilize a
venet
-only configuration (not a veth
-based one). I will get in touch with relevant people and keep you posted.– Aleksandr Blekh
yesterday
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%2f512190%2ftraffic-from-openvz-host-to-container-gets-redirected-to-gateway%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
-networking, openvz