[Xorp-users] compilation problmes with mips

RamaKanthVarala varala_kanth at yahoo.com
Tue Mar 24 08:23:27 PDT 2009


Hi Pavlin,

I could able to increase the number of multicast seesions by following the ERRATA document.

Still iam looking for the following configuration.

to control only the specific multicast range addresses ? 

I followed your comments but still not with much sucess.

Let me explaing my testing environment and my requirement.

Windows PC ==> WAN =eth0==> Xorp Router(Fedora 8 Machine) =eth1==> LAN ==> Windows PC

Fedora Machine has two N IC cards 

1. eth0 with public ip Wan interface 
2. eth1 with lan interface.

Now what iam trying to do is.

1) i want to limit my xorp router to allow only 239.1.1.0/26 i.e 239.1.1.0 to 239.1.1.127 multicast range IGMP , remaining should be discarded .

This is both in case of server and host i.e 

1) if my lan pc is working as receiver it should only get the stream if the range is within the above specified one.
2) if my lan pc is source at that time also if it is with in the above range then only it should be allowed to muliticast.

I think i can use iptables in implementing a firewall in order to discard the packates out side of this range, but this solution would be outside of the xorp.

Iam trying this behavior from the xrop.

thanks and regards
kanth

Iam pasting my config.boot here .

protocols {
/*      fib2mrib {
                 disable: false
                 }*/
        igmp {
                disable: false
                interface eth0 {
                        vif eth0 {
                                disable: false
                                version: 3
                                /*enable-ip-router-alert-option-check: false */
                                query-interval: 125
                                query-last-member-interval: 1
                                query-response-interval: 10
                                robust-count: 2
                                }
                  }
                  interface br0 {
                          vif br0 {
                                disable: false
                                version: 3
                                /*enable-ip-router-alert-option-check: false */
                                query-interval: 125
                                query-last-member-interval: 1
                                query-response-interval: 10
                                robust-count: 2
                                }
                  }
        }
        pimsm4 {
                disable: false
                interface eth0 {
                        vif eth0 {
                                disable: false
                                /*enable-ip-router-alert-option-check: false */
                                dr-priority: 1
                                hello-period: 30
                                hello-triggered-delay: 5
                                }
                        }
                interface br0 {
                        vif br0 {
                        disable: false
                        /*enable-ip-router-alert-option-check: false */
                        dr-priority: 1
                        hello-period: 30
                        hello-triggered-delay: 5
                        }
                }
                static-rps {
                        rp *.*.*.38 {   /* this my fedora wan ip */
                                group-prefix 239.1.1.0/26 {
                                }
                        }
                }
        }
}
fea {
        unicast-forwarding4 {
                disable: false
        }
}
interfaces {
        restore-original-config-on-shutdown: false
        interface eth0 {
                disable: false
                discard: false
                description: ""
                default-system-config {
                }
                }
        interface br0 {
                disable: false
                discard: false
                description: ""
                default-system-config {
                }
        }
}
plumbing {
        mfea4 {
                disable: false
                interface eth0 {
                        vif eth0 {
                                disable: false
                        }
                }
                interface  br0 {
                        vif br0 {
                                disable: false
                        }
                }
        }
}


 
 
RamaKanthVarala <varala_kanth at yahoo.com> wrote:

> Thanks a lot pavlin,
> 
> Your comments are indeed very help full for me.
> 
> I could able to resolve the compilation issues. Following are my changes .
> 
> 1) --wiith-LD = mips-linux-ld
> 
> 2) CFLAGS = "mxgots" 
> 
> 3) CXXFLAGS = "mxgots"
> 
> 4) Enableing the PIMSM V1, PIMSM V2 and IPIP kernal modules.
> 
> With above changes i could able to run the xorp on my target board.
> 
> Through testing i found that it doesnot support immedieate leave , am i right ?

Typically there is few seconds latency when a receiver leaves a
multicast group, because of the way IGMP works.

> To  supports  this do i need change any thing in config.boot ?

Please see rtrmgr/config/multicast4.boot for a sample configuration
file for multicast routing. Also, see the XORP User Manual for
detail description of the configuration statements.

