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 Dec 3 2008, 1:51 am
From: Tom Henderson <t...@tomh.org>
Date: Tue, 02 Dec 2008 22:51:28 -0800
Local: Wed, Dec 3 2008 1:51 am
Subject: Re: 32bit address issue (ns-3.2 stable)

Norman wrote:
> Hi Tom,

> One more observation.

> I tried over the week static route API. Static routes basically works
> fine,
> but again not with 32bit addresses.  As I understand this is a
> separate
> issue which has nothing to do with stub networks (since Global Route
> Manager/SPF computation is not applied).

> I have a very basic setup, in which 3 routers A, B and C are connected
> via p2p interfaces.
> (a.a.a.a/32)A<--x.x.x.0/30-->B<--y.y.y.0/30-->C(c.c.c.c/32)
> router A and C have additionally (beside p2p interface toward B) 32bit
> address assigned
> on additional interface. It is csma interface (not connected to
> anything), but is marked as up.
> For some reasons static routes doesn't work in this scenario (I'm
> using a modified
> version of first.cc program to send a couple of UDP packets).

> I'm actually not sure if it is problem of static routes or something
> else. It looks like everything
> i.e. the whole routing is getting broken once I  assign /32 address on
> interface
> (before even adding static routes). If I will hash out call to
> function responsible for assigning
> those /32 addresses, I'm able to send/receive packets on x.x.x.x/30
> and y.y.y.y/30 networks
> - in order to do that (of course) also I need to modify
> UdpEchoClientHelper echoClient ("c.c.c.c", 9);
> to something like this:
> UdpEchoClientHelper echoClient ("y.y.y.2", 9);

> Conclusion from all of this /32 bit discussion is that (as I believe) /
> 32 bit address problem
> is not only related to global route manager. /32 addresses do not work
> at all and their mere presence
> seem to broke also regular routing between non-/32 addresses.

> Hope this help to diagnose the issue.

Norman,

Could you please have a look at the test programs in this bug report:
http://www.nsnam.org/bugzilla/show_bug.cgi?id=432

I tried to reproduce the above topology, and I found that I could get
static routing to work correctly, and global routing to work with a
small patch to ns-3-dev.  These programs take advantage of the patches
to recent bugs (400, 406) that were checked into ns-3-dev in the past
day or so.

Do you think that the /32 issue is fixed for you now?

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.