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

          Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

          Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

          Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020