Proxmox vps container connection problems Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Come Celebrate our 10 Year Anniversary!bond0 and xen = crashvirtualbox get network access from host (vista/xp) to guest (ubuntu) - NAT?Static virtual IP in debian 6.0.4Centos multiple NICs routing issueSet up Wheezy SubnetsUsing my IPs on OVH server via GREqemu, kvm: Guest: No DHCPOFFERS receivedProxmox additional Ip with Port Forwardingpackets transmitted, 0 received (no internet connection) on centos 6.6 vpsHow to set the dns on lxc containers staticly?

When were vectors invented?

What's the meaning of 間時肆拾貳 at a car parking sign

How to answer "Have you ever been terminated?"

Seeking colloquialism for “just because”

How to tell that you are a giant?

Why are Kinder Surprise Eggs illegal in the USA?

How can I make names more distinctive without making them longer?

Is it fair for a professor to grade us on the possession of past papers?

Compare a given version number in the form major.minor.build.patch and see if one is less than the other

How does the particle を relate to the verb 行く in the structure「A を + B に行く」?

Why is "Consequences inflicted." not a sentence?

First console to have temporary backward compatibility

Using et al. for a last / senior author rather than for a first author

English words in a non-english sci-fi novel

Understanding Ceva's Theorem

Is it true that "carbohydrates are of no use for the basal metabolic need"?

How to call a function with default parameter through a pointer to function that is the return of another function?

Why light coming from distant stars is not discrete?

3 doors, three guards, one stone

Should I use a zero-interest credit card for a large one-time purchase?

Can an alien society believe that their star system is the universe?

Why do people hide their license plates in the EU?

Generate an RGB colour grid

Can inflation occur in a positive-sum game currency system such as the Stack Exchange reputation system?



Proxmox vps container connection problems



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!bond0 and xen = crashvirtualbox get network access from host (vista/xp) to guest (ubuntu) - NAT?Static virtual IP in debian 6.0.4Centos multiple NICs routing issueSet up Wheezy SubnetsUsing my IPs on OVH server via GREqemu, kvm: Guest: No DHCPOFFERS receivedProxmox additional Ip with Port Forwardingpackets transmitted, 0 received (no internet connection) on centos 6.6 vpsHow to set the dns on lxc containers staticly?



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








2















I have Proxmox on my node server which have ip:5.189.190.*
and I created openvz container on an ip : 213.136.87.* and installed centos 6 on it



The problem:
Cann't connect to container ssh directly
Can't open apache server centos welcome page
When I enter container from the node can't ping any sites or wget any url but I can connect 127.0.0.1 and the main node ip



My Configuration:
container /etc/resolv.conf



nameserver 8.8.8.8
nameserver 8.8.4.4


container /etc/sysconfig/network-scripts/ifcfg-venet0



DEVICE=venet0
BOOTPROTO=static
ONBOOT=yes
IPADDR=213.136.87.*
NETMASK=255.255.255.0
BROADCAST=213.136.87.*
IPV6INIT="yes"


container /etc/sysconfig/network-scripts/ifcfg-venet0



DEVICE=venet0:0
ONBOOT=yes
IPADDR=213.136.87.*
NETMASK=255.255.255.0


node /etc/network/interfaces



# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
address 5.189.190.*
netmask 255.255.255.0
gateway 5.189.190.*
bridge_ports eth0
bridge_stp off
bridge_fd 0


node /etc/resolv.conf
having DC nameservers correctly



container ping result:



# ping google.com -c 3
ping: unknown host google.com


container traceroute result:



# traceroute google.com
google.com: Temporary failure in name resolution
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)


node ping result:



# ping google.com -c 3
PING google.com (74.125.29.139) 56(84) bytes of data.
64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=1 ttl=41 time=110 ms
64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=2 ttl=41 time=110 ms
64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=3 ttl=41 time=110 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 110.450/110.462/110.474/0.383 ms


node traceroute result:



