Hi falko, of course 192.168.253.52 is free in my entwork i typed exactly the commands found in the how-to i don't understand what you mean (execuse me, i'm not fluent in english) i tried several templates (debian, centos, fedora ..) but i still get the same problem as describe before. I can give you more details if needed. Thanks in advance.
Which error do you get, if you execute this command on the shell: arpsend -c 1 -w 1 -D -e 192.168.253.52 eth0
Hello, i tried the command but nothing append when i do this ! spiraledebian:~# vzctl stop 102 Stopping VPS ... VPS was stopped VPS is unmounted spiraledebian:~# arpsend -c 1 -w 1 -D -e 192.168.253.52 eth0 spiraledebian:~# vzctl start 102 Starting VPS ... VPS is mounted Adding IP address(es): 192.168.253.52 arpsend: can't get iface 'eth0:' address : Cannot assign requested address vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 192.168.253.52 eth0: FAILED arpsend: can't get iface 'eth0:' address : Cannot assign requested address vps-net_add WARNING: arpsend -c 1 -w 1 -U -i 192.168.253.52 -e 192.168.253.52 eth0: FAILED Setting CPU units: 1000 Set hostname: vps102.* File resolv.conf was modified VPS start in progress... spiraledebian:~# vzlist -a VPSID NPROC STATUS IP_ADDR HOSTNAME 102 16 running 192.168.253.52 vps102.* Do i need a special configuration on the machine specified as "name server" during the configuration ? Bind, Windows AD or anything else ? Thanks in advance for your help
What's the output of Code: ifconfig on the main machine? What's the output of Code: ping -c4 192.168.253.52 on the main machine?
spiraledebian:~# ping -c4 192.168.253.52 PING 192.168.253.52 (192.168.253.52) 56(84) bytes of data. 64 bytes from 192.168.253.52: icmp_seq=1 ttl=64 time=0.076 ms 64 bytes from 192.168.253.52: icmp_seq=2 ttl=64 time=0.050 ms 64 bytes from 192.168.253.52: icmp_seq=3 ttl=64 time=0.045 ms 64 bytes from 192.168.253.52: icmp_seq=4 ttl=64 time=0.051 ms --- 192.168.253.52 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 0.045/0.055/0.076/0.014 ms spiraledebian:~# ifconfig eth0 Lien encap:Ethernet HWaddr 00:11:09:89:AE:9D inet adr:192.168.253.22 Bcast:192.168.253.255 Masque:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1722569 errors:0 dropped:0 overruns:0 frame:0 TX packets:215528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:543024763 (517.8 MiB) TX bytes:21348982 (20.3 MiB) Interruption:23 Adresse de base:0xc000 lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:1232 (1.2 KiB) TX bytes:1232 (1.2 KiB) venet0 Lien encap:UNSPEC HWaddr 00-00-FF-00-00-00-00-00-00-00-00-00-00-00-00-00 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:4857 errors:0 dropped:0 overruns:0 frame:0 TX packets:4130 errors:0 dropped:32 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:558584 (545.4 KiB) TX bytes:247087 (241.2 KiB)
OpenVZ Pb (vmware) Hello, i get exactly the same problem in a vmware. But i've already configured one in the same way and it works fine. arpsend: can't get iface 'eth0:' address : Cannot assign requested address vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 192.168.1.44 eth0: FAILED etc.... The ip 192.168.1.44 is free (i'm sure) . The command arpsend -c 1 -w 1 -D -e 192.168.1.44 eth0 return no errors. Patrick
Re vmpat4:~# ping -c4 192.168.1.44 PING 192.168.1.44 (192.168.1.44) 56(84) bytes of data. From 192.168.1.24 icmp_seq=2 Destination Host Unreachable From 192.168.1.24 icmp_seq=3 Destination Host Unreachable From 192.168.1.24 icmp_seq=4 Destination Host Unreachable --- 192.168.1.44 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2998ms , pipe 3 vmpat4:~# ifconfig eth0 Lien encap:Ethernet HWaddr 00:0C:29:4C:1A:2D inet adr:192.168.1.24 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::20c:29ff:fe4c:1a2d/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30318 errors:0 dropped:0 overruns:0 frame:0 TX packets:19748 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:37337734 (35.6 MiB) TX bytes:1664984 (1.5 MiB) Interruption:177 Adresse de base:0x1080 lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) venet0 Lien 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vmpat4:~#
Re Yes of course. It's the ip of the "master" . master => 192.168.1.24 vserver1 => 192.168.1.44 etc... And i repeat : this config works perfectly on another vmware with the same distrib (debian-3.1 stable).
Sample config ok/nok Hello, I've put here http://xoopmenier.dynalias.net/xoops/docext/vservers/details.htm a config which run perfects. We see this : on the master ifconfig outputs : ..... venet0 Lien encap:UNSPEC HWaddr 00-00-FF-00-00-00-00-00-00-00-00-00-00-00-00-00 .... in the vps ifconfig outputs : ... venet0 Link encap:UNSPEC HWaddr FF-BF-A8-F6-FF-BF-38-93-00-00-00-00-00-00-00-00 ... venet0:0 Link encap:UNSPEC HWaddr FF-BF-A8-F6-FF-BF-1C-F7-00-00-00-00-00-00-00-00 .... Now on a machine which fails to start the vps : ifconfig on the master : ... venet0 Lien encap:UNSPEC HWaddr 00-00-FF-00-00-00-00-00-00-00-00-00-00-00-00-00 .... ifconfig in the vps : ... venet0 Link encap:UNSPEC HWaddr 00-00-FF-00-00-00-00-00-00-00-00-00-00-00-00-00 .... venet0:0 Link encap:UNSPEC HWaddr 00-00-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00 .... We see that HWaddr of venet0 is the same (master/vps) on the broken config. Hope this helps network's gurus to solve our problem...
Partially solved Finally i destroy the virtual machine and reinstall it and that works but i didn't like this behavior and i migrate to linux-vserver. Thanks for your help.