Traffic from OpenVZ host to container gets redirected to gateway The 2019 Stack Overflow...

How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?

Can the DM override racial traits?

What is the padding with red substance inside of steak packaging?

Didn't get enough time to take a Coding Test - what to do now?

Can the Right Ascension and Argument of Perigee of a spacecraft's orbit keep varying by themselves with time?

Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)

Why can't devices on different VLANs, but on the same subnet, communicate?

Can each chord in a progression create its own key?

Accepted by European university, rejected by all American ones I applied to? Possible reasons?

Can withdrawing asylum be illegal?

Presidential Pardon

How do spell lists change if the party levels up without taking a long rest?

Why can't wing-mounted spoilers be used to steepen approaches?

How to support a colleague who finds meetings extremely tiring?

1960s short story making fun of James Bond-style spy fiction

Is there a writing software that you can sort scenes like slides in PowerPoint?

Sort list of array linked objects by keys and values

Why doesn't a hydraulic lever violate conservation of energy?

What force causes entropy to increase?

Are there continuous functions who are the same in an interval but differ in at least one other point?

Is every episode of "Where are my Pants?" identical?

For what reasons would an animal species NOT cross a *horizontal* land bridge?

Word to describe a time interval

What happens to a Warlock's expended Spell Slots when they gain a Level?



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;
}







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









share|improve this question































    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









    share|improve this question



























      0












      0








      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









      share|improve this question
















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 3 hours ago









      Rui F Ribeiro

      42k1483142




      42k1483142










      asked 5 hours ago









      Aleksandr BlekhAleksandr Blekh

      1137




      1137






















          1 Answer
          1






          active

          oldest

          votes


















          2














          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.






          share|improve this answer
























          • 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
            5 hours ago














          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          2














          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.






          share|improve this answer
























          • 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
            5 hours ago


















          2














          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.






          share|improve this answer
























          • 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
            5 hours ago
















          2












          2








          2







          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.






          share|improve this answer













          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 5 hours ago









          GracefulRestartGracefulRestart

          1,31437




          1,31437













          • 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
            5 hours ago





















          • 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
            5 hours ago



















          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
          5 hours ago







          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
          5 hours ago




















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

          Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

          Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m