| veth does not ping itself. Where is the problem? [message #35596] |
Tue, 07 April 2009 22:04  |
divB
Messages: 79
Registered: April 2009
|
Member |
|
|
Hello!
I can't ping myself in the VE. What could be the problem?
# zctl set 300 --netif_add eth0 --save
Saved parameters for VE 300
# vzctl start 300
Starting VE ...
VE is mounted
Setting CPU units: 1000
Configure meminfo: 65536
Configure veth devices: veth300.0
VE start in progress...
# vctl enter 300
## ifconfig eth0 192.168.3.1 netmask 255.255.255.0 up
## ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:51:8A:04:58
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::218:51ff:fe8a:458/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:196 (196.0 b)
## ping 192.168.3.1
PING 192.168.3.1 (192.168.3.1) 56(84) bytes of data.
^C
--- 192.168.3.1 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 6012ms
##
I have not connected veth300.0 on the host to a bridge until now, but I have tried it; id did not change. In my opinion, the ping must work even when I do nothing with veth300.0 on the host...
Thank you,
divB
|
|
|
|
|
|
| Re: veth does not ping itself. Where is the problem? [message #35609 is a reply to message #35597] |
Wed, 08 April 2009 11:08  |
divB
Messages: 79
Registered: April 2009
|
Member |
|
|
Thank you very very much, it really seems to work now.
BUT: I can't see anything on the host. Normally everything i put into eth0 inside a VE should come out on the corresponding veth on the host, shouldn't it? I want to bridge it together with a VLAN, everything anonymous [1].
# ifconfig lo up
# ifconfig eth0 93.83.102.171 netmask 255.255.255.248 up
ns:/# ping 93.83.102.171
PING 93.83.102.171 (93.83.102.171) 56(84) bytes of data.
64 bytes from 93.83.102.171: icmp_seq=1 ttl=64 time=0.080 ms
64 bytes from 93.83.102.171: icmp_seq=2 ttl=64 time=0.052 ms
64 bytes from 93.83.102.171: icmp_seq=3 ttl=64 time=0.041 ms
64 bytes from 93.83.102.171: icmp_seq=4 ttl=64 time=0.058 ms
^C
--- 93.83.102.171 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.041/0.057/0.080/0.017 ms
# ping 93.83.102.170
PING 93.83.102.170 (93.83.102.170) 56(84) bytes of data.
From 93.83.102.171 icmp_seq=1 Destination Host Unreachable
From 93.83.102.171 icmp_seq=2 Destination Host Unreachable
From 93.83.102.171 icmp_seq=3 Destination Host Unreachable
From 93.83.102.171 icmp_seq=5 Destination Host Unreachable
From 93.83.102.171 icmp_seq=6 Destination Host Unreachable
From 93.83.102.171 icmp_seq=7 Destination Host Unreachable
^C
--- 93.83.102.170 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8020ms
, pipe 3
#
As you can see, the ping to the own IP works now but to .170 not. Also, there is no output on the host with "tcpdump -i veth300.0"...
Thank you again,
divB
[1] This means: I have a vlan3 on the host without IP, the veth300.0 on the host without IP, bridge them together into br0, also without IP. The eth0 inside the vServer has an IP address and also some other devices in the same Layer2 network (connected to VLAN3).
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
