From thiago at g3informatica.com.br Tue Jan 10 05:56:11 2012 From: thiago at g3informatica.com.br (Thiago Anderson) Date: Tue, 10 Jan 2012 11:56:11 -0200 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: Message-ID: Cisco Linux 10.244.0.1/32 -------------------[ipsec]---------------------- 10.244.249.117 10.244.229.221/30 ---------------[ gre ] --------------------- 10.244.229.222/30 10.244.0.0/24 ------------------------------------------------------ 10.245.6.240/28 I have a tunnel as above, where gw ipsec - gw and a gre to pass multicast and unicast. Unicast is ok, and works through the normal conecoes tcp / ping. I'm trying to configure the XORP to be able to forward multicast but still unable to deliver the join the group through the GRE tunnel. Below is the configuration of the XORP: **** My home network is on eth2 and gre tunnel is named Bovespa **** rtrmgr { config-directory: "/etc/xorp" } interfaces { interface eth2 { description: "upstream interface" disable:false default-system-config vif eth2 { address 10.245.6.241 { prefix-length:28 multicast-capable: true } } } interface bovespa { description: "downstream interface" disable: false default-system-config vif bovespa { address 10.245.6.222 { prefix-length:30 multicast-capable: true } } } } plumbing { mfea4 { disable: false interface eth2 { vif eth2 { disable: false } } interface bovespa { vif bovespa { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface eth2 { vif eth2 { disable: false } } interface bovespa { vif bovespa { disable: false } } traceoptions { flag all { disable: false } } } pimsm4 { disable: false interface eth2 { vif eth2 { disable: false } } interface bovespa { vif bovespa { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } static-rps { rp 10.244.0.10 { group-prefix 233.111.180.96/27 { /* rp-priority: 192 */ } group-prefix 233.111.180.128/27 { /* rp-priority: 192 */ } } } bootstrap { disable: false cand-bsr { scope-zone 233.111.180.96/27 { cand-bsr-by-vif-name: "bovespa" bsr-priority: 1 hash-mask-len: 30 } } cand-rp { group-prefix 233.111.180.96/27 { cand-rp-by-vif-name: "bovespa" rp-priority: 192 rp-holdtime: 150 } } } traceoptions { flag all { disable: false } } } fib2mrib { disable: false } } ********************** root at gw> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout ********************** root at fw-neppo> show igmp group Interface Group Source LastReported Timeout V State eth2 233.111.180.97 0.0.0.0 10.245.6.242 198 2 E eth2 233.111.180.98 0.0.0.0 10.245.6.242 205 2 E eth2 233.111.180.99 0.0.0.0 10.245.6.242 201 2 E eth2 233.111.180.100 0.0.0.0 10.245.6.242 205 2 E Thank for replay. Thiago. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120110/06dc6056/attachment.html From greearb at candelatech.com Tue Jan 10 09:07:32 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Jan 2012 09:07:32 -0800 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: Message-ID: <4F0C7054.8000401@candelatech.com> On 01/10/2012 05:56 AM, Thiago Anderson wrote: > > Cisco Linux > 10.244.0.1/32 -------------------[ipsec]---------------------- 10.244.249.117 > 10.244.229.221/30 ---------------[ gre ] --------------------- 10.244.229.222/30 > 10.244.0.0/24 ------------------------------------------------------ 10.245.6.240/28 > > I have a tunnel as above, where gw ipsec - gw and a gre to pass multicast and unicast. > Unicast is ok, and works through the normal conecoes tcp / ping. > > I'm trying to configure the XORP to be able to forward multicast but still unable to deliver the join the group through the GRE tunnel. > > Below is the configuration of the XORP: Make sure you are using Xorp 1.8.5-WIP (HEAD tag from github). It fixes some bugs since the last release...I'll be doing a new official 1.8.5 release within the next week or two. Thanks, Ben > > **** My home network is on eth2 and gre tunnel is named Bovespa **** > > > rtrmgr { > config-directory: "/etc/xorp" > } > > interfaces { > interface eth2 { > description: "upstream interface" > disable:false > default-system-config > vif eth2 { > address 10.245.6.241 { > prefix-length:28 > multicast-capable: true > } > } > } > > interface bovespa { > description: "downstream interface" > disable: false > default-system-config > vif bovespa { > address 10.245.6.222 { > prefix-length:30 > multicast-capable: true > } > } > } > > } > > plumbing { > mfea4 { > disable: false > interface eth2 { > vif eth2 { > disable: false > } > } > > interface bovespa { > vif bovespa { > disable: false > } > } > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > disable: false > } > } > traceoptions { > flag all { > disable: false > } > } > } > } > protocols { > > igmp { > disable: false > interface eth2 { > vif eth2 { > disable: false > } > } > > interface bovespa { > vif bovespa { > disable: false > } > } > > traceoptions { > flag all { > disable: false > } > } > } > > pimsm4 { > disable: false > interface eth2 { > vif eth2 { > disable: false > } > } > > interface bovespa { > vif bovespa { > disable: false > } > } > > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > disable: false > } > } > > static-rps { > rp 10.244.0.10 { > group-prefix 233.111.180.96/27 { > /* rp-priority: 192 */ > } > group-prefix 233.111.180.128/27 { > /* rp-priority: 192 */ > } > } > } > > bootstrap { > disable: false > cand-bsr { > scope-zone 233.111.180.96/27 { > cand-bsr-by-vif-name: "bovespa" > bsr-priority: 1 > hash-mask-len: 30 > } > } > cand-rp { > group-prefix 233.111.180.96/27 { > cand-rp-by-vif-name: "bovespa" > rp-priority: 192 > rp-holdtime: 150 > } > } > } > > > traceoptions { > flag all { > disable: false > } > } > } > fib2mrib { > disable: false > } > } > > > ********************** > root at gw> show pim neighbors > Interface DRpriority NeighborAddr V Mode Holdtime Timeout > > > ********************** > > root at fw-neppo> show igmp group > Interface Group Source LastReported Timeout V State > eth2 233.111.180.97 0.0.0.0 10.245.6.242 198 2 E > eth2 233.111.180.98 0.0.0.0 10.245.6.242 205 2 E > eth2 233.111.180.99 0.0.0.0 10.245.6.242 201 2 E > eth2 233.111.180.100 0.0.0.0 10.245.6.242 205 2 E > > > Thank for replay. > > Thiago. > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From thiago at g3informatica.com.br Tue Jan 10 10:23:37 2012 From: thiago at g3informatica.com.br (Thiago Anderson) Date: Tue, 10 Jan 2012 16:23:37 -0200 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: <4F0C7054.8000401@candelatech.com> References: <4F0C7054.8000401@candelatech.com> Message-ID: Ben, Thz for reply... i try to compile and get errors: # git clone git://github.com/greearb/xorp.ct.git # cd xorp.ct/xorp # scons You will also want to edit similar code around line 282 of: /usr/include/linux/netfilter_ipv6/ip6_tables.h NOTE: Recent kernels use struct xt_entry_target for the argument for these methods, so use that instead of ipt_entry_target if that is the case for your system. Checking for C library curses... yes Checking for C library pdcurses... no Checking for C library ncurses... yes Detected libraries: rt resolv crypto dl pcap curses ncurses Mkdir("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib") Mkdir("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib/xorp") Symlink("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib", as "/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib/xorp/lib") scons: warning: Two different environments were specified for target aspath.os, but they appear to have the same action: $SHCXX -o $TARGET -c $SHCXXFLAGS $SHCCFLAGS $_CCCOMCOM $SOURCES File "/usr/src/xorp.ct/xorp/bgp/SConscript", line 169, in scons: done reading SConscript files. scons: Building targets ... scons: Configure: creating obj/i686-pc-linux-gnu/xorp_config.h g++ -o obj/i686-pc-linux-gnu/cli/tools/cli_generic.o -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -DXRL_PF=120 -DXORP_VERSION=1.8.5-WIP -D_FORTIFY_SOURCE=0 -Iobj/i686-pc-linux-gnu -I. -I. cli/tools/cli_generic.cc :0:0: error: "_FORTIFY_SOURCE" redefined [-Werror] :0:0: note: this is the location of the previous definition cc1plus: all warnings being treated as errors scons: *** [obj/i686-pc-linux-gnu/cli/tools/cli_generic.o] Error 1 scons: building terminated because of errors. Help? Thiago 2012/1/10 Ben Greear > On 01/10/2012 05:56 AM, Thiago Anderson wrote: > >> >> Cisco Linux >> 10.244.0.1/32 -------------------[ipsec]----**------------------ >> 10.244.249.117 >> 10.244.229.221/30 ---------------[ gre ] >> --------------------- 10.244.229.222/30 >> 10.244.0.0/24 ------------------------------**------------------------ >> 10.245.6.240/28 >> >> >> I have a tunnel as above, where gw ipsec - gw and a gre to pass multicast >> and unicast. >> Unicast is ok, and works through the normal conecoes tcp / ping. >> >> I'm trying to configure the XORP to be able to forward multicast but >> still unable to deliver the join the group through the GRE tunnel. >> >> Below is the configuration of the XORP: >> > > Make sure you are using Xorp 1.8.5-WIP (HEAD tag from github). It fixes > some bugs since the last release...I'll be doing a new official 1.8.5 > release > within the next week or two. > > Thanks, > Ben > > >> **** My home network is on eth2 and gre tunnel is named Bovespa **** >> >> >> rtrmgr { >> config-directory: "/etc/xorp" >> } >> >> interfaces { >> interface eth2 { >> description: "upstream interface" >> disable:false >> default-system-config >> vif eth2 { >> address 10.245.6.241 { >> prefix-length:28 >> multicast-capable: true >> } >> } >> } >> >> interface bovespa { >> description: "downstream interface" >> disable: false >> default-system-config >> vif bovespa { >> address 10.245.6.222 { >> prefix-length:30 >> multicast-capable: true >> } >> } >> } >> >> } >> >> plumbing { >> mfea4 { >> disable: false >> interface eth2 { >> vif eth2 { >> disable: false >> } >> } >> >> interface bovespa { >> vif bovespa { >> disable: false >> } >> } >> interface register_vif { >> vif register_vif { >> /* Note: this vif should be always enabled */ >> disable: false >> } >> } >> traceoptions { >> flag all { >> disable: false >> } >> } >> } >> } >> protocols { >> >> igmp { >> disable: false >> interface eth2 { >> vif eth2 { >> disable: false >> } >> } >> >> interface bovespa { >> vif bovespa { >> disable: false >> } >> } >> >> traceoptions { >> flag all { >> disable: false >> } >> } >> } >> >> pimsm4 { >> disable: false >> interface eth2 { >> vif eth2 { >> disable: false >> } >> } >> >> interface bovespa { >> vif bovespa { >> disable: false >> } >> } >> >> interface register_vif { >> vif register_vif { >> /* Note: this vif should be always enabled */ >> disable: false >> } >> } >> >> static-rps { >> rp 10.244.0.10 { >> group-prefix 233.111.180.96/27 { >> /* rp-priority: 192 */ >> } >> group-prefix 233.111.180.128/27 { >> >> /* rp-priority: 192 */ >> } >> } >> } >> >> bootstrap { >> disable: false >> cand-bsr { >> scope-zone 233.111.180.96/27 { >> >> cand-bsr-by-vif-name: "bovespa" >> bsr-priority: 1 >> hash-mask-len: 30 >> } >> } >> cand-rp { >> group-prefix 233.111.180.96/27 { >> >> cand-rp-by-vif-name: "bovespa" >> rp-priority: 192 >> rp-holdtime: 150 >> } >> } >> } >> >> >> traceoptions { >> flag all { >> disable: false >> } >> } >> } >> fib2mrib { >> disable: false >> } >> } >> >> >> ********************** >> root at gw> show pim neighbors >> Interface DRpriority NeighborAddr V Mode Holdtime Timeout >> >> >> ********************** >> >> root at fw-neppo> show igmp group >> Interface Group Source LastReported Timeout V State >> eth2 233.111.180.97 0.0.0.0 10.245.6.242 198 2 E >> eth2 233.111.180.98 0.0.0.0 10.245.6.242 205 2 E >> eth2 233.111.180.99 0.0.0.0 10.245.6.242 201 2 E >> eth2 233.111.180.100 0.0.0.0 10.245.6.242 205 2 E >> >> >> Thank for replay. >> >> Thiago. >> >> >> >> ______________________________**_________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.**EDU/mailman/listinfo/xorp-**users >> > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120110/0c757f1f/attachment-0001.html From greearb at candelatech.com Tue Jan 10 10:38:36 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Jan 2012 10:38:36 -0800 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: <4F0C7054.8000401@candelatech.com> Message-ID: <4F0C85AC.7070106@candelatech.com> On 01/10/2012 10:23 AM, Thiago Anderson wrote: > Ben, > > Thz for reply... > > i try to compile and get errors: > > # git clone git://github.com/greearb/xorp.ct.git > # cd xorp.ct/xorp > # scons > > You will also want to edit similar code around line 282 of: > /usr/include/linux/netfilter_ipv6/ip6_tables.h > NOTE: Recent kernels use struct xt_entry_target for the argument > for these methods, so use that instead of ipt_entry_target if that > is the case for your system. > Checking for C library curses... yes > Checking for C library pdcurses... no > Checking for C library ncurses... yes > Detected libraries: rt resolv crypto dl pcap curses ncurses > Mkdir("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib") > Mkdir("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib/xorp") > Symlink("/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib", as "/usr/src/xorp.ct/xorp/obj/i686-pc-linux-gnu/lib/xorp/lib") > > scons: warning: Two different environments were specified for target aspath.os, > but they appear to have the same action: $SHCXX -o $TARGET -c $SHCXXFLAGS $SHCCFLAGS $_CCCOMCOM $SOURCES > File "/usr/src/xorp.ct/xorp/bgp/SConscript", line 169, in > scons: done reading SConscript files. > scons: Building targets ... > scons: Configure: creating obj/i686-pc-linux-gnu/xorp_config.h > g++ -o obj/i686-pc-linux-gnu/cli/tools/cli_generic.o -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align -Woverloaded-virtual > -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -DXRL_PF=120 -DXORP_VERSION=1.8.5-WIP -D_FORTIFY_SOURCE=0 -Iobj/i686-pc-linux-gnu -I. -I. cli/tools/cli_generic.cc > :0:0: error: "_FORTIFY_SOURCE" redefined [-Werror] > :0:0: note: this is the location of the previous definition > cc1plus: all warnings being treated as errors > > scons: *** [obj/i686-pc-linux-gnu/cli/tools/cli_generic.o] Error 1 > scons: building terminated because of errors. > > > Help? Someone else reported this. Must be something to do with the latest Ubuntu. Try commenting this code out of the SConstruct file. I'm not sure why this was added in the first place... # Forcibly disable GCC's SSP support., as it may be incompatible # with the XORP code base. env.AppendUnique(CPPDEFINES = [ ( '_FORTIFY_SOURCE', 0 ), ]) Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From thiago at g3informatica.com.br Tue Jan 10 10:51:35 2012 From: thiago at g3informatica.com.br (Thiago Anderson) Date: Tue, 10 Jan 2012 16:51:35 -0200 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: <4F0C85AC.7070106@candelatech.com> References: <4F0C7054.8000401@candelatech.com> <4F0C85AC.7070106@candelatech.com> Message-ID: Ben, another erros reports: gcc -o obj/i686-pc-linux-gnu/libxorp/daemon.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-prototypes -Wcast-qual -Wmissing-declarations -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -pipe -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5-WIP -Iobj/i686-pc-linux-gnu -I. -I. libxorp/daemon.c libxorp/daemon.c: In function ?xorp_daemonize?: libxorp/daemon.c:92:3: error: ignoring return value of ?chdir?, declared with attribute warn_unused_result [-Werror=unused-result] cc1: all warnings being treated as errors scons: *** [obj/i686-pc-linux-gnu/libxorp/daemon.os] Error 1 scons: building terminated because of errors. root at fw-neppo:/usr/src/xorp.ct/xorp# Thiago. 2012/1/10 Ben Greear > On 01/10/2012 10:23 AM, Thiago Anderson wrote: > >> Ben, >> >> Thz for reply... >> >> i try to compile and get errors: >> >> # git clone git://github.com/greearb/xorp.**ct.git< >> http://github.com/greearb/**xorp.ct.git >> > >> >> # cd xorp.ct/xorp >> # scons >> >> You will also want to edit similar code around line 282 of: >> /usr/include/linux/netfilter_**ipv6/ip6_tables.h >> NOTE: Recent kernels use struct xt_entry_target for the argument >> for these methods, so use that instead of ipt_entry_target if that >> is the case for your system. >> Checking for C library curses... yes >> Checking for C library pdcurses... no >> Checking for C library ncurses... yes >> Detected libraries: rt resolv crypto dl pcap curses ncurses >> Mkdir("/usr/src/xorp.ct/xorp/**obj/i686-pc-linux-gnu/lib") >> Mkdir("/usr/src/xorp.ct/xorp/**obj/i686-pc-linux-gnu/lib/**xorp") >> Symlink("/usr/src/xorp.ct/**xorp/obj/i686-pc-linux-gnu/**lib", as >> "/usr/src/xorp.ct/xorp/obj/**i686-pc-linux-gnu/lib/xorp/**lib") >> >> scons: warning: Two different environments were specified for target >> aspath.os, >> but they appear to have the same action: $SHCXX -o $TARGET -c >> $SHCXXFLAGS $SHCCFLAGS $_CCCOMCOM $SOURCES >> File "/usr/src/xorp.ct/xorp/bgp/**SConscript", line 169, in >> scons: done reading SConscript files. >> scons: Building targets ... >> scons: Configure: creating obj/i686-pc-linux-gnu/xorp_**config.h >> g++ -o obj/i686-pc-linux-gnu/cli/**tools/cli_generic.o -c -O2 -g3 >> -Werror -W -Wall -Wwrite-strings -Wcast-qual -Wpointer-arith -Wcast-align >> -Woverloaded-virtual >> -ftemplate-depth-25 -pipe -DXORP_BUILDINFO -DXRL_PF=120 >> -DXORP_VERSION=1.8.5-WIP -D_FORTIFY_SOURCE=0 -Iobj/i686-pc-linux-gnu -I. >> -I. cli/tools/cli_generic.cc >> :0:0: error: "_FORTIFY_SOURCE" redefined [-Werror] >> :0:0: note: this is the location of the previous definition >> cc1plus: all warnings being treated as errors >> >> scons: *** [obj/i686-pc-linux-gnu/cli/**tools/cli_generic.o] Error 1 >> scons: building terminated because of errors. >> >> >> Help? >> > > Someone else reported this. Must be something to do with the latest > Ubuntu. > > Try commenting this code out of the SConstruct file. I'm not > sure why this was added in the first place... > > # Forcibly disable GCC's SSP support., as it may be incompatible > # with the XORP code base. > env.AppendUnique(CPPDEFINES = [ > ( '_FORTIFY_SOURCE', 0 ), > ]) > > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120110/8cb83fa1/attachment.html From greearb at candelatech.com Tue Jan 10 11:20:51 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Jan 2012 11:20:51 -0800 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: <4F0C7054.8000401@candelatech.com> <4F0C85AC.7070106@candelatech.com> Message-ID: <4F0C8F93.3000208@candelatech.com> On 01/10/2012 10:51 AM, Thiago Anderson wrote: > Ben, > > another erros reports: > gcc -o obj/i686-pc-linux-gnu/libxorp/daemon.os -c -O2 -g3 -Werror -W -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-prototypes -Wcast-qual > -Wmissing-declarations -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -pipe -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5-WIP > -Iobj/i686-pc-linux-gnu -I. -I. libxorp/daemon.c > libxorp/daemon.c: In function ?xorp_daemonize?: > libxorp/daemon.c:92:3: error: ignoring return value of ?chdir?, declared with attribute warn_unused_result [-Werror=unused-result] > cc1: all warnings being treated as errors > > scons: *** [obj/i686-pc-linux-gnu/libxorp/daemon.os] Error 1 > scons: building terminated because of errors. > root at fw-neppo:/usr/src/xorp.ct/xorp# I'm going to install a Ubuntu 11.10 version now and get Xorp building there. Will be a few hours at least.... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From thiago at g3informatica.com.br Tue Jan 10 11:43:15 2012 From: thiago at g3informatica.com.br (Thiago Anderson) Date: Tue, 10 Jan 2012 17:43:15 -0200 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: <4F0C8F93.3000208@candelatech.com> References: <4F0C7054.8000401@candelatech.com> <4F0C85AC.7070106@candelatech.com> <4F0C8F93.3000208@candelatech.com> Message-ID: Ok, Thx. Thiago 2012/1/10 Ben Greear > On 01/10/2012 10:51 AM, Thiago Anderson wrote: > >> Ben, >> >> another erros reports: >> gcc -o obj/i686-pc-linux-gnu/libxorp/**daemon.os -c -O2 -g3 -Werror -W >> -Wall -Wwrite-strings -Wbad-function-cast -Wmissing-prototypes -Wcast-qual >> -Wmissing-declarations -Wpointer-arith -Wcast-align -Wstrict-prototypes >> -Wnested-externs -pipe -fPIC -DXRL_PF=120 -DXORP_VERSION=1.8.5-WIP >> -Iobj/i686-pc-linux-gnu -I. -I. libxorp/daemon.c >> libxorp/daemon.c: In function ?xorp_daemonize?: >> libxorp/daemon.c:92:3: error: ignoring return value of ?chdir?, declared >> with attribute warn_unused_result [-Werror=unused-result] >> >> cc1: all warnings being treated as errors >> >> scons: *** [obj/i686-pc-linux-gnu/**libxorp/daemon.os] Error 1 >> scons: building terminated because of errors. >> root at fw-neppo:/usr/src/xorp.**ct/xorp# >> > > I'm going to install a Ubuntu 11.10 version now and get Xorp building > there. > Will be a few hours at least.... > > > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120110/c06dfa33/attachment.html From greearb at candelatech.com Tue Jan 10 13:01:33 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Jan 2012 13:01:33 -0800 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: <4F0C7054.8000401@candelatech.com> <4F0C85AC.7070106@candelatech.com> <4F0C8F93.3000208@candelatech.com> Message-ID: <4F0CA72D.7040201@candelatech.com> On 01/10/2012 11:43 AM, Thiago Anderson wrote: > Ok, > > Thx. > Please pull the latest and see how it works for you. It compiles on Ubuntu 11.10 for me now. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From thiago at g3informatica.com.br Tue Jan 10 18:34:54 2012 From: thiago at g3informatica.com.br (Thiago Anderson) Date: Wed, 11 Jan 2012 00:34:54 -0200 Subject: [Xorp-users] Multicast over GRE tunnel between Cisco and Ubuntu 11.10 In-Reply-To: References: <4F0C7054.8000401@candelatech.com> <4F0C85AC.7070106@candelatech.com> <4F0C8F93.3000208@candelatech.com> <4F0CA72D.7040201@candelatech.com> Message-ID: Ben, Thanks for helping the tunnel is booming .... hehehe multicast is ok ... to anyone who want the setup done .... follows... So details for the tunnel is a gre ipsec with: Configuring ipsec with openswan: conn tunnel00 type=tunnel connaddrfamily=ipv4 authby= secret left=your_net_ip leftnexthop=your_net_gw leftsubnet=ip_linux/32 leftsourceip=source_ip rightsourceip=ip_cisco/32 right=ip_cisco_net rightsubnet=ip_cisco/32 ike=3des-md5,3des-sha-modp1024 phase2alg=3des-md5-96,3des-sha1 keyexchange=ike pfs=no auto=add rightid=ip_cisco_net leftid=your_net_ip GRE tunnel configuration: modprobe ip_gre ip tu ad gre00 mode gre local ip_linux/32 remote ip_cisco/32 dev internet_eth ip ad ad dev gre00 ip_gre_linux peer ip_gre_cisco/30 ip li se dev gre00 up ifconfig gre00 multicast XORP configuration, installed from github: eth2 is the network interface gre00 is the gre tunnel protocols { igmp { interface gre00 { vif gre00 { query-interval: 30 } } interface eth2 { vif eth2 { } } } pimsm4 { interface "register_vif" { vif "register_vif" { } } interface eth2 { vif eth2 { } } interface gre00 { vif gre00 { } } static-rps { rp ip_rp { group-prefix MULTICAST_GROUP/MASK { } } } } static { /*route 0.0.0.0/0 { next-hop: ip_linux_net_gw }*/ mrib-route 0.0.0.0/0 { next-hop: ip_gre_cisco /* tunnel */ } } } fea { unicast-forwarding4 { } } interfaces { interface eth2 { default-system-config vif eth2 { address IP_INTERFACE_ETH2 { prefix-length: MASK } } } interface lo { vif lo { } } interface gre00 { default-system-config vif gre00 { address ip_gre_linux { prefix-length: 30 multicast-capable: true } } } } plumbing { mfea4 { interface eth2 { vif eth2 { } } interface "register_vif" { vif "register_vif" { } } interface gre00 { vif gre00 { } } } } Thanks for everything once again, was about changing my fw linux for a cisco router ... :) Thiago Anderson 2012/1/10 Thiago Anderson > Hello, Ben > > Thank you I am testing and put the return. > > Thank you, > > Thiago > > > 2012/1/10 Ben Greear > >> On 01/10/2012 11:43 AM, Thiago Anderson wrote: >> >>> Ok, >>> >>> Thx. >>> >>> >> Please pull the latest and see how it works for you. It compiles >> on Ubuntu 11.10 for me now. >> >> Thanks, >> >> Ben >> >> -- >> Ben Greear >> Candela Technologies Inc http://www.candelatech.com >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120111/5e8c97d2/attachment.html From andriysenkovych at gmail.com Wed Jan 11 03:34:00 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Wed, 11 Jan 2012 13:34:00 +0200 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: <4EFB37FD.6010408@candelatech.com> References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> Message-ID: Hello, Ben 2011/12/28 Ben Greear : I have built the last HEAD yesterday (together with yesterday fixes) on Debian box successfully. This problem is fixed, however another one appeared. If you try to use xorpsh more than once(log in to xorpsh and logout), xorp_rtrmgr will hang in an endless loop with the following output found with strace(lots of similar lines): poll([{fd=45, events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 1, -1) = 1 ([{fd=45, revents=POLLIN|POLLERR|POLLHUP}]) -- WBR, Andriy Senkovych From greearb at candelatech.com Wed Jan 11 09:16:20 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 09:16:20 -0800 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> Message-ID: <4F0DC3E4.2080906@candelatech.com> On 01/11/2012 03:34 AM, Andriy Senkovych wrote: > Hello, Ben > > 2011/12/28 Ben Greear: > > I have built the last HEAD yesterday (together with yesterday fixes) > on Debian box successfully. This problem is fixed, however another one > appeared. > If you try to use xorpsh more than once(log in to xorpsh and logout), > xorp_rtrmgr will hang in an endless loop with the following output > found with strace(lots of similar lines): > > poll([{fd=45, events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 1, -1) = 1 > ([{fd=45, revents=POLLIN|POLLERR|POLLHUP}]) > Please let me know exactly how you reproduce this, and please send the xorp logs for your system when the problem happens. How repeatable is the problem for you? The latest code seems to be working for me. [root at lec2010-ath9k-1 lanforge]# xorpsh Welcome to XORP v1.8.5-WIP on lec2010-ath9k-1 Version tag: 0757adb Build Date: 2012-01-10 17:22 32-bit root at lec2010-ath9k-1> show ospf4 ver Not a XORP command! root at lec2010-ath9k-1> show ospf4 ^ syntax error, expecting `database', or `neighbor'. root at lec2010-ath9k-1> show ospf4 neighbor Address Interface State ID Pri Dead 12.3.3.3 rddVR3/rddVR3 Full 127.1.0.3 128 34 root at lec2010-ath9k-1> exit [root at lec2010-ath9k-1 lanforge]# xorpsh Welcome to XORP v1.8.5-WIP on lec2010-ath9k-1 Version tag: 0757adb Build Date: 2012-01-10 17:22 32-bit root at lec2010-ath9k-1> show ospf4 neighbor Address Interface State ID Pri Dead 12.3.3.3 rddVR3/rddVR3 Full 127.1.0.3 128 28 root at lec2010-ath9k-1> quit [root at lec2010-ath9k-1 lanforge]# Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From andriysenkovych at gmail.com Wed Jan 11 09:16:54 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Wed, 11 Jan 2012 19:16:54 +0200 Subject: [Xorp-users] Xorp is not visible as neighbor for Cisco router Message-ID: Dear xorp-users, I'm stuck in configuring PIM-SM between Cisco router and Xorp. The initial configuration is the same as in my previous thread [1]. The problem is that I do discover the neighbor Cisco router, but the other side don't see me as a neighbor. I also tried the configuration from the neighbor thread [2] which didn't work either. Thank you in advance. [1]: http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2011-December/004634.html [2]: http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2012-January/004648.html -- WBR, Andriy Senkovych From greearb at candelatech.com Wed Jan 11 09:27:33 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 09:27:33 -0800 Subject: [Xorp-users] Xorp is not visible as neighbor for Cisco router In-Reply-To: References: Message-ID: <4F0DC685.1090803@candelatech.com> On 01/11/2012 09:16 AM, Andriy Senkovych wrote: > Dear xorp-users, > > I'm stuck in configuring PIM-SM between Cisco router and Xorp. The > initial configuration is the same as in my previous thread [1]. The > problem is that I do discover the neighbor Cisco router, but the other > side don't see me as a neighbor. I also tried the configuration from > the neighbor thread [2] which didn't work either. You are using the latest xorp code (1.8.5-WIP) now? Please always mention the version you are using, and post your config files. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From andriysenkovych at gmail.com Wed Jan 11 15:09:17 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Thu, 12 Jan 2012 01:09:17 +0200 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: <4F0DC3E4.2080906@candelatech.com> References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> <4F0DC3E4.2080906@candelatech.com> Message-ID: Hello, Ben. 2012/1/11 Ben Greear : > Please let me know exactly how you reproduce this, and please send the > xorp logs for your system when the problem happens. How repeatable is the > problem for you? The latest code seems to be working for me. Here is the way how I reproduce this: # invoke-rc.d xorp start Starting eXtensible Open Router Platform : xorp. # xorpsh Welcome to XORP v1.8.5-WIP on cmegw Version tag: 00000000 Build Date: 2012-01-11 00:01 32-bit root at cmegw> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout cme-gw 1 10.145.2.221 2 Sparse 105 98 root at cmegw> (Push Ctrl+D) End of connection. # sleep 60 # xorpsh (Hangs here, uses all CPU resources) I can reproduce this almost all the time. Interesting thing: If I omit sleep command and run xorpsh right after startup then I cannot reproduce the bug for some time. There is no difference wether I exit with EOF or with "quit" command. Startup logs and configuration file can be found on https://gist.github.com/1597298 Xorp information: Revision: 0757adb64f4aaabce7abff7b7ec9b624ec07bf7b Revision Date: Tue Jan 10 13:00:36 2012 -0800 Information about build environment and running environment: Debian Release: 6.0.3(squeeze/stable) Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of libraries' packages xorp was built against: libboost-dev 1.42.0.1 libboost1.42-dev 1.42.0-4 libncurses5-dev 5.7+20100313-5 libpcap0.8-dev 1.1.1-2+squeeze1 libssl-dev 0.9.8o-4squeeze3 zlib1g-dev 1%3a1.2.3.4.dfsg-3 Versions of packages xorp depends on: ii adduser 3.112+nmu2 ii libc6 2.13-23 ii libgcc1 1:4.6.2-9 ii libncurses5 5.7+20100313-5 ii libpcap0.8 1.1.1-2+squeeze1 ii libssl0.9.8 0.9.8o-4squeeze4 ii libstdc++6 4.6.2-9 Versions of packages xorp recommends: ii iputils-ping 3:20100418-3 ii iputils-tracepath ii traceroute 1:2.0.15-1 -- WBR, Andriy Senkovych From andriysenkovych at gmail.com Wed Jan 11 15:17:36 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Thu, 12 Jan 2012 01:17:36 +0200 Subject: [Xorp-users] Xorp is not visible as neighbor for Cisco router In-Reply-To: <4F0DC685.1090803@candelatech.com> References: <4F0DC685.1090803@candelatech.com> Message-ID: Ben, > You are using the latest xorp code (1.8.5-WIP) now? > > Please always mention the version you are using, and post your > config files. Sorry, I'll do so in my future mails. Right, I'm using 1.8.5-WIP, the environment and the setup is the same as in [1,2,3]. [1]: http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2012-January/004653.html [2]: http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2011-December/004634.html [3]: https://gist.github.com/1597298 -- WBR, Andriy Senkovych From greearb at candelatech.com Wed Jan 11 15:23:56 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 15:23:56 -0800 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> <4F0DC3E4.2080906@candelatech.com> Message-ID: <4F0E1A0C.9010408@candelatech.com> On 01/11/2012 03:09 PM, Andriy Senkovych wrote: > Hello, Ben. > > 2012/1/11 Ben Greear: >> Please let me know exactly how you reproduce this, and please send the >> xorp logs for your system when the problem happens. How repeatable is the >> problem for you? The latest code seems to be working for me. > > Here is the way how I reproduce this: > > # invoke-rc.d xorp start > Starting eXtensible Open Router Platform : xorp. > # xorpsh > Welcome to XORP v1.8.5-WIP on cmegw > Version tag: 00000000 Build Date: 2012-01-11 00:01 32-bit > root at cmegw> show pim neighbors > Interface DRpriority NeighborAddr V Mode Holdtime Timeout > cme-gw 1 10.145.2.221 2 Sparse 105 98 > root at cmegw> > (Push Ctrl+D) > End of connection. > # sleep 60 > # xorpsh > (Hangs here, uses all CPU resources) xorpsh is using all resources, or some other process? If xorpsh, can you start xorpsh in another terminal and have it work as normal? > I can reproduce this almost all the time. Interesting thing: If I omit > sleep command and run xorpsh right after startup then I cannot > reproduce the bug for some time. There is no difference wether I exit > with EOF or with "quit" command. Ok, I'll see if I can reproduce that on my system. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Wed Jan 11 15:40:45 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 15:40:45 -0800 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> <4F0DC3E4.2080906@candelatech.com> Message-ID: <4F0E1DFD.8010908@candelatech.com> On 01/11/2012 03:09 PM, Andriy Senkovych wrote: > Hello, Ben. > > 2012/1/11 Ben Greear: >> Please let me know exactly how you reproduce this, and please send the >> xorp logs for your system when the problem happens. How repeatable is the >> problem for you? The latest code seems to be working for me. > > Here is the way how I reproduce this: > > # invoke-rc.d xorp start > Starting eXtensible Open Router Platform : xorp. > # xorpsh > Welcome to XORP v1.8.5-WIP on cmegw > Version tag: 00000000 Build Date: 2012-01-11 00:01 32-bit > root at cmegw> show pim neighbors > Interface DRpriority NeighborAddr V Mode Holdtime Timeout > cme-gw 1 10.145.2.221 2 Sparse 105 98 > root at cmegw> > (Push Ctrl+D) > End of connection. > # sleep 60 > # xorpsh > (Hangs here, uses all CPU resources) > > I can reproduce this almost all the time. Interesting thing: If I omit > sleep command and run xorpsh right after startup then I cannot > reproduce the bug for some time. There is no difference wether I exit > with EOF or with "quit" command. It worked for me 3 times in a row...maybe there is something special about your system or configuration that causes it to happen on your system and not on mine. Is the 60 seconds magic? In other words, does it (almost?) always work at 50 seconds and 70 seconds but fail at 60?) I don't see any obvious problem in your logs. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From andriysenkovych at gmail.com Wed Jan 11 15:43:56 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Thu, 12 Jan 2012 01:43:56 +0200 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: <4F0E1A0C.9010408@candelatech.com> References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> <4F0DC3E4.2080906@candelatech.com> <4F0E1A0C.9010408@candelatech.com> Message-ID: 2012/1/12 Ben Greear : > On 01/11/2012 03:09 PM, Andriy Senkovych wrote: >> >> Hello, Ben. >> >> 2012/1/11 Ben Greear: >>> >>> Please let me know exactly how you reproduce this, and please send the >>> xorp logs for your system when the problem happens. ?How repeatable is >>> the >>> problem for you? ?The latest code seems to be working for me. >> >> >> Here is the way how I reproduce this: >> >> # invoke-rc.d xorp start >> Starting eXtensible Open Router Platform : xorp. >> # xorpsh >> Welcome to XORP v1.8.5-WIP on cmegw >> Version tag: 00000000 ?Build Date: 2012-01-11 00:01 32-bit >> root at cmegw> ?show pim neighbors >> Interface ? ?DRpriority NeighborAddr ? ?V Mode ? Holdtime Timeout >> cme-gw ? ? ? ? ? ? ? ?1 10.145.2.221 ? ?2 Sparse ? ? ?105 ? ? ?98 >> root at cmegw> >> (Push Ctrl+D) >> End of connection. >> # sleep 60 >> # xorpsh >> (Hangs here, uses all CPU resources) > > > xorpsh is using all resources, or some other process? > > If xorpsh, can you start xorpsh in another terminal and have it work as > normal? Sorry, I wasn't clear on this point in my message. /usr/sbin/xorp_rtrmgr starts to use all resources. Htop shows that huge amount of system load goes on the kernel. The strace messages which appear I have shown already. > It worked for me 3 times in a row...maybe there is something special about > your system or configuration that causes it to happen on your system > and not on mine. > Is the 60 seconds magic? In other words, does it (almost?) always work at 50 seconds and 70 seconds > but fail at 60?) It's not magic but a measure of "some long time you cannot seat before terminal and do nothing". -- WBR, Andriy Senkovych From greearb at candelatech.com Wed Jan 11 17:36:17 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 17:36:17 -0800 Subject: [Xorp-users] XORP version 1.8.5 is released. Message-ID: <4F0E3911.5090107@candelatech.com> This release fixes some major bugs with OSPF and GRE. Highlights are below: Release 1.8.5 * Fix bad OSPF bug that made neighbours very slow to go to Full state in large and/or lossy OSPF router configurations. Thanks to Iqor for access to test systems and for funding this effort. * Compile in build-information to better track versions in logs and bug reports. * Optimize logging to check the log level before doing the work to create the logging messages. Simplify a lot of the related code. Runtime should be faster, but executable size is slightly larger. * netbsd: Fix compile on netbsd, properly detect IPv6 Multicast routing support, fix a few bugs related to multicast. It *might* work now, but seeing spurious failures when trying the MRT6_ADD_MIF call. Thanks to Uwe <6bone at 6bone.informatik.uni-leipzig.de> for access to netbsd boxes and testing work. * Fix multicast over GRE tunnels. Anything else over GRE also has a chance to work now. Thanks to J G Miller for bug reporting and testing. * ARM: Fix raw-sockets on some ARM platforms. The scons checks were lame at best. They are still suspect, but now unknown will be treated as supporting IPV4 raw input/output. If we find other systems that do NOT support this (freebsd, netbsd??), we can update the scons accordingly and/or find a way to do the detection more proper. Thanks to J G Miller for doing tests on his ARM box. * Fix compile on Ubuntu 11.10 (and perhaps other recent systems). Please follow the various links at www.xorp.org for full release notes, binary downloads, source-code, etc. Please post to the list if you notice any problems. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Wed Jan 11 17:43:18 2012 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Jan 2012 17:43:18 -0800 Subject: [Xorp-users] Wrong IP address used for GRE interface In-Reply-To: References: <4EFB2731.7010905@candelatech.com> <4EFB37FD.6010408@candelatech.com> <4F0DC3E4.2080906@candelatech.com> <4F0E1A0C.9010408@candelatech.com> Message-ID: <4F0E3AB6.9090603@candelatech.com> On 01/11/2012 03:43 PM, Andriy Senkovych wrote: > 2012/1/12 Ben Greear: >>> Here is the way how I reproduce this: >>> >>> # invoke-rc.d xorp start >>> Starting eXtensible Open Router Platform : xorp. >>> # xorpsh >>> Welcome to XORP v1.8.5-WIP on cmegw >>> Version tag: 00000000 Build Date: 2012-01-11 00:01 32-bit >>> root at cmegw> show pim neighbors >>> Interface DRpriority NeighborAddr V Mode Holdtime Timeout >>> cme-gw 1 10.145.2.221 2 Sparse 105 98 >>> root at cmegw> >>> (Push Ctrl+D) >>> End of connection. >>> # sleep 60 >>> # xorpsh >>> (Hangs here, uses all CPU resources) For completeness: Andriy was able to give me access to his system, and we determined that the hang was in ldap library code. He disabled ldap and the busy-spin poll() problem went away. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From keshavsrinu at gmail.com Mon Jan 16 03:07:05 2012 From: keshavsrinu at gmail.com (kesava Srinivas) Date: Mon, 16 Jan 2012 16:37:05 +0530 Subject: [Xorp-users] XORP for Static Multicast Routing ?? Message-ID: HI All, Does XORP Supports Static Multicast Routing?? If so; Would request to Please Share Configuration for it! Have been using smcroute previously to do this Job. Now; we are shifting to xorp for support of both Static & Dynamic Multicast Routing.Can both of them be achieved with XORP at a same time ?? Ex: Multicast Packets destined for coming from to be destined to Looking forward for the reply ! -Best Regards, VKS -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120116/4f30cced/attachment.html From andriysenkovych at gmail.com Tue Jan 17 06:15:15 2012 From: andriysenkovych at gmail.com (Andriy Senkovych) Date: Tue, 17 Jan 2012 16:15:15 +0200 Subject: [Xorp-users] Xorp is not visible as neighbor for Cisco router In-Reply-To: References: <4F0DC685.1090803@candelatech.com> Message-ID: Hello, Ben Just to clarify: do I correctly understant that in order to detect PIM neighbor this cisco router should just receive PIM_HELLO on the correct interface(e.g. over gre tunnel in my case)? I used tcpdump to track outgoung packets and founfd that I do send PIM_HELLO packets. In other words, is it enough to receive PIM_HELLO message to detect PIM neighbor? -- WBR, Andriy Senkovych From greearb at candelatech.com Tue Jan 17 08:43:10 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 17 Jan 2012 08:43:10 -0800 Subject: [Xorp-users] Xorp is not visible as neighbor for Cisco router In-Reply-To: References: <4F0DC685.1090803@candelatech.com> Message-ID: <4F15A51E.3090204@candelatech.com> On 01/17/2012 06:15 AM, Andriy Senkovych wrote: > Hello, Ben > > Just to clarify: do I correctly understant that in order to detect PIM > neighbor this cisco router should just receive PIM_HELLO on the > correct interface(e.g. over gre tunnel in my case)? I used tcpdump to > track outgoung packets and founfd that I do send PIM_HELLO packets. In > other words, is it enough to receive PIM_HELLO message to detect PIM > neighbor? > I really don't know. I believe some other folks have recently gotten multicast over GRE working, so maybe they can offer some assistance. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From igorm at etf.rs Wed Jan 18 03:22:34 2012 From: igorm at etf.rs (=?ISO-8859-2?Q?Igor_Maravi=E6?=) Date: Wed, 18 Jan 2012 12:22:34 +0100 Subject: [Xorp-users] IEEE HPSR 2012 - Full paper submission extended Message-ID: ********************************************************************************************************************* ********************************************************************************************************************* IEEE HPSR 2012 June 24-27 Belgrade Serbia http://www.ieee-hpsr.org Important Dates Full paper submission (extended): February 3, 2012 Tutorial submission: January 20, 2012 Acceptance notifications: March 20, 2012 Camera-ready due: April 15, 2012 IEEE Conference on High Performance Switching and Routing 2012 will be held in Belgrade, the capital of Serbia. Belgrade is a lively metropolis that is a blend of different cultures whose representatives were visiting at various points of history. As such, it is very well suited to host the IEEE HPSR conference that gathers scientists and engineers from the entire world, after Heidelberg, Dallas, Kobe, Torino, Arizona, Hong Kong, Poznan, New York, Shanghai, Paris, Dallas (again), and Cartagena. Internet traffic keeps growing thanks to the access technologies whose speeds are increasing at a fast pace, and thanks to many non-profit and commercial efforts to bridge the digital-divide by providing all the advantages of the Internet to developing countries as well. At the same time, challenging applications are gaining popularity on the Internet such as multimedia and P2P applications. Multimedia applications require a lot of bandwidth and low delays, while the traffic patterns of P2P applications are impossible to predict. IPv4 addresses are being exhausted at this very moment. Data centers are moving a vast amount of content through thousands of switches. Also, routers and switches are being attacked, and energy available for them, as for everything else, is decreasing. All these circumstances put a higher burden than ever on switching and routing. So, there is a lot of work to be done, and IEEE HPSR 2012 will do its part by addressing the following topics: Architectures of high-performance switches and routers High-speed packet processors Address lookup algorithms Packet classification, scheduling and dropping Switching, bridging and routing protocols Multicasting P2P routing Routing in wireless, mobile and sensor networks Optical switching and routing Switching, bridging and routing in data centers and clouds Data placement and migration Multiprocessor networks Network management Pricing, accounting and charging QoS and scalability of switching, bridging and routing Traffic characterization and engineering Power-aware switching, bridging and routing protocols High-speed network security Paper submission guidelines: Submitted papers must be unpublished, and cannot be submitted elsewhere at the same time. Accepted papers should not exceed 6 pages in two-column IEEE Transactions style (www.ieee.org). Accepted papers longer than 6 pages will be charged $100 for each extra page. Papers cannot be longer than 8 pages. Papers should be submitted as PDF files through the EDAS system (http://edas.info). All submitted papers will be subject to three independent reviews. Awards: The Best Paper Award will be granted based on the reviewers? comments and scores that it received. Presentation of the paper will be scored by the audience, and will influence its final ranking. Note: In order to publish the paper at the IEEE HPSR 2012 proceedings and IEEE Xplore, the paper must be presented at the conference, and at least one of its authors should have a full registration. Non-refundable registration fees must be paid prior to uploading the final IEEE formatted, publication-ready, version of the paper. General Chairs: Aleksandra Smiljani? (Belgrade University, Serbia), Mounir Hamdi (Hong Kong University of Science and Technology, China) Technical Program Committee Chairs: Jonathan Chao (Polytechnic Institute of NYU, USA), Eiji Oki (University of Electro-Communications in Tokyo, Japan), Cyriel Minkenberg (IBM Research, Switzerland) Publicity Chairs: Andrea Bianco (Politecnico di Torino, Italy), Aleksandar Kolarov (Telcordia, USA), Dominique Verchere (Alcatel-Lucent, France) Registration and Finance Chair: Milan Bjelica (Belgrade University, Serbia) Publication Chair: Ljiljana Trajkovi? (Simon Fraser University, Canada) Local Arrangement Chairs: Zoran ?i?a, Nata?a Maksi?, and Marija Anti? (Belgrade University, Serbia) Tutorials Chair: Dejan Kosti? (EPFL, Switzerland), dejan.kostic at epfl.ch Panel Chair: Mitchell Gusat (IBM, Switzerland) Q&A: aleksandra at etf.rs, zoran.cica at etf.rs From alexsb92 at gmail.com Mon Jan 23 14:40:47 2012 From: alexsb92 at gmail.com (Alexandru Blidaru) Date: Mon, 23 Jan 2012 17:40:47 -0500 Subject: [Xorp-users] Changing OSPF routes/costs/any part in the OSPF routing table Message-ID: Hey there, I'm a computer engineering student, and I've recently became interested in networks, and this whole routers stuff (scheduled to take a networking class next semester). So I found XORP, and I installed it on a few VMs, and I started playing around with the whole setup. I've been going through the docs found here: http://xorp.run.montefiore.ulg.ac.be/latex2wiki/dev_getting_started, and I started wondering if there is a way to change the routing table. So for example when a certain path would have a cost value of 10, to change it to 20 and see how a packet would move in those conditions. From my understanding even if there is a way to manually do this, due to the way OSPF works, the routing table would be updated after a certain time period. So my question is, is there a way to modify any of the values in the OSPF routing table, in order to then analyze how the packets end up moving around the network? If yes (whether by changing parts of the code, or through settings of some sort), could you give me a few pointers and set me in the right direction? Alexandru Blidaru @G_raph || LinkedIn || Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120123/1bc7439a/attachment.html From greearb at candelatech.com Mon Jan 23 16:33:47 2012 From: greearb at candelatech.com (Ben Greear) Date: Mon, 23 Jan 2012 16:33:47 -0800 Subject: [Xorp-users] Changing OSPF routes/costs/any part in the OSPF routing table In-Reply-To: References: Message-ID: <4F1DFC6B.3090202@candelatech.com> On 01/23/2012 02:40 PM, Alexandru Blidaru wrote: > Hey there, > > I'm a computer engineering student, and I've recently became interested in networks, and this whole routers stuff (scheduled to take a networking class next > semester). So I found XORP, and I installed it on a few VMs, and I started playing around with the whole setup. I've been going through the docs found here: > http://xorp.run.montefiore.ulg.ac.be/latex2wiki/dev_getting_started, and I started wondering if there is a way to change the routing table. So for example when > a certain path would have a cost value of 10, to change it to 20 and see how a packet would move in those conditions. From my understanding even if there is a > way to manually do this, due to the way OSPF works, the routing table would be updated after a certain time period. > > So my question is, is there a way to modify any of the values in the OSPF routing table, in order to then analyze how the packets end up moving around the > network? If yes (whether by changing parts of the code, or through settings of some sort), could you give me a few pointers and set me in the right direction? You can use xorpsh to re-configure xorp, including the interface costs, and it should take affect shortly after you commit the changes. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From alexsb92 at gmail.com Wed Jan 25 17:05:24 2012 From: alexsb92 at gmail.com (Alexandru Blidaru) Date: Wed, 25 Jan 2012 20:05:24 -0500 Subject: [Xorp-users] Changing OSPF routes/costs/any part in the OSPF routing table In-Reply-To: <4F1DFC6B.3090202@candelatech.com> References: <4F1DFC6B.3090202@candelatech.com> Message-ID: Hey Ben, Thanks for the pointer! I took a look around the configuration mode, but i wasn't able to see something that i'd recognize as useful. Since I'm not too familiar with networks and stuff I did have quite a bit of stuff to look up, but I still couldn't really find anything that'd be of use. Do you know any more specific under what category i could find those options? Alexandru Blidaru @G_raph || LinkedIn || Facebook On Mon, Jan 23, 2012 at 7:33 PM, Ben Greear wrote: > On 01/23/2012 02:40 PM, Alexandru Blidaru wrote: > >> Hey there, >> >> I'm a computer engineering student, and I've recently became interested >> in networks, and this whole routers stuff (scheduled to take a networking >> class next >> semester). So I found XORP, and I installed it on a few VMs, and I >> started playing around with the whole setup. I've been going through the >> docs found here: >> http://xorp.run.montefiore.**ulg.ac.be/latex2wiki/dev_**getting_started, >> and I started wondering if there is a way to change the routing table. So >> for example when >> a certain path would have a cost value of 10, to change it to 20 and see >> how a packet would move in those conditions. From my understanding even if >> there is a >> way to manually do this, due to the way OSPF works, the routing table >> would be updated after a certain time period. >> >> So my question is, is there a way to modify any of the values in the OSPF >> routing table, in order to then analyze how the packets end up moving >> around the >> network? If yes (whether by changing parts of the code, or through >> settings of some sort), could you give me a few pointers and set me in the >> right direction? >> > > You can use xorpsh to re-configure xorp, including the interface costs, > and it > should take affect shortly after you commit the changes. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120125/d5afe09e/attachment.html From greearb at candelatech.com Thu Jan 26 11:28:29 2012 From: greearb at candelatech.com (Ben Greear) Date: Thu, 26 Jan 2012 11:28:29 -0800 Subject: [Xorp-users] Changing OSPF routes/costs/any part in the OSPF routing table In-Reply-To: References: <4F1DFC6B.3090202@candelatech.com> Message-ID: <4F21A95D.3060907@candelatech.com> On 01/25/2012 05:05 PM, Alexandru Blidaru wrote: > Hey Ben, > > Thanks for the pointer! I took a look around the configuration mode, but i wasn't able to see something that i'd recognize as useful. Since I'm not too familiar > with networks and stuff I did have quite a bit of stuff to look up, but I still couldn't really find anything that'd be of use. Do you know any more specific > under what category i could find those options? Here's an example that changes some things. Each ' -c ' option starts a new command that you could also interactively type into a xorpsh session. xorpsh -c configure -c delete interfaces interface rddVR9 vif rddVR9 -c set interfaces interface rddVR9 vif rddVR9 address 12.1.1.3 prefix-length 24 -c delete protocols ospf4 area 0.0.0.0 interface rddVR9 vif rddVR9 -c set protocols ospf4 area 0.0.0.0 interface rddVR9 vif rddVR9 address 12.1.1.3 interface-cost 1 -c commit -c exit discard -c exit Your commands would have to match your network and existing xorp configuration of course... Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Sun Jan 29 12:46:57 2012 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sun, 29 Jan 2012 21:46:57 +0100 Subject: [Xorp-users] Xorp 1.8.5 OSPF adjacencies problems on FreeBSD 8.2 with jails. Message-ID: <779237D3-0F0D-4D69-AFC1-99380992615F@spacebugs.nl> Hello list, When I upgrade Xorp to version 1.8.5 it seems that OSPF has trouble forming adjacencies. I use FreeBSD 8.2 and running the Xorp inside jails. OSPF is configured on virtual ethernet interfaces (epair). The configuration is simple: Two jails are connected together by an epair interface. I upgraded Xorp by moving the original version out of the way: cd /usr/local mv xopr xorp-1.8 After that I rebooted to machine, so that only the operating system is started. No jails are started or Xorp. Then I cloned the git repository with git clone, compiled and installed Xorp. When I created the jails again, and starting Xorp, OSPF is not forming any neighborship. The configuration used in both cases are exactly the same. Before I upgraded to Xorp 1.8-CT beheer at R4> show version Version 1.8-CT beheer at R4> [start]#> Welcome to XORP on R4 beheer at R4> show ospf4 neighbor Address Interface State ID Pri Dead 10.1.100.2 epair1a/epair1a Full 10.1.100.2 128 38 10.1.100.6 epair2a/epair2a Full 10.1.100.6 128 37 beheer at R4> With Xorp 1.8.5 OSPF isn't working: [start]#> Welcome to XORP v1.8.5 on R4 Version tag: 92efc7d Build Date: 2012-01-29 20:11 64-bit Version 1.8.5 beheer at R4> show ospf4 neighbor Address Interface State ID Pri Dead beheer at R4> When I move the 1.8.5 version out of the way, and moving back the 1.8 tree, everything works again. In the log file I see the next error: [ 2012/01/29 21:30:37.814126 ERROR xorp_ospfv2:4699 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair2a vif epair2a: 102 Command failed Error while sending to vif: epair2a:epair2a src: 10.1.100.5 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.1.100.5 to 224.0.0.5 on interface epair2a vif epair2a) failed: Invalid argument Any help on this is much appreciated Edwin Schokkenbroek From greearb at candelatech.com Sun Jan 29 13:17:01 2012 From: greearb at candelatech.com (Ben Greear) Date: Sun, 29 Jan 2012 13:17:01 -0800 Subject: [Xorp-users] Xorp 1.8.5 OSPF adjacencies problems on FreeBSD 8.2 with jails. In-Reply-To: <779237D3-0F0D-4D69-AFC1-99380992615F@spacebugs.nl> References: <779237D3-0F0D-4D69-AFC1-99380992615F@spacebugs.nl> Message-ID: <4F25B74D.5010600@candelatech.com> On 01/29/2012 12:46 PM, Edwin Schokkenbroek wrote: > Hello list, > > When I upgrade Xorp to version 1.8.5 it seems that OSPF has trouble forming adjacencies. I use FreeBSD 8.2 and running the Xorp inside jails. OSPF is configured on virtual ethernet interfaces (epair). The configuration is simple: Two jails are connected together by an epair interface. > > I upgraded Xorp by moving the original version out of the way: > > cd /usr/local > mv xopr xorp-1.8 > > After that I rebooted to machine, so that only the operating system is started. No jails are started or Xorp. > > Then I cloned the git repository with git clone, compiled and installed Xorp. > > When I created the jails again, and starting Xorp, OSPF is not forming any neighborship. > > The configuration used in both cases are exactly the same. > > Before I upgraded to Xorp 1.8-CT > > beheer at R4> show version > Version 1.8-CT > beheer at R4> > > > [start]#> Welcome to XORP on R4 > beheer at R4> show ospf4 neighbor > Address Interface State ID Pri Dead > 10.1.100.2 epair1a/epair1a Full 10.1.100.2 128 38 > 10.1.100.6 epair2a/epair2a Full 10.1.100.6 128 37 > beheer at R4> > > With Xorp 1.8.5 OSPF isn't working: > > [start]#> Welcome to XORP v1.8.5 on R4 > Version tag: 92efc7d Build Date: 2012-01-29 20:11 64-bit > > Version 1.8.5 > beheer at R4> show ospf4 neighbor > Address Interface State ID Pri Dead > beheer at R4> > > > When I move the 1.8.5 version out of the way, and moving back the 1.8 tree, everything works again. > In the log file I see the next error: > > [ 2012/01/29 21:30:37.814126 ERROR xorp_ospfv2:4699 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair2a vif epair2a: 102 Command failed Error while sending to vif: epair2a:epair2a src: 10.1.100.5 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.1.100.5 to 224.0.0.5 on interface epair2a vif epair2a) failed: Invalid argument > > Any help on this is much appreciated Does the IP in the error message in match the interface? Ever done a 'git bisect'? That should tell us what commit caused the problem..though it can take a while. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Mon Jan 30 15:24:54 2012 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 31 Jan 2012 00:24:54 +0100 Subject: [Xorp-users] Xorp-users Digest, Vol 70, Issue 10 In-Reply-To: References: Message-ID: <0075DA82-9E5B-403E-AEB2-8F1A7E76CD86@spacebugs.nl> Hello Ben, Thanks for your reply. >> >> When I move the 1.8.5 version out of the way, and moving back the 1.8 tree, everything works again. >> In the log file I see the next error: >> >> [ 2012/01/29 21:30:37.814126 ERROR xorp_ospfv2:4699 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair2a vif epair2a: 102 Command failed Error while sending to vif: epair2a:epair2a src: 10.1.100.5 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.1.100.5 to 224.0.0.5 on interface epair2a vif epair2a) failed: Invalid argument >> >> Any help on this is much appreciated > > Does the IP in the error message in match the interface? That is the strange part. The configuration isn't changed between switching versions. For example on R4. When I do a show of interface and protocol options, they look the same: beheer at R4> show version Version 1.8.5 beheer at R4> beheer at R4> show interfaces epair1a/epair1a: Flags: mtu 1500 speed unknown inet 10.1.100.1 subnet 10.1.100.0/30 broadcast 10.1.100.3 physical index 2 ether 02:cb:55:00:04:0a epair2a/epair2a: Flags: mtu 1500 speed unknown inet 10.1.100.5 subnet 10.1.100.4/30 broadcast 10.1.100.7 physical index 3 ether 02:33:5d:00:04:0a beheer at R4# show interfaces interface epair1a { vif epair1a { address 10.1.100.1 { prefix-length: 30 broadcast: 10.1.100.3 } } } interface epair2a { vif epair2a { address 10.1.100.5 { prefix-length: 30 } } } beheer at R4# show protocols ospf4 router-id: 10.1.100.1 area 0.0.0.0 { interface epair1a { vif epair1a { address 10.1.100.1 { } } } interface epair2a { vif epair2a { address 10.1.100.5 { } } } beheer at R4> show version Version 1.8-CT beheer at R4> show interfaces epair1a/epair1a: Flags: mtu 1500 speed unknown inet 10.1.100.1 subnet 10.1.100.0/30 broadcast 10.1.100.3 physical index 2 ether 02:c7:55:00:04:0a epair2a/epair2a: Flags: mtu 1500 speed unknown inet 10.1.100.5 subnet 10.1.100.4/30 broadcast 10.1.100.7 physical index 3 ether 02:c3:55:00:04:0a beheer at R4# show interfaces interface epair1a { vif epair1a { address 10.1.100.1 { prefix-length: 30 broadcast: 10.1.100.3 } } } interface epair2a { vif epair2a { address 10.1.100.5 { prefix-length: 30 } } } beheer at R4# show protocols ospf4 router-id: 10.1.100.1 area 0.0.0.0 { interface epair1a { vif epair1a { address 10.1.100.1 { } } } interface epair2a { vif epair2a { address 10.1.100.5 { } } } > > Ever done a 'git bisect'? That should tell us what commit > caused the problem..though it can take a while. I don't know git enough to understand this, but if it helps to solve to problem I can try it. What do I have to do exactly ? Just run: 'git bisect' ? Edwin Schokkenbroek > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > > > ------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > End of Xorp-users Digest, Vol 70, Issue 10 > ****************************************** The night, as a mystic wall. I like dry balconies. The sounds rising from the darkened city... The yellow light gives me no comfort at all. From greearb at candelatech.com Mon Jan 30 15:42:16 2012 From: greearb at candelatech.com (Ben Greear) Date: Mon, 30 Jan 2012 15:42:16 -0800 Subject: [Xorp-users] Xorp-users Digest, Vol 70, Issue 10 In-Reply-To: <0075DA82-9E5B-403E-AEB2-8F1A7E76CD86@spacebugs.nl> References: <0075DA82-9E5B-403E-AEB2-8F1A7E76CD86@spacebugs.nl> Message-ID: <4F272AD8.5010105@candelatech.com> On 01/30/2012 03:24 PM, Edwin Schokkenbroek wrote: > Hello Ben, > > Thanks for your reply. >> Ever done a 'git bisect'? That should tell us what commit >> caused the problem..though it can take a while. > > I don't know git enough to understand this, but if it helps to solve to problem I can try it. What do I have to do exactly ? Just run: 'git bisect' ? Basically, you pick a good (1.8-CT) and a bad (1.8.5) commit and then use 'git bisect' to figure out the commit that caused the problems. http://book.git-scm.com/5_finding_issues_-_git_bisect.html Likely there are other resources online somewhere to give you more details, but ask if you get stuck. Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Jan 31 12:15:03 2012 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 31 Jan 2012 21:15:03 +0100 Subject: [Xorp-users] Xorp-users Digest, Vol 70, Issue 11 In-Reply-To: References: Message-ID: <21E5A7C1-61FC-40D7-AF42-2707CFFD900B@spacebugs.nl> Hello Ben, I looked into the git bisect thing. I'm sorry, but it is way over my head. I'm not a developer and I'm not that familiar with tracking down bugs in a repository. If you can explain the steps to take, I may be able to try and see if I can come up with something. I tried with FreeBSD 9.0 , and Xorp 1.8.5 but same problem. I followed the log file for a while: [ 2012/01/31 21:07:46.765638 ERROR xorp_ospfv2:7617 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair1a vif epair1a: 102 Command failed Error while sending to vif: epair1a:epair1a src: 10.0.0.1 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.0.0.1 to 224.0.0.5 on interface epair1a vif epair1a) failed: Invalid argument [ 2012/01/31 21:07:56.765041 WARNING xorp_fea:7509 XrlFeaTarget obj/i386-unknown-freebsd9.0/xrl/targets/fea_base.cc:11377 handle_raw_packet4_0_1_send ] Handling method for raw_packet4/0.1/send failed: XrlCmdError 102 Command failed Error while sending to vif: epair1a:epair1a src: 10.0.0.1 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.0.0.1 to 224.0.0.5 on interface epair1a vif epair1a) failed: Invalid argument [ 2012/01/31 21:07:56.765586 ERROR xorp_ospfv2:7617 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair1a vif epair1a: 102 Command failed Error while sending to vif: epair1a:epair1a src: 10.0.0.1 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.0.0.1 to 224.0.0.5 on interface epair1a vif epair1a) failed: Invalid argument [ 2012/01/31 21:08:06.765025 WARNING xorp_fea:7509 XrlFeaTarget obj/i386-unknown-freebsd9.0/xrl/targets/fea_base.cc:11377 handle_raw_packet4_0_1_send ] Handling method for raw_packet4/0.1/send failed: XrlCmdError 102 Command failed Error while sending to vif: epair1a:epair1a src: 10.0.0.1 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.0.0.1 to 224.0.0.5 on interface epair1a vif epair1a) failed: Invalid argument [ 2012/01/31 21:08:06.765691 ERROR xorp_ospfv2:7617 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair1a vif epair1a: 102 Command failed Error while sending to vif: epair1a:epair1a src: 10.0.0.1 dest: 224.0.0.5: sendmsg(proto 89 size 64 from 10.0.0.1 to 224.0.0.5 on interface epair1a vif epair1a) failed: Invalid argument I can try to see if 1.8.4 works. Edwin Schokkenbroek > >>> Ever done a 'git bisect'? That should tell us what commit >>> caused the problem..though it can take a while. >> >> I don't know git enough to understand this, but if it helps to solve to problem I can try it. What do I have to do exactly ? Just run: 'git bisect' ? > > Basically, you pick a good (1.8-CT) and a bad (1.8.5) commit and > then use 'git bisect' to figure out the commit that caused > the problems. > > http://book.git-scm.com/5_finding_issues_-_git_bisect.html > > > Likely there are other resources online somewhere to give you more > details, but ask if you get stuck. > > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > > > ------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > End of Xorp-users Digest, Vol 70, Issue 11 > ****************************************** The night, as a mystic wall. I like dry balconies. The sounds rising from the darkened city... The yellow light gives me no comfort at all. From greearb at candelatech.com Tue Jan 31 12:18:45 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 31 Jan 2012 12:18:45 -0800 Subject: [Xorp-users] Xorp-users Digest, Vol 70, Issue 11 In-Reply-To: <21E5A7C1-61FC-40D7-AF42-2707CFFD900B@spacebugs.nl> References: <21E5A7C1-61FC-40D7-AF42-2707CFFD900B@spacebugs.nl> Message-ID: <4F284CA5.2080106@candelatech.com> On 01/31/2012 12:15 PM, Edwin Schokkenbroek wrote: > Hello Ben, > > I looked into the git bisect thing. I'm sorry, but it is way over my head. I'm not a developer and I'm not that familiar with tracking down bugs in a repository. If you can explain the steps to take, I may be able to try and see if I can come up with something. > > I tried with FreeBSD 9.0 , and Xorp 1.8.5 but same problem. I followed the log file for a while: Well, to start with..could you try rls 1.8.3 and see if that works? If not, use an earlier release..and if it does, try 1.8.4. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Jan 31 15:33:16 2012 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 1 Feb 2012 00:33:16 +0100 Subject: [Xorp-users] Xorp 1.8.5 OSPF adjacencies problems on FreeBSD 8.2 with jails. In-Reply-To: References: Message-ID: <06108D50-DAC9-4658-9A49-BDB38C5C4F3A@spacebugs.nl> Hello Ben, I looked into the git bisect thing. I'm sorry, but it is way over my head. I'm not a developer and I'm not that familiar with tracking down bugs in a repository. If you can explain the steps to take, I may be able to try and see if I can come up with something. I tried with FreeBSD 9.0 , and Xorp 1.8.5 but same problem. I followed the log file for a while: Well, to start with..could you try rls 1.8.3 and see if that works? If not, use an earlier release..and if it does, try 1.8.4. Yep no problem :-) The machine is a testing machine, so I can basically do everything with it. So far I tried : 1.8-CT -> Works (original version I started with). 1.8.3 -> Works. 1.8.4 -> Works. 1.8.5 -> Doesn't work. For completeness : These tests are done on FreeBSD 8.2 Edwin Schokkenbroek From greearb at candelatech.com Tue Jan 31 15:49:23 2012 From: greearb at candelatech.com (Ben Greear) Date: Tue, 31 Jan 2012 15:49:23 -0800 Subject: [Xorp-users] Xorp 1.8.5 OSPF adjacencies problems on FreeBSD 8.2 with jails. In-Reply-To: <06108D50-DAC9-4658-9A49-BDB38C5C4F3A@spacebugs.nl> References: <06108D50-DAC9-4658-9A49-BDB38C5C4F3A@spacebugs.nl> Message-ID: <4F287E03.4030202@candelatech.com> On 01/31/2012 03:33 PM, Edwin Schokkenbroek wrote: > > Hello Ben, > > > > I looked into the git bisect thing. I'm sorry, but it is way over my head. I'm not a developer and I'm not that familiar with tracking down bugs in a repository. If you can explain the steps to take, I may be able to try and see if I can come up with something. > > I tried with FreeBSD 9.0 , and Xorp 1.8.5 but same problem. I followed the log file for a while: > > > Well, to start with..could you try rls 1.8.3 and see if that works? > > If not, use an earlier release..and if it does, try 1.8.4. > > > Yep no problem :-) The machine is a testing machine, so I can basically do everything with it. > So far I tried : 1.8-CT -> Works (original version I started with). 1.8.3 -> Works. 1.8.4 -> Works. 1.8.5 -> Doesn't work. Ok, so the bug was introduced in the 1.8.5 release it seems. To bisect this, you clone the xorp project: git clone git://github.com/greearb/xorp.ct.git Then, in the newly created repository: git bisect start git bisect good xorp-1.8.4 git bisect bad HEAD Now, compile xorp, install it and test. If it is good, then just enter 'git bisect good' and if it fails, then 'git bisect bad'. Then compile, test, repeat. Eventually, git bisect will tell you which commit introduced the problem. Let me know that information and hopefully I can figure out where the problem lies. Thanks, Ben > > For completeness : These tests are done on FreeBSD 8.2 > > Edwin Schokkenbroek > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com