[Xorp-users] BGP setup

[Atanu Ghosh]

Hi,

Just runnning gmake check in the bgp/harnesses directory should give you
some insight into how to run the scripts.

The format of the icsi1.mrtd is MRTd, this is the format used by the
Route Views project (http://www.routeviews.org/) the tool route_btoa
from the MRTd (http://mrt.sourceforge.net/) can be used to view the dump
file. We decided to use a commonly used format rather then invent our
own.

The implementation of "get_ready_priority" is in the file selector.cc in
the libxorp directory. This method tries to find the highest priority file
descriptor event, it is part of the task scheduling code.

	   Atanu.

>>>>> "HJ" == HJ  <hengjuen at gmail.com> writes:

    HJ>    Thanks Pavlin and Kristian, for you input. My intention is
    HJ> trying to get BGP up and play with loading it and see my CPU
    HJ> performance.



    HJ>    I found some interesting test scripts in the harness folder,
    HJ> which can serve similar purpose.

    HJ>    May I know what is the way to write our own dump file for the
    HJ> router, since i am not able to view icsi1.mrtd used in
    HJ> test_peering2.sh.

    HJ>    What is the content of icsi1.mrtd?



    HJ>    Also i found out that there is a function call on
    HJ> "get_ready_priority" under xorp_bgp function consume the most
    HJ> CPU cycle. May i know what is the reason? I counldn't get into
    HJ> the source code since it is showing assembly rather then C.





    HJ>    Thanks.  Heng Juen.


    HJ>    On 9/19/07, Pavlin Radoslavov <pavlin at icir.org> wrote:

    HJ>      Kristian Larsson <kristian at spritelink.net> wrote:
    >> HJ wrote: > Hi, > I try to play around with BGP using with below
    >> configuration
    HJ>      and test
    >> > setup, but it seems like i am not able to send a packet over
    HJ>      the other
    >> > side. Can anyone help to access my configuration file below?  >
    >> Thanks in advance.  > Heng Juen
    >> 
    >> You don't need BGP for this setup. You only need a routing
    HJ>      protocol if
    >> you have several routers that need to talk to each other.  In
    >> this case something else is wrong.  Are you running on Linux?
    >> Perhaps you've forgot to enable ip
    HJ>      forwarding
    >> (echo 1 > /proc/sys/net/ipv4/ip_forward). Make sure the default
    HJ>      gateways If fea/unicast-forwarding4 is enabled (as it
    HJ> appears in the original configuration) then the FEA will take
    HJ> care of enabling the forwarding in the kernel and there is no
    HJ> need for "echo 1 > /proc/sys/net/ipv4/ip_forward".  My $0.02 :)
    HJ> Pavlin
    >> of your end hosts are the routers interface addresses.  Please
    >> provide more details on your setup.
    >> 
    >> -K
    >> 
    >> _______________________________________________ Xorp-users
    >> mailing list Xorp-users at xorp.org
    >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
    HJ> _______________________________________________ Xorp-users
    HJ> mailing list Xorp-users at xorp.org
    HJ> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users