> How many minimum number of multicast groups it can support ?

I presume you mean "maximum" instead of "minimum".
I believe for Linux the default max. value is 20 groups (per
interface?).
See the MLD/IGMP and PIM-SM sections in the xorp/ERRATA file for
hints if you need to increase that number.

> Do we have any control like on the specific interface we can allow only the specific multicast range addresses ? 

Currently the only control is by specifying the group prefix per
static-rp or for the bootstrap mechanism.
Please add a feature request to Bugzilla for per-interface address
range control.

Regards,
Pavlin

> Please send your comments
> 
> regards
> Kanth
> 
> ________________________________
> From: Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU>
> To: RamaKanthVarala <varala_kanth at yahoo.com>
> Cc: Pavlin Radoslavov <pavlin at ICSI.Berkeley..EDU>; xorp-users at xorp.org
> Sent: Friday, 20 March, 2009 11:10:48 PM
> Subject: Re: [Xorp-users] compilation problmes with mips
> 
> Kanth,
> 
> Before I try to answer your questions I'd like to emphasize that if
> you want to use XORP for multicast routing, you MUST use PIM-SM
> (i.e., IGMP only is not enough).
> 
> RamaKanthVarala <varala_kanth at yahoo.com> wrote:
> 
> > Thanks pavlin,
> > 
> > 
> > Iam using the latest stable version 1.6 .
> > 
> > My testing environment is like below
> > 
> > Windows PC (server )====WAN ===> Fedor 8 Linux PC =====Private Lan ===> Windows PC (client/host)
> > 
> > When i compile the source with fedora 8 version i did not had any problems.
> > 
> > In linux pc iam using the iptables to give me the NAT functionality to windows PC .
> > 
> > In this when i compiled for fedora 8 and tested it , the video stream is received by the client PC from server PC in short it gave me the expected result .
> > 
> > As same like above now my target board with mips on it is between server and client instead of fedora Linux PC.
> > 
> > My intention is to get the same result what i got with the linux pc.I hope i can achive the same ..!
> > 
> > My basic obstacles till now is 
> > 
> > 
> > 1) Compilation problems in the BGP and FEA modules..?
> 
> The error you are seeing ("... is not a valid libtool object")
> doesn't indicate an obvious issue. Here are few things that you can
> try:
> * Start with a clean source and build tree
> 
> * Don't use parallel make like "gmake -j4" in case you are. You
>   could try "gmake -j1", but I think "-j1" is the default anyway.
> 
> * Double-check that your cross-compilation environment is setup
>   properly (e.g., try to cross-compile other software that you know
>   can be cross-compiled).
> 
> * Try using "--enable-static --disable-shared" argument to ./configure
> 
> * Try using older XORP release (e.g., XORP-1.5).
> 
> > 2) Do they really need to be compiled in order to use igmp ..?
> 
> For multicast you need (at least) the following processes/modules:
> fea/mfea, igmp, rib, fib2mrib, pim.
> 
> Depends on the setup, you might need some unicast routing protocols
> as well (unless all unicast routes are static and installed outside
> of XORP).
> 
> > 3) What are all the modules does igmp depend on ..?
> 
> igmp itself depends only on fea/mfea, but as I mentioned before you
> must run pim.
> 
> Regards,
> Pavlin
> 
> > Please put in your thoughts .
> > 
> > Thanks & Regards
> > Kanth
> > 
> > ________________________________
> > From: Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU>
> > To: RamaKanthVarala <varala_kanth at yahoo.com>
> > Cc: xorp-users at xorp.org
> > Sent: Tuesday, 17 March, 2009 10:40:25 PM
> > Subject: Re: [Xorp-users] compilation problmes with mips
> > 
> > RamaKanthVarala <varala_kanth at yahoo.com> wrote:
> > 
> > > Hello friends,
> > > 
> > > I want to use the xorp as igmp proxy.
> > 
> > Unfortunately you can't use XORP as IGMP proxy.
> > The IGMP implementation in XORP is the router-side, and it is used
> > in tandem with PIM-SM.
> > 
> > Re. the "libtool object" error below, what XORP version are you
> > using? The latest 1.6 release or the code from CVS?
> > 
> > Regards,
> > Pavlin
> > 
> > > I want to put this into one of my target board which has mips as its o.s.
> > > 
> > > I configured with options like host as mips-linux  and --with-openssl to corresponding package.
> > > 
> > > When  i make it i get the following error.
> > > 
> > > /bin/sh ../../../libtool --tag=CXX   --mode=link mips-linux-g++  -g -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe   -o libxorp_fibconfig.la  fibconfig_entry_get_click.lo fibconfig_entry_get_dummy.lo fibconfig_entry_get_iphelper.lo fibconfig_entry_get_netlink_socket.lo fibconfig_entry_get_routing_socket.lo fibconfig_entry_get_rtmv2.lo fibconfig_entry_observer_dummy.lo fibconfig_entry_observer_iphelper.lo fibconfig_entry_observer_netlink_socket.lo fibconfig_entry_observer_routing_socket.lo fibconfig_entry_observer_rtmv2.lo fibconfig_entry_parse_netlink_socket.lo fibconfig_entry_parse_routing_socket.lo fibconfig_entry_set_click.lo fibconfig_entry_set_dummy.lo fibconfig_entry_set_iphelper.lo fibconfig_entry_set_netlink_socket.lo fibconfig_entry_set_routing_socket..lo fibconfig_entry_set_rtmv2.lo fibconfig_forwarding_dummy.lo fibconfig_forwarding_proc_linux.lo
> > >  fibconfig_forwarding_solaris.lo fibconfig_forwarding_sysctl.lo fibconfig_forwarding_windows.lo fibconfig_table_get_click.lo fibconfig_table_get_dummy..lo fibconfig_table_get_iphelper.lo fibconfig_table_get_netlink_socket.lo fibconfig_table_get_sysctl.lo fibconfig_table_observer_dummy.lo fibconfig_table_observer_iphelper.lo fibconfig_table_observer_netlink_socket.lo fibconfig_table_observer_routing_socket.lo fibconfig_table_observer_rtmv2.lo fibconfig_table_parse_netlink_socket.lo fibconfig_table_parse_routing_socket.lo fibconfig_table_set_click.lo fibconfig_table_set_dummy.lo fibconfig_table_set_iphelper.lo fibconfig_table_set_netlink_socket.lo fibconfig_table_set_routing_socket.lo fibconfig_table_set_rtmv2..lo  -lcrypto  -L/root/SW/userapps/opensource/openssl -L/root/SW/userapps/opensource/openssl/lib -lrt
> > > libtool: link: `fibconfig_forwarding_proc_linux.lo' is not a valid libtool object
> > > make: *** [libxorp_fibconfig.la] Error 1
> > > 
> > > 
> > > Another general doubt is what are all the components needed for igmp to work ..
> > > 
> > > If i donot include fea and ospf does it work..?
> > > 
> > > Your help will be highly appreciated in this.
> > > 
> > > regards
> > > Kanth 
> > > ________________________________
> > > Add more friends to your messenger and enjoy! Invite them now.. 
> > > 
> > > 
> > >      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/_______________________________________________
> > > Xorp-users mailing list
> > > Xorp-users at xorp.org
> > > http://mailman.ICSI.Berkeley..EDU/mailman/listinfo/xorp-users
> > 
> > ________________________________
> > Download prohibited? No problem. CHAT from any browser, without download.
> > 
> > 
> >      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/_______________________________________________
> > Xorp-users mailing list
> > Xorp-users at xorp..org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> 
> 
> 
>      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/_______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


________________________________

From: Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU>
To: RamaKanthVarala <varala_kanth at yahoo.com>
Cc: Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU>; xorp-users at xorp.org
Sent: Sunday, 22 March, 2009 1:58:05 AM
Subject: Re: [Xorp-users] compilation problmes with mips



      Connect with friends all over the world. Get Yahoo! India Messenger at http://in.messenger.yahoo.com/?wm=n/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20090324/2e469178/attachment-0001.html 


More information about the Xorp-users mailing list