OpenVZ Forum


Home » General » Support » *SOLVED* Networking Issue
*SOLVED* Networking Issue [message #4882] Tue, 01 August 2006 14:49 Go to next message
ataraxis is currently offline  ataraxis
Messages: 19
Registered: August 2006
Junior Member
Hi,
I am running
Quote:

m00host:~# uname -a
Linux m00host 2.6.16-026test015 #1 SMP Tue Aug 1 09:34:43 CEST 2006 i686 GNU/Linux

on a Debian System.

Installation went fine, but VE don't have network.
I can ping from the HN to the outside world
I can ping from the HN to the VE
I cannot ping from the VE to anywhere (including virtual router, HN)

I also have a nmap prob on the HN, maybe it's related:
Quote:


m00host:~# nmap x.y.z.229

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-08-01 15:19 CEST
Failed to find interface venet0 mentioned in /proc/net/route

QUITTING!



Here are some infos:
ifconfig -a
HN
m00host:~# ifconfig -a
eth0      Protokoll:Ethernet  Hardware Adresse 00:13:72:69:F2:4A
          inet Adresse:x.y.z.228  Bcast:x.y.z.255  Maske:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10932 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10383 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:799295 (780.5 KiB)  TX bytes:778275 (760.0 KiB)
          Basisadresse:0xdcc0 Speicher:fe7e0000-fe800000

eth1      Protokoll:Ethernet  Hardware Adresse 00:13:72:69:F2:4B
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Basisadresse:0xdc80 Speicher:fe7c0000-fe7e0000

lo        Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:77 errors:0 dropped:0 overruns:0 frame:0
          TX packets:77 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:8645 (8.4 KiB)  TX bytes:8645 (8.4 KiB)

venet0    Protokoll:UNSPEC  Hardware Adresse 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST PUNKTZUPUNKT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:1462 (1.4 KiB)  TX bytes:0 (0.0 b)

VE:
m00host:~# vzctl exec 110  ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:1294 (1.2 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:x.y.z.230  P-t-P:x.y.z.230  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1


route -n
HN:
m00host:~# route -n
Kernel IP Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
x.y.z.229  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
x.y.z.230  0.0.0.0         255.255.255.255 UH    0      0        0 venet0
x.x.z.224  0.0.0.0         255.255.255.224 U     0      0        0 eth0
0.0.0.0         x.y.z.225  0.0.0.0         UG    0      0        0 eth0

VE:
m00host:~# vzctl exec 110  route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
191.255.255.1   0.0.0.0         255.255.255.255 UH    0      0        0 venet0
0.0.0.0         191.255.255.1   0.0.0.0         UG    0      0        0 venet0


These are the VEs on my HN:
m00host:~# vzlist -a
     VPSID      NPROC STATUS  IP_ADDR         HOSTNAME
       102         16 running x.y.z.229  m00s02
       110          8 running x.y.z.230  m00s10


Any help is appreciated,

Kai

[Updated on: Wed, 02 August 2006 08:18] by Moderator

Report message to a moderator

Re: Networking Issue [message #4903 is a reply to message #4882] Wed, 02 August 2006 06:09 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Can you post
#cat /proc/sys/net/ipv4/ip_forward

output here.
If the output is zero ("0"), then you should do
#echo 1 > /proc/sys/net/ipv4/ip_forward

Report message to a moderator

Re: Networking Issue [message #4910 is a reply to message #4903] Wed, 02 August 2006 07:45 Go to previous messageGo to next message
ataraxis is currently offline  ataraxis
Messages: 19
Registered: August 2006
Junior Member
ip forwarding was already on
Quote:

m00host:~# cat /proc/sys/net/ipv4/ip_forward
1

Report message to a moderator

Re: Networking Issue [message #4913 is a reply to message #4910] Wed, 02 August 2006 07:55 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hmm... looks like it should work Smile
What about iptables rules?

Report message to a moderator

Re: Networking Issue [message #4914 is a reply to message #4882] Wed, 02 August 2006 08:01 Go to previous messageGo to next message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
I had the same problem. After a lot of trying I discovered that you need to load the ip_contrack as follows:

modprobe ip_conntrack ip_conntrack_enable_ve0=1


If this module is loaded without the option, unloading en reloading doesn't do the trick! You must reboot (the old Windows trick Smile) and make sure that this module is loaded with the option before any of the other ip_ modules are loaded.

There is also a possibility that Debian has some problems with the venet0 en venet0:0 construct. If the above is not the solution, you could read this post.

Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/

[Updated on: Wed, 02 August 2006 08:03]

Report message to a moderator

Re: Networking Issue [message #4916 is a reply to message #4913] Wed, 02 August 2006 08:10 Go to previous messageGo to next message
ataraxis is currently offline  ataraxis
Messages: 19
Registered: August 2006
Junior Member
iptables: all chains on accept

HN:
Quote:

m00host:~# iptables -L -vn
Chain INPUT (policy ACCEPT 58025 packets, 49M bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 41010 packets, 6352K bytes)
pkts bytes target prot opt in out source destination



VE:
Quote:

m00host:~# vzctl exec 110 iptables -L -vn
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 164 packets, 9188 bytes)
pkts bytes target prot opt in out source destination

Report message to a moderator

Re: Networking Issue [message #4918 is a reply to message #4914] Wed, 02 August 2006 08:17 Go to previous message
ataraxis is currently offline  ataraxis
Messages: 19
Registered: August 2006
Junior Member
hvdkamer wrote on Wed, 02 August 2006 10:01

I had the same problem. After a lot of trying I discovered that you need to load the ip_contrack as follows:

modprobe ip_conntrack ip_conntrack_enable_ve0=1


If this module is loaded without the option, unloading en reloading doesn't do the trick! You must reboot (the old Windows trick Smile) and make sure that this module is loaded with the option before any of the other ip_ modules are loaded.



Rebooted, added the module -> works.
Thank you!

Report message to a moderator

Previous Topic: *SOLVED* Can't Boot 2.6.8-022stab078.14 on CentOS 4.3
Next Topic: Dual veth interfaces
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Apr 30 14:49:02 GMT 2024

Total time taken to generate the page: 0.01699 seconds
Powered by FUDforum Powered by Virtuozzo Containers