Re: eth1 on VPS [message #7452 is a reply to message #7403] |
Fri, 13 October 2006 15:06   |
ferp2
Messages: 29 Registered: May 2006
|
Junior Member |
|
|
Hello Vass,
Thank you for your response.
To answer your requests:
Quote: | Can you ping anyone else in network?
|
Quote: | Please, do ifconfig -a and route -nv in VE and on HN and post the results here.
|
Please note that I have encounter new problems since rebooting the HN, which I will detail first before answering your requests:
Problem 1:
The booting sequence proceeded normally until booting VE 104. At this point, I received the following message.
Quote: | martian source 192.168.0.255 from 192.168.0.104,
on dev eth0
|| header: ff:ff:ff:ff:ff:ff:00:50:fc:72.56.44.08:00
|
Shortly after the HN system became unresponsive and required a cold reboot.
Upon rebooting a second time, the "martian source" message did not reappear, and the HN remained responsive.
Problem 2:
I could neither ssh nor ping VE 104. To remedy this, I did:
Quote: | $ cd /vz/private/104/etc/network
$ mv interfaces.template interfaces.template.off
|
I then rebooted VE 104 and was able to log in successfully.
Here are the details of ifconfig -a and route -nv:
ifconfig -a
Quote: | eth1 Link encap:Ethernet HWaddr 00:50:FC:72:56:44
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:10248 (10.0 KiB)
Interrupt:11 Base address:0xd400
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:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11060 (10.8 KiB) TX bytes:11060 (10.8 KiB)
venet0 Link encap:UNSPEC HWaddr 00-00-FF-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:187 errors:0 dropped:0 overruns:0 frame:0
TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16380 (15.9 KiB) TX bytes:14481 (14.1 KiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.0.104 P-t-P:192.168.0.104 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
|
route -nv
Quote: | 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
|
Obviously, eth1 is not functioning in the present configuration. To make it functional, I will log into VE 104 and make the eth1 boot configuration file active again. Here are the details of that file:
/etc/network/interfaces.template
Quote: | auto eth1
iface eth1 inet static
address 192.168.0.104
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.254
|
Now I will reboot VE 104 from the HN. Details are:
vzctl restart 104
Quote: | Restarting VPS
Stopping VPS ...
VPS was stopped
VPS is not mounted
Starting VPS ...
vzquota : (warning) Quota is running for id 104 already
VPS is mounted
Deleting IP address(es): 192.168.0.104
SIOCSIFFLAGS: Cannot assign requested address
Adding IP address(es): 192.168.0.104
Setting CPU units: 1000
Set hostname: vz4.lan.rmt
File resolv.conf was modified
VPS start in progress...
|
Note that I can no longer ping nor ssh into VE 104, which means I cannot reproduce the situation I was in when I started this thread.
Meanwhile, I have noticed 2 clues which may point to a solution to this problem. They are:
- The martian source message I received before the HN became unresponsive and
- SIOCSIFFLAGS: Cannot assign requested address
Here are a few details regarding my attempted network setup:
HN - 192.168.0.7 - eth0
VE 1 - 192.168.0.101 - eth0
VE 2 - 192.168.0.102 - eth0
VE 3 - 192.168.0.103 - eth0
=======================
VE 4 - 192.168.0.104 - eth1
|
|
|