# traceroute google.com
traceroute to google.com (74.125.29.139), 30 hops max, 60 byte packets
1 ip-1-90-136-213.static.contabo.net (213.136.90.1) 0.506 ms 0.517 ms 0.513 ms
2 ffm-b11-link.telia.net (62.115.36.237) 0.493 ms 0.491 ms 0.484 ms
3 hbg-b1-link.telia.net (62.115.139.164) 15.379 ms 15.393 ms 15.384 ms
4 hbg-bb4-link.telia.net (213.155.135.88) 16.048 ms hbg-bb4-link.telia.net (213.155.135.86) 15.419 ms hbg-bb4-link.telia.net (213.155.135.84) 15.456 ms
5 nyk-bb1-link.telia.net (80.91.247.127) 96.568 ms nyk-bb2-link.telia.net (80.91.247.123) 107.638 ms nyk-bb1-link.telia.net (80.91.247.129) 96.582 ms
6 nyk-b6-link.telia.net (213.155.130.251) 105.478 ms 105.470 ms nyk-b6-link.telia.net (80.91.254.32) 101.005 ms
7 google-ic-303645-nyk-b6.c.telia.net (213.248.78.250) 101.235 ms 105.746 ms 105.719 ms
8 209.85.248.242 (209.85.248.242) 101.694 ms 106.213 ms 106.250 ms
9 209.85.249.212 (209.85.249.212) 101.225 ms 209.85.246.4 (209.85.246.4) 101.597 ms 209.85.252.242 (209.85.252.242) 101.179 ms
10 209.85.249.11 (209.85.249.11) 102.247 ms 112.917 ms 72.14.239.93 (72.14.239.93) 97.931 ms
11 64.233.174.9 (64.233.174.9) 104.733 ms 66.249.95.229 (66.249.95.229) 109.232 ms 66.249.95.231 (66.249.95.231) 106.086 ms
12 72.14.234.53 (72.14.234.53) 106.179 ms 72.14.238.73 (72.14.238.73) 110.471 ms 72.14.234.53 (72.14.234.53) 106.170 ms
13 * * *
14 qg-in-f139.1e100.net (74.125.29.139) 110.479 ms 110.656 ms 106.154 ms


Any ideas will be welcomed



Thanks










