OpenVZ Forum


Home » General » Support » Networking problem after physical to VE
Networking problem after physical to VE [message #34540] Fri, 16 January 2009 08:49 Go to next message
dignus is currently offline  dignus
Messages: 6
Registered: March 2007
Junior Member
Hey there,

I just did another physical-to-VE procedure. Done it before with no problems, but this one gives me a headache.

Some relevant lines:

[root@hw28101 private]# cat /etc/vz/conf/28999.conf
# Configuration file generated by vzsplit for 1 VEs
# on HN with total amount of physical mem 4011 Mb
# low memory 4011 Mb, swap size 8095 Mb, Max treads 8000
# Resourse commit level 0:
# Free resource distribution. Any parameters may be increased
# Primary parameters
NUMPROC="20538:20538"
AVNUMPROC="10269:10269"
NUMTCPSOCK="20538:20538"
NUMOTHERSOCK="20538:20538"
VMGUARPAGES="616143:9223372036854775807"

# Secondary parameters
KMEMSIZE="841240576:925364633"
TCPSNDBUF="196289877:280413525"
TCPRCVBUF="196289877:280413525"
OTHERSOCKBUF="98144938:182268586"
DGRAMRCVBUF="98144938:98144938"
OOMGUARPAGES="616143:9223372036854775807"
PRIVVMPAGES="616143:677757"

# Auxiliary parameters
LOCKEDPAGES="41076:41076"
SHMPAGES="61614:61614"
PHYSPAGES="0:9223372036854775807"
NUMFILE="328608:328608"
NUMFLOCK="1000:1100"
NUMPTY="512:512"
NUMSIGINFO="1024:1024"
DCACHESIZE="183765250:189278208"
NUMIPTENT="200:200"
DISKSPACE="14975830:16473414"
DISKINODES="16651330:18316464"
CPUUNITS="120050"
OSTEMPLATE=debian-4.0
IP_ADDRESS="85.113.250.230"


vzlist:
[root@hw28101 private]# vzlist | grep 28999
     28999         89 running 85.113.250.230  -


routing table in VE:

cleanmail:/# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.0.2.1       0.0.0.0         255.255.255.255 UH    0      0        0 venet0
0.0.0.0         192.0.2.1       0.0.0.0         UG    0      0        0 venet0


/etc/network/interfaces:
cleanmail:/# cat /etc/network/interfaces
# This configuration file is auto-generated.
# WARNING: Do not edit this file, otherwise your changes will be lost.
# Please edit template /etc/network/interfaces.template instead.


# Auto generated interfaces
auto lo
iface lo inet loopback

auto venet0
iface venet0 inet static
        address 127.0.0.1
        netmask 255.255.255.255
        broadcast 0.0.0.0
        up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
        up route add default gw 192.0.2.1
auto venet0:0
iface venet0:0 inet static
        address 85.113.250.230
        netmask 255.255.255.255
        broadcast 0.0.0.0


iptables:
cleanmail:/# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


ifconfig:
target     prot opt source               destination
cleanmail:/# ifconfig
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:16436  Metric:1
          RX packets:124 errors:0 dropped:0 overruns:0 frame:0
          TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10020 (9.7 KiB)  TX bytes:10020 (9.7 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:307 errors:0 dropped:0 overruns:0 frame:0
          TX packets:296 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:24830 (24.2 KiB)  TX bytes:21967 (21.4 KiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:85.113.250.230  P-t-P:85.113.250.230  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1


/etc/resolv.conf:
cleanmail:/# cat /etc/resolv.conf
search jkit.nl
nameserver 208.67.222.222


iptables on host <snipped>:
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
<snip>
           all  --  85.113.250.230       anywhere
           all  --  anywhere             85.113.250.230

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


Now.. maybe I'm not seeing it, but this looks all fine to me. Yet.. no traffic possible, not in, not out. Any hints?
Re: Networking problem after physical to VE [message #34542 is a reply to message #34540] Fri, 16 January 2009 11:17 Go to previous messageGo to next message
ulver is currently offline  ulver
Messages: 12
Registered: July 2008
Junior Member
Hello,

Do you have others VEs which are running and with a working networking on your HN ?
Maybe the problem come from the HN ?
Do you have a good /etc/sysctlf.conf ?

http://wiki.openvz.org/Quick_installation#sysctl
Re: Networking problem after physical to VE [message #34543 is a reply to message #34542] Fri, 16 January 2009 11:18 Go to previous messageGo to next message
dignus is currently offline  dignus
Messages: 6
Registered: March 2007
Junior Member
Yes, I do have other working VE's on the HN. Also: I vzmigrated the VE to another HN.. same problem. The second HN also has other (properly working) VE's.
Re: Networking problem after physical to VE [message #34982 is a reply to message #34543] Mon, 16 February 2009 09:50 Go to previous messageGo to next message
Delphine1300 is currently offline  Delphine1300
Messages: 2
Registered: February 2009
Junior Member

Hello,

I've the same problem.
Did you find a solution ?
Could you please tell me what solved this issue ?

Thanks,

Delphine
Re: Networking problem after physical to VE [message #34984 is a reply to message #34982] Mon, 16 February 2009 10:21 Go to previous message
dignus is currently offline  dignus
Messages: 6
Registered: March 2007
Junior Member
Nope ...
Previous Topic: Security implications of giving CAP_NET_ADMIN to a vps
Next Topic: Ubuntu
Goto Forum:
  


Current Time: Mon Nov 04 14:25:14 GMT 2024

Total time taken to generate the page: 0.03519 seconds