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 32bit address issue (ns-3.2 stable)
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
 
Tom Henderson  
View profile  
 More options Nov 25 2008, 9:49 am
From: Tom Henderson <t...@tomh.org>
Date: Tue, 25 Nov 2008 06:49:06 -0800
Local: Tues, Nov 25 2008 9:49 am
Subject: Re: 32bit address issue (ns-3.2 stable)

Norman wrote:
>> I believe that this in general is related to the lack of support for
>> stub networks, as has been recently called out in the end of bug 406:http://www.nsnam.org/bugzilla/show_bug.cgi?id=406

>> I believe that, after bug 406 is fixed, you should be able to create a
>> new virtual device (a second loopback) and put an address on it and use
>> that as a router ID; I'll write a test case for that scenario.

>> I am going to prioritize fixing the above this week and will get back to
>> you when I make progress.

> Hi Tom,

> Thanks for your replay. Now  I understand that problem is caused by a
> stub networks.
> I would be great if you could somehow manage to fix it!
> I appreciate prioritizing this issue, that's fantastic!

> One more question, by problem with "stab networks" do you mean a
> general routing issue
> or just a problem with global route manager? Bug seems to be  related
> only to global route manager,
> so my understanding is that if I will use a static route API (I didn't
> try this before) routing should work?

The global route manager is a port of the Dijkstra algorithm from
quagga's OSPFv2 implementation.  OSPF shortest path computation is a
two-stage process; in the first stage, routes to shared and transit
links are computed, and in the second stage, routes to stub networks and
interfaces are computed.  We only implemented the first stage initially,
since it was sufficient to cover initial use cases in which every link
was part of the routing topology.

Yes, you can directly set routes using the static routing API available
in class ns3::Ipv4.

- Tom


 
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.