share|improve this question




























    2















    I have Proxmox on my node server which have ip:5.189.190.*
    and I created openvz container on an ip : 213.136.87.* and installed centos 6 on it



    The problem:
    Cann't connect to container ssh directly
    Can't open apache server centos welcome page
    When I enter container from the node can't ping any sites or wget any url but I can connect 127.0.0.1 and the main node ip



    My Configuration:
    container /etc/resolv.conf



    nameserver 8.8.8.8
    nameserver 8.8.4.4


    container /etc/sysconfig/network-scripts/ifcfg-venet0



    DEVICE=venet0
    BOOTPROTO=static
    ONBOOT=yes
    IPADDR=213.136.87.*
    NETMASK=255.255.255.0
    BROADCAST=213.136.87.*
    IPV6INIT="yes"


    container /etc/sysconfig/network-scripts/ifcfg-venet0



    DEVICE=venet0:0
    ONBOOT=yes
    IPADDR=213.136.87.*
    NETMASK=255.255.255.0


    node /etc/network/interfaces



    # network interface settings
    auto lo
    iface lo inet loopback

    auto eth0
    iface eth0 inet manual

    auto vmbr0
    iface vmbr0 inet static
    address 5.189.190.*
    netmask 255.255.255.0
    gateway 5.189.190.*
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0


    node /etc/resolv.conf
    having DC nameservers correctly



    container ping result:



    # ping google.com -c 3
    ping: unknown host google.com


    container traceroute result:



    # traceroute google.com
    google.com: Temporary failure in name resolution
    Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)


    node ping result:



    # ping google.com -c 3
    PING google.com (74.125.29.139) 56(84) bytes of data.
    64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=1 ttl=41 time=110 ms
    64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=2 ttl=41 time=110 ms
    64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=3 ttl=41 time=110 ms

    --- google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2000ms
    rtt min/avg/max/mdev = 110.450/110.462/110.474/0.383 ms


    node traceroute result:



    # traceroute google.com
    traceroute to google.com (74.125.29.139), 30 hops max, 60 byte packets
    1 ip-1-90-136-213.static.contabo.net (213.136.90.1) 0.506 ms 0.517 ms 0.513 ms
    2 ffm-b11-link.telia.net (62.115.36.237) 0.493 ms 0.491 ms 0.484 ms
    3 hbg-b1-link.telia.net (62.115.139.164) 15.379 ms 15.393 ms 15.384 ms
    4 hbg-bb4-link.telia.net (213.155.135.88) 16.048 ms hbg-bb4-link.telia.net (213.155.135.86) 15.419 ms hbg-bb4-link.telia.net (213.155.135.84) 15.456 ms
    5 nyk-bb1-link.telia.net (80.91.247.127) 96.568 ms nyk-bb2-link.telia.net (80.91.247.123) 107.638 ms nyk-bb1-link.telia.net (80.91.247.129) 96.582 ms
    6 nyk-b6-link.telia.net (213.155.130.251) 105.478 ms 105.470 ms nyk-b6-link.telia.net (80.91.254.32) 101.005 ms
    7 google-ic-303645-nyk-b6.c.telia.net (213.248.78.250) 101.235 ms 105.746 ms 105.719 ms
    8 209.85.248.242 (209.85.248.242) 101.694 ms 106.213 ms 106.250 ms
    9 209.85.249.212 (209.85.249.212) 101.225 ms 209.85.246.4 (209.85.246.4) 101.597 ms 209.85.252.242 (209.85.252.242) 101.179 ms
    10 209.85.249.11 (209.85.249.11) 102.247 ms 112.917 ms 72.14.239.93 (72.14.239.93) 97.931 ms
    11 64.233.174.9 (64.233.174.9) 104.733 ms 66.249.95.229 (66.249.95.229) 109.232 ms 66.249.95.231 (66.249.95.231) 106.086 ms
    12 72.14.234.53 (72.14.234.53) 106.179 ms 72.14.238.73 (72.14.238.73) 110.471 ms 72.14.234.53 (72.14.234.53) 106.170 ms
    13 * * *
    14 qg-in-f139.1e100.net (74.125.29.139) 110.479 ms 110.656 ms 106.154 ms


    Any ideas will be welcomed



    Thanks










    share|improve this question
























      2












      2








      2








      I have Proxmox on my node server which have ip:5.189.190.*
      and I created openvz container on an ip : 213.136.87.* and installed centos 6 on it



      The problem:
      Cann't connect to container ssh directly
      Can't open apache server centos welcome page
      When I enter container from the node can't ping any sites or wget any url but I can connect 127.0.0.1 and the main node ip



      My Configuration:
      container /etc/resolv.conf



      nameserver 8.8.8.8
      nameserver 8.8.4.4


      container /etc/sysconfig/network-scripts/ifcfg-venet0



      DEVICE=venet0
      BOOTPROTO=static
      ONBOOT=yes
      IPADDR=213.136.87.*
      NETMASK=255.255.255.0
      BROADCAST=213.136.87.*
      IPV6INIT="yes"


      container /etc/sysconfig/network-scripts/ifcfg-venet0



      DEVICE=venet0:0
      ONBOOT=yes
      IPADDR=213.136.87.*
      NETMASK=255.255.255.0


      node /etc/network/interfaces



      # network interface settings
      auto lo
      iface lo inet loopback

      auto eth0
      iface eth0 inet manual

      auto vmbr0
      iface vmbr0 inet static
      address 5.189.190.*
      netmask 255.255.255.0
      gateway 5.189.190.*
      bridge_ports eth0
      bridge_stp off
      bridge_fd 0


      node /etc/resolv.conf
      having DC nameservers correctly



      container ping result:



      # ping google.com -c 3
      ping: unknown host google.com


      container traceroute result:



      # traceroute google.com
      google.com: Temporary failure in name resolution
      Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)


      node ping result:



      # ping google.com -c 3
      PING google.com (74.125.29.139) 56(84) bytes of data.
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=1 ttl=41 time=110 ms
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=2 ttl=41 time=110 ms
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=3 ttl=41 time=110 ms

      --- google.com ping statistics ---
      3 packets transmitted, 3 received, 0% packet loss, time 2000ms
      rtt min/avg/max/mdev = 110.450/110.462/110.474/0.383 ms


      node traceroute result:



      # traceroute google.com
      traceroute to google.com (74.125.29.139), 30 hops max, 60 byte packets
      1 ip-1-90-136-213.static.contabo.net (213.136.90.1) 0.506 ms 0.517 ms 0.513 ms
      2 ffm-b11-link.telia.net (62.115.36.237) 0.493 ms 0.491 ms 0.484 ms
      3 hbg-b1-link.telia.net (62.115.139.164) 15.379 ms 15.393 ms 15.384 ms
      4 hbg-bb4-link.telia.net (213.155.135.88) 16.048 ms hbg-bb4-link.telia.net (213.155.135.86) 15.419 ms hbg-bb4-link.telia.net (213.155.135.84) 15.456 ms
      5 nyk-bb1-link.telia.net (80.91.247.127) 96.568 ms nyk-bb2-link.telia.net (80.91.247.123) 107.638 ms nyk-bb1-link.telia.net (80.91.247.129) 96.582 ms
      6 nyk-b6-link.telia.net (213.155.130.251) 105.478 ms 105.470 ms nyk-b6-link.telia.net (80.91.254.32) 101.005 ms
      7 google-ic-303645-nyk-b6.c.telia.net (213.248.78.250) 101.235 ms 105.746 ms 105.719 ms
      8 209.85.248.242 (209.85.248.242) 101.694 ms 106.213 ms 106.250 ms
      9 209.85.249.212 (209.85.249.212) 101.225 ms 209.85.246.4 (209.85.246.4) 101.597 ms 209.85.252.242 (209.85.252.242) 101.179 ms
      10 209.85.249.11 (209.85.249.11) 102.247 ms 112.917 ms 72.14.239.93 (72.14.239.93) 97.931 ms
      11 64.233.174.9 (64.233.174.9) 104.733 ms 66.249.95.229 (66.249.95.229) 109.232 ms 66.249.95.231 (66.249.95.231) 106.086 ms
      12 72.14.234.53 (72.14.234.53) 106.179 ms 72.14.238.73 (72.14.238.73) 110.471 ms 72.14.234.53 (72.14.234.53) 106.170 ms
      13 * * *
      14 qg-in-f139.1e100.net (74.125.29.139) 110.479 ms 110.656 ms 106.154 ms


      Any ideas will be welcomed



      Thanks










      share|improve this question














      I have Proxmox on my node server which have ip:5.189.190.*
      and I created openvz container on an ip : 213.136.87.* and installed centos 6 on it



      The problem:
      Cann't connect to container ssh directly
      Can't open apache server centos welcome page
      When I enter container from the node can't ping any sites or wget any url but I can connect 127.0.0.1 and the main node ip



      My Configuration:
      container /etc/resolv.conf



      nameserver 8.8.8.8
      nameserver 8.8.4.4


      container /etc/sysconfig/network-scripts/ifcfg-venet0



      DEVICE=venet0
      BOOTPROTO=static
      ONBOOT=yes
      IPADDR=213.136.87.*
      NETMASK=255.255.255.0
      BROADCAST=213.136.87.*
      IPV6INIT="yes"


      container /etc/sysconfig/network-scripts/ifcfg-venet0



      DEVICE=venet0:0
      ONBOOT=yes
      IPADDR=213.136.87.*
      NETMASK=255.255.255.0


      node /etc/network/interfaces



      # network interface settings
      auto lo
      iface lo inet loopback

      auto eth0
      iface eth0 inet manual

      auto vmbr0
      iface vmbr0 inet static
      address 5.189.190.*
      netmask 255.255.255.0
      gateway 5.189.190.*
      bridge_ports eth0
      bridge_stp off
      bridge_fd 0


      node /etc/resolv.conf
      having DC nameservers correctly



      container ping result:



      # ping google.com -c 3
      ping: unknown host google.com


      container traceroute result:



      # traceroute google.com
      google.com: Temporary failure in name resolution
      Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)


      node ping result:



      # ping google.com -c 3
      PING google.com (74.125.29.139) 56(84) bytes of data.
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=1 ttl=41 time=110 ms
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=2 ttl=41 time=110 ms
      64 bytes from qg-in-f139.1e100.net (74.125.29.139): icmp_req=3 ttl=41 time=110 ms

      --- google.com ping statistics ---
      3 packets transmitted, 3 received, 0% packet loss, time 2000ms
      rtt min/avg/max/mdev = 110.450/110.462/110.474/0.383 ms


      node traceroute result:



      # traceroute google.com
      traceroute to google.com (74.125.29.139), 30 hops max, 60 byte packets
      1 ip-1-90-136-213.static.contabo.net (213.136.90.1) 0.506 ms 0.517 ms 0.513 ms
      2 ffm-b11-link.telia.net (62.115.36.237) 0.493 ms 0.491 ms 0.484 ms
      3 hbg-b1-link.telia.net (62.115.139.164) 15.379 ms 15.393 ms 15.384 ms
      4 hbg-bb4-link.telia.net (213.155.135.88) 16.048 ms hbg-bb4-link.telia.net (213.155.135.86) 15.419 ms hbg-bb4-link.telia.net (213.155.135.84) 15.456 ms
      5 nyk-bb1-link.telia.net (80.91.247.127) 96.568 ms nyk-bb2-link.telia.net (80.91.247.123) 107.638 ms nyk-bb1-link.telia.net (80.91.247.129) 96.582 ms
      6 nyk-b6-link.telia.net (213.155.130.251) 105.478 ms 105.470 ms nyk-b6-link.telia.net (80.91.254.32) 101.005 ms
      7 google-ic-303645-nyk-b6.c.telia.net (213.248.78.250) 101.235 ms 105.746 ms 105.719 ms
      8 209.85.248.242 (209.85.248.242) 101.694 ms 106.213 ms 106.250 ms
      9 209.85.249.212 (209.85.249.212) 101.225 ms 209.85.246.4 (209.85.246.4) 101.597 ms 209.85.252.242 (209.85.252.242) 101.179 ms
      10 209.85.249.11 (209.85.249.11) 102.247 ms 112.917 ms 72.14.239.93 (72.14.239.93) 97.931 ms
      11 64.233.174.9 (64.233.174.9) 104.733 ms 66.249.95.229 (66.249.95.229) 109.232 ms 66.249.95.231 (66.249.95.231) 106.086 ms
      12 72.14.234.53 (72.14.234.53) 106.179 ms 72.14.238.73 (72.14.238.73) 110.471 ms 72.14.234.53 (72.14.234.53) 106.170 ms
      13 * * *
      14 qg-in-f139.1e100.net (74.125.29.139) 110.479 ms 110.656 ms 106.154 ms


      Any ideas will be welcomed



      Thanks







      networking domain-name-system openvz proxmox






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 20 '14 at 7:51









      MelloMello

      1112




      1112




















          1 Answer
          1






          active

          oldest

          votes


















          0














          Try something like this.
          On node add static routing for container IP address. Edit /etc/network/interfaces and add for vmbr0 interface:



          post-up route add -host $containerIP gw $nodeIP
          pre-down route del -host $containerIP gw $nodeIP


          On container, add following line to /etc/sysconfig/network-scripts/ifcfg-venet0



          GATEWAY=$nodeIP
          SCOPE="peer $nodeIP"


          Also create file /etc/sysconfig/network-scripts/route-venet0 with content:



          0.0.0.0/0 via $nodeIP


          Restart network on node and on container, check if it works.



          I use above configuration for several of my KVM hosts and VMs where IP on the VM is in different subnet than IP of the node.






          share|improve this answer

























          • netmask 255.255.255.255 or netmask 255.255.255.0 ?

            – Mello
            Sep 20 '14 at 11:52











          • My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

            – Piotr
            Sep 20 '14 at 13:22











          • I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

            – Mello
            Sep 20 '14 at 13:27












          • in few words, your containers has public ips and your nodes private address?

            – c4f4t0r
            Sep 20 '14 at 21:36











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          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
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f629997%2fproxmox-vps-container-connection-problems%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









          0














          Try something like this.
          On node add static routing for container IP address. Edit /etc/network/interfaces and add for vmbr0 interface:



          post-up route add -host $containerIP gw $nodeIP
          pre-down route del -host $containerIP gw $nodeIP


          On container, add following line to /etc/sysconfig/network-scripts/ifcfg-venet0



          GATEWAY=$nodeIP
          SCOPE="peer $nodeIP"


          Also create file /etc/sysconfig/network-scripts/route-venet0 with content:



          0.0.0.0/0 via $nodeIP


          Restart network on node and on container, check if it works.



          I use above configuration for several of my KVM hosts and VMs where IP on the VM is in different subnet than IP of the node.






          share|improve this answer

























          • netmask 255.255.255.255 or netmask 255.255.255.0 ?

            – Mello
            Sep 20 '14 at 11:52











          • My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

            – Piotr
            Sep 20 '14 at 13:22











          • I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

            – Mello
            Sep 20 '14 at 13:27












          • in few words, your containers has public ips and your nodes private address?

            – c4f4t0r
            Sep 20 '14 at 21:36















          0














          Try something like this.
          On node add static routing for container IP address. Edit /etc/network/interfaces and add for vmbr0 interface:



          post-up route add -host $containerIP gw $nodeIP
          pre-down route del -host $containerIP gw $nodeIP


          On container, add following line to /etc/sysconfig/network-scripts/ifcfg-venet0



          GATEWAY=$nodeIP
          SCOPE="peer $nodeIP"


          Also create file /etc/sysconfig/network-scripts/route-venet0 with content:



          0.0.0.0/0 via $nodeIP


          Restart network on node and on container, check if it works.



          I use above configuration for several of my KVM hosts and VMs where IP on the VM is in different subnet than IP of the node.






          share|improve this answer

























          • netmask 255.255.255.255 or netmask 255.255.255.0 ?

            – Mello
            Sep 20 '14 at 11:52











          • My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

            – Piotr
            Sep 20 '14 at 13:22











          • I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

            – Mello
            Sep 20 '14 at 13:27












          • in few words, your containers has public ips and your nodes private address?

            – c4f4t0r
            Sep 20 '14 at 21:36













          0












          0








          0







          Try something like this.
          On node add static routing for container IP address. Edit /etc/network/interfaces and add for vmbr0 interface:



          post-up route add -host $containerIP gw $nodeIP
          pre-down route del -host $containerIP gw $nodeIP


          On container, add following line to /etc/sysconfig/network-scripts/ifcfg-venet0



          GATEWAY=$nodeIP
          SCOPE="peer $nodeIP"


          Also create file /etc/sysconfig/network-scripts/route-venet0 with content:



          0.0.0.0/0 via $nodeIP


          Restart network on node and on container, check if it works.



          I use above configuration for several of my KVM hosts and VMs where IP on the VM is in different subnet than IP of the node.






          share|improve this answer















          Try something like this.
          On node add static routing for container IP address. Edit /etc/network/interfaces and add for vmbr0 interface:



          post-up route add -host $containerIP gw $nodeIP
          pre-down route del -host $containerIP gw $nodeIP


          On container, add following line to /etc/sysconfig/network-scripts/ifcfg-venet0



          GATEWAY=$nodeIP
          SCOPE="peer $nodeIP"


          Also create file /etc/sysconfig/network-scripts/route-venet0 with content:



          0.0.0.0/0 via $nodeIP


          Restart network on node and on container, check if it works.



          I use above configuration for several of my KVM hosts and VMs where IP on the VM is in different subnet than IP of the node.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Sep 20 '14 at 13:21

























          answered Sep 20 '14 at 9:39









          PiotrPiotr

          781312




          781312












          • netmask 255.255.255.255 or netmask 255.255.255.0 ?

            – Mello
            Sep 20 '14 at 11:52











          • My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

            – Piotr
            Sep 20 '14 at 13:22











          • I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

            – Mello
            Sep 20 '14 at 13:27












          • in few words, your containers has public ips and your nodes private address?

            – c4f4t0r
            Sep 20 '14 at 21:36

















          • netmask 255.255.255.255 or netmask 255.255.255.0 ?

            – Mello
            Sep 20 '14 at 11:52











          • My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

            – Piotr
            Sep 20 '14 at 13:22











          • I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

            – Mello
            Sep 20 '14 at 13:27












          • in few words, your containers has public ips and your nodes private address?

            – c4f4t0r
            Sep 20 '14 at 21:36
















          netmask 255.255.255.255 or netmask 255.255.255.0 ?

          – Mello
          Sep 20 '14 at 11:52





          netmask 255.255.255.255 or netmask 255.255.255.0 ?

          – Mello
          Sep 20 '14 at 11:52













          My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

          – Piotr
          Sep 20 '14 at 13:22





          My bad, 'network' statement shouldn't be there as you are adding static route for single host. I've just edited my answer.

          – Piotr
          Sep 20 '14 at 13:22













          I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

          – Mello
          Sep 20 '14 at 13:27






          I appreciate your help. but it doesn't work with error Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning). Reconfiguring network interfaces... Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds). RTNETLINK answers: File exists vzifup-post ERROR: Unable to add route ip route add 213.136.87.221 dev venet0 run-parts: /etc/network/if-up.d/vzifup-post exited with return code 34 On restart network on node

          – Mello
          Sep 20 '14 at 13:27














          in few words, your containers has public ips and your nodes private address?

          – c4f4t0r
          Sep 20 '14 at 21:36





          in few words, your containers has public ips and your nodes private address?

          – c4f4t0r
          Sep 20 '14 at 21:36

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • 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%2fserverfault.com%2fquestions%2f629997%2fproxmox-vps-container-connection-problems%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

          Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

          Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

          What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company