Man Linux: Main Page and Category List


       sbgp - a simple BGP4 speaker and listener


       Usage: sbgp [-01av] [-i binary_data_in_file] [-o binary_data_out_file]
                   [-l  log_file]  [-f  config_file]  [-c  port] [-d port] [-s
                   [-E seconds_idle_after_in_file_EOF]
                   [ASmy_as] [peer_ip ASpeer_as]...

       SBGP is a simple BGP4 speaker and listener. SBGP does not apply  policy
       to  routes,  nor  does  it maintain a routing information base (RIB) of
       routes it has previously learned. Rather, SBGP provides a mechanism for
       monitoring  routing  information  sent  from  a peer, and for injecting
       routing information into a peering session.


       sbgp  [-av]  [-i  binary_data_in_file]  [-o  binary_data_out_file]  [-l
       log_file]  [-f  config_file]  [-c  port]  [-d  port]  [my  AS] [peer_IP



          Accept peering BGP connection from all peers.


          Turn on verbose logging to standard output.

       -i binary_data_in_file

          Inject routes from this file into every  peering  session.  Use  the
              name ’stdin’ to read input from standard in.

       -o binary_data_out_file

          Save route updates from all peering sessions into this file. Use the
              file name ’stdout’ to write output to standard out.

          -l log_file
          Write logging information to this file. By default, SBGP logs to
              /tmp/, where pid is the process ID number of the SBGP

          -f config_file
          Not supported yet

          Not supported yet

          -c port
          Connect to this port on all BGP peers.

          -d port
          Listen on this port for BGP peering connections.

          [my AS] [peer_IP peer_AS]...
          Use my AS for my Autonymous System number and open peering sessions
              with each peer_IP address.


          As arguments, SBGP takes the local AS number followed by the IP
          address  and  AS number of the BGP4 peer. Multiple peer IP addresses
          AS pairs may be specified. For example:

          sbgp AS2011 AS690

          attempts to initiate a BGP4 peering session with the old NSFNET
          backone on enss131. By default, SBGP writes logging information to

          The following command directs tracing information to stdout (the -v
          option) and will save MRT messages containing the contents of BPG4
          update packets to /tmp/data (the -o option).

          sbgp -vo data AS2011 AS690

           Note that the remote peer must  be  configured  to  accept  a  BGP4
           session from the machine on which SBGP is running.

          The following command will inject routes stored in the binary MRT
          message file data into the peering sessions with enss131:

          sbgp -vi data AS185 AS690

       You can find more documentation in /usr/share/doc/mrt/html/