| Re: arpsend: x.x.x.x is detected on another computer [message #4463 is a reply to message #4448] |
Tue, 11 July 2006 09:03   |
hvdkamer
Messages: 40
Registered: July 2006
|
Member |
|
|
| aistis wrote on Mon, 10 July 2006 23:45 |
"arp guarding"(?) mode
|
I don't know if Strato is doing this. However as said, it only happens when OpenVZ is started. If it is indeed an feature of an upstream switch, it should also raise the problem without OpenVZ. Right?
strato:~# iptables -t nat -F
strato:~# iptables -F
strato:~# iptables -vxnL
Chain INPUT (policy ACCEPT 33 packets, 2988 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 16 packets, 1600 bytes)
pkts bytes target prot opt in out source destination
strato:~# /etc/init.d/vz stop
Shutting down VPS 1313
Stopping OpenVZ: ..done
strato:~# lsmod | grep vz
vzdquota 40800 0 [permanent]
vzdev 2624 1 vzdquota
strato:~# ping -c4 192.168.13.2
PING 192.168.13.2 (192.168.13.2) 56(84) bytes of data.
--- 192.168.13.2 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
strato:~# /etc/init.d/vz start
Starting OpenVZ: ..done
Bringing up interface venet0: ..done
Configuring interface venet0: ..done
strato:~# lsmod | grep vz
vznetdev 17952 1
vzmon 45020 1 vznetdev
vzdquota 40800 0 [permanent]
vzdev 2624 3 vznetdev,vzmon,vzdquota
strato:~# ping -c4 192.168.13.2
PING 192.168.13.2 (192.168.13.2) 56(84) bytes of data.
From 85.214.0.133 icmp_seq=2 Destination Net Unreachable
--- 192.168.13.2 ping statistics ---
4 packets transmitted, 0 received, +1 errors, 100% packet loss, time 2999ms
strato:~# vzctl start 1313
Starting VPS ...
VPS is mounted
Adding IP address(es): 192.168.13.2
arpsend: 192.168.13.2 is detected on another computer : 00:00:5e:00:01:02
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 192.168.13.2 eth0 FAILED
Setting CPU units: 1000
VPS start in progress...
strato:~# ping -c4 192.168.13.2
PING 192.168.13.2 (192.168.13.2) 56(84) bytes of data.
64 bytes from 192.168.13.2: icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from 192.168.13.2: icmp_seq=2 ttl=64 time=0.014 ms
64 bytes from 192.168.13.2: icmp_seq=3 ttl=64 time=0.012 ms
64 bytes from 192.168.13.2: icmp_seq=4 ttl=64 time=0.013 ms
--- 192.168.13.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 0.012/0.031/0.086/0.031 ms
There is a slight difference with my start of this topic. The ping with only vz started doesn't work anymore. Probably because after much experimenting I now have networking in the VE nodes. But as you can see the aprsend is still failing. At first I thought that that was the cause of my problems. Now I think that this message is complete bogus. It would be nice if it can be resolved however, bacuase now I wasted a day before I decided that it probably doesn mean anything...
Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
[Updated on: Tue, 11 July 2006 09:05] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
