Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion IPv4 Routing behaviour after interface SetDown procedure
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Egemen Cetinkaya  
View profile  
 More options Nov 5 2008, 7:51 pm
From: Egemen Cetinkaya <egemen.cetink...@gmail.com>
Date: Wed, 5 Nov 2008 16:51:51 -0800 (PST)
Local: Wed, Nov 5 2008 7:51 pm
Subject: IPv4 Routing behaviour after interface SetDown procedure
Hi,

I am trying to simulate a scenario which brings down a PointToPoint
link between a node pair. The topology consists of three nodes, no
loop, and using GlobalRoute manager to route OnOff traffic. To
accomplish this we used Ipv4::SetDown and Ipv4::SetUp procedures.

It looks like setting down and setting up the IPv4 interfaces (of the
source node and the hop node) are working fine. Although, I am
observing that after setting the "interfaces up", the source does not
able to send the packets. Below is the portion in the logs I think as
problematic:

1800000000ns Ipv4L3Protocol:SendRealOut(): No route to host.  Drop.

My interpretation of the "Ipv4L3Protocol:SendRealOut(): No route to
host.  Drop." is that:

A-This can be due to LSAs not being sent on a regular basis (or maybe
they are being performed without showing anything in the logs). I
observed in the logs that Link State algorithm do calculations only at
the beginning of the script. At the end the LS data is cleared due to
Simulation:Destroy command.

or

B-In the ipv4-l3-protocol.cc file it states that (starting line 596):

" XXX Note here that in most ipv4 stacks in the world, the route
calculation for an outgoing packet is not done in the ip layer. It is
done within the application socket when the first packet is sent to
avoid this costly lookup on a per-packet basis. That would require us
to get the route from the packet, most likely with a packet tag. The
higher layers do not do this yet for us. "

Which I interpret, since there is no IP layer calculation, after the
interface is brought up, application socket doesn't know how to route
the packets. (But why, I don't know)

Now, my first question is what should I do for the source node to be
able to forward the packets after its interface is setdown and setup?
I was thinking to reinitialize GlobalRouterManager via a schedule, but
the script complained about using the PopulateRoutingTables (); since
it was used previously to initialize/populate routing tables.

Second question is: do you think not sending LSAs periodically is the
normal behaviour, or can it be a bug?

Thank you beforehand for your help,

Regards,

Egemen


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.