Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 171704

Host has no route to container after update to Proxmox 4

$
0
0
I did the migration following the instructions in the Proxmox Wiki (Convert OpenVZ to LXC).
So far everything looks good. The restored (OpenVZ->LXC) container is running and has Internet connectivity.
However I'm nomore able to connect from the host to the guest.

The config is:
Code:

$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 188.40.101.72
        netmask 255.255.255.192
        gateway 188.40.101.65
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

/etc/network/interfaces has not changed with the update.

Container network config:
Code:

pct set 126 -net0 name=eth0,bridge=vmbr0,ip=192.168.2.126/32
With the container running, that's the output of ifconfig and route:
Code:

$ ifconfig
eth0      Link encap:Ethernet  HWaddr 40:61:86:2b:87:c6 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32308 errors:0 dropped:114 overruns:0 frame:0
          TX packets:25776 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15543141 (14.8 MiB)  TX bytes:8091218 (7.7 MiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:10181 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3031823 (2.8 MiB)  TX bytes:3031823 (2.8 MiB)

veth126i0 Link encap:Ethernet  HWaddr fe:51:8d:c1:8f:0f 
          inet6 addr: fe80::fc51:8dff:fec1:8f0f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:490 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:812 (812.0 B)  TX bytes:31496 (30.7 KiB)

vmbr0    Link encap:Ethernet  HWaddr 40:61:86:2b:87:c6 
          inet addr:188.40.101.72  Bcast:188.40.101.127  Mask:255.255.255.192
          inet6 addr: fe80::4261:86ff:fe2b:87c6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24958 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14808740 (14.1 MiB)  TX bytes:8036982 (7.6 MiB)

$ route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
default        static.65.101.4 0.0.0.0        UG    0      0        0 vmbr0
188.40.101.64  *              255.255.255.192 U    0      0        0 vmbr0

What I note here is that there's no route to the container's IP. With Proxmox 3, I had entried like this (automatically generated):
Code:

$ route
192.168.2.126  *              255.255.255.255 UH    0      0        0 venet0

What's missing here?

Viewing all articles
Browse latest Browse all 171704

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>