OpenVZ Forum


Home » General » Support » Networking issue with FC4
Networking issue with FC4 [message #8017] Fri, 03 November 2006 13:11 Go to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Hello,

The installation of OpenVZ on the server was a breeze, both the kernel replacement and the daemon installation:

[07:59:05][~]> rpm -qa | grep vz
vzquota-3.0.9-1
vzpkg-2.7.0-18
vzctl-lib-3.0.12-1
vzctl-3.0.12-1
vzrpm44-4.4.1-22.5
vzrpm44-python-4.4.1-22.5
vztmpl-fedora-core-5-2.0-2
ovzkernel-2.6.9-023stab032.1
vzyum-2.4.0-11
vzrpm43-python-4.3.3-7_nonptl.6
[07:59:12][~]> uname -a
Linux X.Y.Z 2.6.9-023stab032.1 #1 Fri Oct 20 02:48:36 MSD 2006 i686 athlon i386 GNU/Linux


I modified the kernel tuning parameters as mentioned in the guide and networking parameters are all set:

[08:03:26][~]> cat /proc/sys/net/ipv4/ip_forward
1
[08:03:33][~]> iptables -L
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


I have created a FC5 VE and added it an IP as described in your guide, however networking doesn't work. Ifconfig & route on the VE lists the following info:

-bash-3.1# 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:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1084 (1.0 KiB)  TX bytes:1084 (1.0 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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:23688 (23.1 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:11.22.33.44  P-t-P:11.22.33.44  Bcast:11.22.33.44  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
-bash-3.1# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
191.255.255.0   0.0.0.0         255.255.255.0   U     0      0        0 venet0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 venet0
0.0.0.0         191.255.255.1   0.0.0.0         UG    0      0        0 venet0


Where 11.22.33.44 is the IP I added for the VE. Now here's the output for the HN:

[08:09:05][~]> ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:00:21:F4:53:1F
          inet addr:11.22.33.99  Bcast:11.22.33.255  Mask:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1081802 errors:0 dropped:0 overruns:0 frame:0
          TX packets:300108 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:88613125 (84.5 MiB)  TX bytes:185321665 (176.7 MiB)
          Interrupt:17 Base address:0xd000

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:33065 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33065 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3462234 (3.3 MiB)  TX bytes:3462234 (3.3 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:164 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:23688 (23.1 KiB)  TX bytes:0 (0.0 b)


Where 11.22.33.99 is my main IP address.

After browsing these forums, I tried several tricks but none worked (the preserve arguments for /bin/cf and the early load of the ip_conntrack module).

Any suggestions for my problem?
Thank you and for your great product.

Report message to a moderator

Re: Networking issue with FC4 [message #8020 is a reply to message #8017] Fri, 03 November 2006 13:28 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Can you ping HW from VE?

Thanks.

Report message to a moderator

Re: Networking issue with FC4 [message #8024 is a reply to message #8020] Fri, 03 November 2006 13:48 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Nope, the only successful ping I can do from the VE is pinging to its assigned IP.

Report message to a moderator

Re: Networking issue with FC4 [message #8025 is a reply to message #8024] Fri, 03 November 2006 13:54 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
In addition to my previous post, here's what tcpdump captured while pinging google:

HN:
[08:51:31][~]> tcpdump -n -i venet0
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooked socket
tcpdump: WARNING: venet0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
08:51:48.180973 IP 11.22.33.44 > 64.233.167.99: icmp 64: echo request seq 0
08:51:49.180063 IP 11.22.33.44 > 64.233.167.99: icmp 64: echo request seq 1
08:51:50.179916 IP 11.22.33.44 > 64.233.167.99: icmp 64: echo request seq 2
08:51:51.179758 IP 11.22.33.44 > 64.233.167.99: icmp 64: echo request seq 3

4 packets captured
4 packets received by filter
0 packets dropped by kernel


VE:
[08:50:59][~]> vzctl enter 102
entered into VE 102
-bash-3.00# ping 64.233.167.99
PING 64.233.167.99 (64.233.167.99) 56(84) bytes of data.

--- 64.233.167.99 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

Report message to a moderator

Re: Networking issue with FC4 [message #8028 is a reply to message #8025] Fri, 03 November 2006 14:06 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Sorry if I missunderstood, you but:

As far as I undestand your HN IP address is 11.22.33.99, not 64.233.167.99. So, please, ping you HN (11.22.33.99) from VE(11.22.33.44), and show us the tcpdump.

Thanks.

BTW, can you provide access to the node?

Report message to a moderator

Re: Networking issue with FC4 [message #8029 is a reply to message #8028] Fri, 03 November 2006 14:12 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Sorry, I misunderstood Very Happy Here's the output:

VE:
-bash-3.00# ping 11.22.33.99
PING 11.22.33.99 (11.22.33.99) 56(84) bytes of data.

--- 11.22.33.99 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms


HN:
[09:09:48][~]> tcpdump -n -i venet0
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooke                                              d socket
tcpdump: WARNING: venet0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
09:10:36.381161 IP 11.22.33.44 > 11.22.33.99: icmp 64: echo request seq 0
09:10:37.380548 IP 11.22.33.44 > 11.22.33.99: icmp 64: echo request seq 1
09:10:38.380406 IP 11.22.33.44 > 11.22.33.99: icmp 64: echo request seq 2
09:10:39.380247 IP 11.22.33.44 > 11.22.33.99: icmp 64: echo request seq 3

4 packets captured
4 packets received by filter
0 packets dropped by kernel


11.22.33.44 - IP assigned to the VE
11.22.33.99 - main IP of the HN

About the access, it's a production server, I'm not allowed to Sad

[Updated on: Fri, 03 November 2006 14:13]

Report message to a moderator

Re: Networking issue with FC4 [message #8031 is a reply to message #8017] Fri, 03 November 2006 14:27 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
In the subject of your post FC4 VE is pointed at,
but in the actual post you mentioned FC5, so what template do you actually use? Smile
Are there other VEs (perhaps with other templates), that work with network well?

Thanks.

[Updated on: Fri, 03 November 2006 14:28]

Report message to a moderator

Re: Networking issue with FC4 [message #8033 is a reply to message #8031] Fri, 03 November 2006 14:36 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
HN runs FC4, while the I tested more templates, including FC5 I mentioned. CentOS fails as well.

Report message to a moderator

Re: Networking issue with FC4 [message #8036 is a reply to message #8033] Fri, 03 November 2006 14:59 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

can you post us output of the following command:
# ip r get 11.22.33.44
# route -an

Thanks.

Report message to a moderator

Re: Networking issue with FC4 [message #8038 is a reply to message #8017] Fri, 03 November 2006 15:06 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Here's the output after exectuding the commands on the HN. Please note that the "a" argument failed for my /sbin/route, and the ip command out put is identical on the VE too. The route table of the VE id displayed in the first post of the thread.

[10:03:45][~]> ip r get 11.22.33.44
local 11.22.33.44 dev lo  src 11.22.33.44
    cache <local>  mtu 16436 advmss 16396 metric 10 64
[10:04:11][~]> route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
11.22.33.44    0.0.0.0         255.255.255.255 UH    0      0        0 venet0
11.22.33.128    0.0.0.0         255.255.255.128 U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         11.22.33.129    0.0.0.0         UG    0      0        0 eth0


Thank you

Report message to a moderator

Re: Networking issue with FC4 [message #8056 is a reply to message #8038] Sat, 04 November 2006 11:38 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Any suggestions for my problem? Very Happy

I'm now 100% positive that the issue is not template dependent, I've tested all published distro templates and all get to be unconnected.

Report message to a moderator

Re: Networking issue with FC4 [message #8060 is a reply to message #8017] Sun, 05 November 2006 14:17 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
I think I found something. While testing the suggested trick by ussing mod ip_conntrack I found that it is loaded AFTER ip_tables for the HN - a excerpt from dmesg follows:

Nov  1 16:40:24 master kernel: ip_tables: (C) 2000-2002 Netfilter core team
Nov  1 16:40:24 master kernel: NET: Unregistered protocol family 17
Nov  1 16:40:24 master kernel: NET: Registered protocol family 17
Nov  1 16:40:24 master kernel: ip_conntrack : parameter ip_conntrack_enable_ve0 is obsolet
ed. In kernel >= 2.6.15 connection tracking on hardware node is enabled by default, use ip
_conntrack_disable_ve0=1 parameter to disable.
Nov  1 16:40:24 master kernel: ip_conntrack version 2.1 (4095 buckets, 32760 max) - 328 by
tes per conntrack


I just placed the options line at the beginning of /etc/modprobe.conf, what should I do yo load it before ip_tables?

Thank you.

Report message to a moderator

Re: Networking issue with FC4 [message #8061 is a reply to message #8060] Sun, 05 November 2006 14:56 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
I loaded ip_conntrack before the other ip_ modules but didn't worked anyway Sad

Report message to a moderator

Re: Networking issue with FC4 [message #8072 is a reply to message #8061] Mon, 06 November 2006 23:35 Go to previous messageGo to next message
hbidad is currently offline  hbidad
Messages: 4
Registered: November 2006
Junior Member
Seems I am having the exact same problem...any insight?

Report message to a moderator

Re: Networking issue with FC4 [message #8073 is a reply to message #8017] Mon, 06 November 2006 23:42 Go to previous messageGo to next message
hbidad is currently offline  hbidad
Messages: 4
Registered: November 2006
Junior Member
Although, if I remove the VE IP from the host, I can connect directly to to the VE from a remote workstation. I though all would be good after this, but I can not get the VE to resolve any domain (i.e. install cpanel)

I have setup my nameservers and verified them in resolv.conf. my nameservers run off a vlan (intranet IP's) The host resolves everything fine...but beyond this.. I am stumped

I am at SoftLayer datacenter..

Report message to a moderator

Re: Networking issue with FC4 [message #8075 is a reply to message #8073] Tue, 07 November 2006 06:27 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

hbidad, It's better to start new thread about your problem.

Thank,
Vasily.

[Updated on: Tue, 07 November 2006 07:52]

Report message to a moderator

Re: Networking issue with FC4 [message #8076 is a reply to message #8038] Tue, 07 November 2006 07:21 Go to previous messageGo to next message
Vasily Tarasov is currently offline  Vasily Tarasov
Messages: 1345
Registered: January 2006
Senior Member
Hello,

Sorry for delay, we have some holidays here. Smile
As you see the problem is in routing:
Quote:

[10:03:45][~]> ip r get 11.22.33.44
local 11.22.33.44 dev lo  src 11.22.33.44
    cache <local>  mtu 16436 advmss 16396 metric 10 64
[10:04:11][~]> route -n


Every packet that goes to VE (11.22.33.44) thanks to routing goes to lo interface, but should go to venet0.

The question is why this happens? Rolling Eyes
I'll think about it.

Report message to a moderator

Re: Networking issue with FC4 [message #8077 is a reply to message #8017] Tue, 07 November 2006 07:35 Go to previous messageGo to next message
hbidad is currently offline  hbidad
Messages: 4
Registered: November 2006
Junior Member
Vasily, I am sure you were talking to me about starting a new thread. However, our problems are exactly alike. I get the same output as the OP. Down to the routing problem as you described.

I was just trying to if eth0 being vlan and eth1 being public would have something to with it.

Report message to a moderator

Re: Networking issue with FC4 [message #8090 is a reply to message #8017] Tue, 07 November 2006 10:59 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Vasily, good find, I couldn't figure that myself in years. Unfortunatelly I'm not very good with these kind of tasks related to routing, so if you have any suggestions for me please let me know.

Also, I don't know if this helps, but in the HN route table (which I listed in a previous post) the network masks seem to be different, could this be a problem?

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
11.22.33.44    0.0.0.0         255.255.255.255 UH    0      0        0 venet0
11.22.33.128    0.0.0.0         255.255.255.128 U     0      0        0 eth0


I mean 255.255.255.255 vs 255.255.255.128 for the actual internet connection ...

Thanks a lot!

Report message to a moderator

Re: Networking issue with FC4 [message #8568 is a reply to message #8090] Sun, 26 November 2006 20:46 Go to previous messageGo to next message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
Any suggestions for my issue? Very Happy

Thanks!

Report message to a moderator

Re: Networking issue with FC4 [message #8569 is a reply to message #8017] Mon, 27 November 2006 01:07 Go to previous messageGo to next message
hbidad is currently offline  hbidad
Messages: 4
Registered: November 2006
Junior Member
Hell, I had the exact problem as you (see above Rolling Eyes) .. I resolved my issue..

go to /etc/sysconfig/network-scripts/ and tell us the filenames that start with ifcfg-eth1* (e.g. ifcfg-eth1-range*)

Report message to a moderator

Re: Networking issue with FC4 [message #8570 is a reply to message #8569] Mon, 27 November 2006 01:12 Go to previous message
wasrv is currently offline  wasrv
Messages: 12
Registered: November 2006
Junior Member
 
[20:10:55][/etc/sysconfig/network-scripts]> ls ifcfg-eth*
-rw-r--r--  1 root root 142 Sep 28  2005 ifcfg-eth0
-rw-r--r--  1 root root 166 Sep 27  2005 ifcfg-eth1


Thanks for the relpy!

Both files configure real NICs, but only eth0 is cabled. However no *range* files there Confused

Thanks again.

Report message to a moderator

Previous Topic: *SOLVED* VLAN on VETH device?
Next Topic: Best setup with lvm?
Goto Forum:
  

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

Current Time: Sat Jul 27 14:20:56 GMT 2024

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