some problems about inet example BGP2RoutersInAs

15 views
Skip to first unread message

Jevy Lee

unread,
Jan 25, 2016, 2:48:32 AM1/25/16
to OMNeT++ Users
Hello Guys:
  I tried to use inet example "BGP2RoutersInAs". I'm using the source code and I didn't change anything. And I find a problem about this example.
  The network is as show in Figure 1:

Figure 1 the network

     The RC1 and RC2 are both connecting with BGPRouter C. RC1 is connecting with a small network which IP Prefix is 192.171.0.0. RC2 is connecting with a network which IP prefix is 192.172.0.0.when I'm running this example, the routingTables in C is showing in Figure 2. From the figure, we can see that there are tow entries 192.171.0.0 and 192.172.0.0.

Figure 2. routingTables in C

And the routing tables in A2 is shown in Figure 3.

Figure 3 routingTables in A2.

From the routingtables in A2, we can see that BGP router A2 has already learned the routing table entry 192.172.0.0. And here my question comes, why A2 hasn't learned routing entry 192.171.0.0?  Besides, how can I control the notification of routing prefix?

Is there anyone familar with this example? It will be very grateful if anyone can help me.



  

Pasquale Di Dio

unread,
Feb 1, 2016, 7:14:47 AM2/1/16
to OMNeT++ Users
Hello,

I spent some time on this example.

The IPv4Configurator into network.ned file,  has the addstaticRouter = false, this means that the routing tables must be built by OSPF and BGP protocols dynamicly.
 
If you wait...until 17s (more or less) you will see that the A2 RoutingTabel match exactly the C RoutingTable.
The OSPF have to converge first of all...and it need some time.
Then BGP (eBPG session from C --> A2) send a BGPUpdate msg that upload the entry into A2 RoutingTable.
That's what i understand!

"Besides, how can I control the notification of routing prefix?"
Sorry...but i don't know how to do it.

Good Luck

Jevy Lee

unread,
May 23, 2016, 4:20:12 AM5/23/16
to omn...@googlegroups.com
Thank you very much! Are you working in network area?

--
You received this message because you are subscribed to a topic in the Google Groups "OMNeT++ Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/omnetpp/rLUqDMzHiNw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages