Virtual IP setup Problem
Madhur
node requires unique IP address to be assigned. Due to crunch of linux
machines at home, I planned to use Virtual IP, running A, B, C and D
on Machine 1 and E on Machine 2. An IP packet is expected to travel
from D to C, C to B and B to outside network. On the other way around
from the outside network -> B, B->C and C->D. Lets I ping a machine
in the outside network. I can see the packet traversing D->C, C->B B-
>outside network and on the way around outside network ->B, B->C, C-
>D, but the ping response is not shown at command prompt. This means
the packet is getting dropped at the IP stack of Machine 2.
When I had close look at the packets, I could observe that packets
which are coming out from C->D were with Ethernet MAC address being
all zeroes. This might be the cause of IP packets getting dropped. Is
there a solution I can avoid so that packets are not dropped. When I
start doing pinging C from D, ping packets from the outside network
gets displayed. For time being temporary solution, I start redundant
ping which keeps pinging C from D.
This problem is almost killing my multiple node issue. I kindly
request for help.
Jorgen Grahn
> I am trying to run multiple network nodes (A, B, C, D and E). Each
> node requires unique IP address to be assigned. Due to crunch of linux
> machines at home, I planned to use Virtual IP,
What does Virtual IP mean to you? I don't think there is a common
definition (despite the Wikipedia entry, which seems to
connect/confuse it with VLAN (IEEE 802.1Q) somehow).
If it's just "assign many addresses to the same interface", don't
expect them to work as separate IP stacks with e.g. routing inbetween.
> running A, B, C and D
> on Machine 1 and E on Machine 2. An IP packet is expected to travel
> from D to C, C to B and B to outside network. On the other way around
> from the outside network -> B, B->C and C->D.
So it's
outside -- B -- C -- D
-----------
machine 1
Where did A and E go?
> Lets I ping a machine
> in the outside network. I can see the packet traversing
> D->C, C->B B->outside network and on the way around
> outside network ->B, B->C, C->D, but the ping response is not shown
> at command prompt. This means
> the packet is getting dropped at the IP stack of Machine 2.
There is something wrong with your description -- that machine
is not involved.
> When I had close look at the packets, I could observe that packets
> which are coming out from C->D were with Ethernet MAC address being
> all zeroes. This might be the cause of IP packets getting dropped. Is
> there a solution I can avoid so that packets are not dropped. When I
> start doing pinging C from D, ping packets from the outside network
> gets displayed. For time being temporary solution, I start redundant
> ping which keeps pinging C from D.
> This problem is almost killing my multiple node issue. I kindly
> request for help.
You need to clarify your question.
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
Pascal Hambourg
Jorgen Grahn a ï¿œcrit :
> On Sat, 2009-12-19, Madhur wrote:
>> I am trying to run multiple network nodes (A, B, C, D and E). Each
>> node requires unique IP address to be assigned. Due to crunch of linux
>> machines at home, I planned to use Virtual IP,
>
> What does Virtual IP mean to you?
I guess the OP meant more something like "virtual machines".
> I don't think there is a common
> definition (despite the Wikipedia entry, which seems to
> connect/confuse it with VLAN (IEEE 802.1Q) somehow).
Do you mean <http://en.wikipedia.org/wiki/Virtual_IP_address> ?
I do not see any connection or confusion with VLAN. IIUC, it is the kind
of service address used in redundant evironments, e.g. a virtual router
address with VRRP.
> You need to clarify your question.
I agree.
Jorgen Grahn
> Hello,
>
> Jorgen Grahn a �crit :
>> On Sat, 2009-12-19, Madhur wrote:
>>> I am trying to run multiple network nodes (A, B, C, D and E). Each
>>> node requires unique IP address to be assigned. Due to crunch of linux
>>> machines at home, I planned to use Virtual IP,
>>
>> What does Virtual IP mean to you?
>
> I guess the OP meant more something like "virtual machines".
That thought never crossed my mind, but now that you mention it ...
>> I don't think there is a common
>> definition (despite the Wikipedia entry, which seems to
>> connect/confuse it with VLAN (IEEE 802.1Q) somehow).
>
> Do you mean <http://en.wikipedia.org/wiki/Virtual_IP_address> ?
> I do not see any connection or confusion with VLAN.
"Virtual LAN" is in the "See also" section of that article without any
further explanation -- that was why I mentioned it.
> IIUC, it is the kind
> of service address used in redundant evironments, e.g. a virtual router
> address with VRRP.
>
>> You need to clarify your question.
>
> I agree.
--