<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Ben,<br>
<br>
I've gone ahead and submitted a bug to FreeBSD regarding this
behavior which can be seen here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.freebsd.org/cgi/query-pr.cgi?pr=175365">http://www.freebsd.org/cgi/query-pr.cgi?pr=175365</a><br>
<br>
However, you will notice that its listed as a low priority and
"non-critical" which I find a bit annoying considering the fact that
userland software can cause the kernel to panic. To that effect, is
there something we could be doing differently on our Xorp config to
perhaps mitigate the problem? <br>
<br>
I was hoping other users with GRE and multicast experience would be able
to speak up about our configuration we are trying to make work, but the
lack of replies to it has me feeling like we're not going to be getting
a lot of help from the community and this combined with having to deal
with the whole kernel panic issue as well has me wondering where to go
for working multicast capabilities as most of the other software
projects I could find were so old and/or not actively maintained that it
seemed like a long shot anything would be possible. Xorp to me at least
felt like our last best hope for getting working multicast on FreeBSD,
but I don't pretend to know everything out there.<br>
<br>
Any help is appreciated, thanks!<br>
<blockquote style="border: 0px none;"
cite="mid:50F60A55.5010703@candelatech.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="greearb@candelatech.com" photoname="Ben Greear"
src="cid:part1.07010909.07080600@agiosat.net"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:greearb@candelatech.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Ben Greear</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Tuesday, January
15, 2013 6:03 PM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<br>Well, whatever the problem might be with Xorp, the kernel shouldn't
<br>crash, so it's a FreeBSD bug primarily.
<br>
<br>I mostly work with Linux, so hopefully someone else (probably
<br>on some BSD mailing list) can help with the BSD kernel issues...
<br>
<br>Thanks,
<br>Ben
<br>
<br></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="dspisak@agiosat.net" photoname="Daniel Spisak"
src="cid:part1.07010909.07080600@agiosat.net"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:dspisak@agiosat.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Daniel Spisak</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Tuesday, January
15, 2013 5:45 PM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hi there, I'm new to the list!
<br>
<br>Myself and a colleague have been trying to use Xorp 1.8.6 (we pulled
the
source from the git repo about a two months ago) to handle multicast
routing over GRE tunnels for a rather convoluted scenario. In the course
of trying to get that setup working (which will be another separate
email to the list) we seem to be running into behavior from Xorp that is
causing kernel panics to happen on FreeBSD 8.3-RELEASE.
<br>
<br>Currently, we are able to startup Xorp normally with no apparent
problems. However, as soon as we try to shutdown the Xorp service or
initiate a system reboot the system will kernel panic. We are running
Xorp on ALIX1.D single board computers. You can see more about the
hardware specs here:
<br>
<br><a class="moz-txt-link-freetext" href="http://pcengines.ch/alix1d.htm">http://pcengines.ch/alix1d.htm</a>
<br>
<br>I have created a file dump of some of the kernel panics along with
some
kdbg backtraces for developers to take a look at (along with a
kernel.debug for our kernel build). If I am reading the backtraces
right, it looks like there might be an issue being caused by IGMP
somehow. Perhaps a mismatch between v2 and v3?
<br>
<br><a class="moz-txt-link-freetext" href="http://www.mediafire.com/?ojxdc172mp7q6">http://www.mediafire.com/?ojxdc172mp7q6</a>
<br>
<br>I'm pretty new to Xorp and multicast so its possible I've missed
something here. Below is the xorp.config of the box in question that
does the kernel panics:
<br>
<br>/* XORP configuration file
<br> *
<br> * Configuration format: 1.1
<br> * XORP version: 1.8.6-WIP
<br> * Date: 2012/12/05 00:04:02.421583
<br> * Host: dispatch-dev
<br> * User: root
<br> */
<br>
<br>protocols {
<br> fib2mrib {
<br> disable: false
<br> }
<br> igmp {
<br> disable: false
<br> interface vr0 {
<br> vif vr0 {
<br> disable: false
<br> version: 2
<br> enable-ip-router-alert-option-check: false
<br> query-interval: 125
<br> query-last-member-interval: 1
<br> query-response-interval: 10
<br> robust-count: 2
<br> }
<br> }
<br> traceoptions {
<br> flag {
<br> all {
<br> disable: false
<br> }
<br> }
<br> }
<br> }
<br> pimsm4 {
<br> disable: false
<br> interface vr0 {
<br> vif vr0 {
<br> disable: false
<br> dr-priority: 100
<br> hello-period: 30
<br> hello-triggered-delay: 5
<br> }
<br> }
<br> interface "register_vif" {
<br> vif "register_vif" {
<br> disable: false
<br> dr-priority: 1
<br> hello-period: 30
<br> hello-triggered-delay: 5
<br> }
<br> }
<br> static-rps {
<br> rp 10.255.254.254 {
<br> group-prefix 239.0.0.1/32 {
<br> rp-priority: 192
<br> hash-mask-len: 30
<br> }
<br> }
<br> }
<br> switch-to-spt-threshold {
<br> disable: false
<br> interval: 100
<br> bytes: 102400
<br> }
<br> traceoptions {
<br> flag {
<br> all {
<br> disable: false
<br> }
<br> }
<br> }
<br> }
<br>}
<br>interfaces {
<br> restore-original-config-on-shutdown: false
<br> interface vr0 {
<br> description: "Ethernet Iface"
<br> disable: false
<br> discard: false
<br> unreachable: false
<br> management: false
<br> parent-ifname: ""
<br> iface-type: ""
<br> vid: ""
<br> vif vr0 {
<br> disable: false
<br> }
<br> default-system-config
<br> }
<br>}
<br>plumbing {
<br> mfea4 {
<br> disable: false
<br> interface vr0 {
<br> vif vr0 {
<br> disable: false
<br> }
<br> }
<br> interface "register_vif" {
<br> vif "register_vif" {
<br> disable: false
<br> }
<br> }
<br> traceoptions {
<br> flag {
<br> all {
<br> disable: false
<br> }
<br> }
<br> }
<br> }
<br>}
<br>
<br>Output from fbsd for interfaces:
<br>
<br>dispatch-dev# ifconfig -a
<br>vr0:
flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric
0 mtu 1500
<br>
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
<br> ether 00:0d:b9:0e:32:d4
<br> inet XX.XX.XXX.XX netmask 0xfffffffc broadcast XX.XX.XXX.XX
<br> inet 192.168.10.2 netmask 0xffffff00 broadcast
192.168.10.255
<br> inet 10.13.8.253 netmask 0xffffff80 broadcast 10.13.8.255
<br> media: Ethernet autoselect (100baseTX <full-duplex>)
<br> status: active
<br>lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu
16384
<br> options=3<RXCSUM,TXCSUM>
<br> inet 127.0.0.1 netmask 0xff000000
<br>enc0: flags=0<> metric 0 mtu 1536
<br>pflog0: flags=0<> metric 0 mtu 33200
<br>gre0: flags=9010<POINTOPOINT,LINK0,MULTICAST> metric 0 mtu
1476
<br>
<br>If anyone has any input/insight as to what is causing the kernel
panics
and how to fix it, that would be great. Thanks!
<br>
<br></div>
</blockquote>
<br>
<div class="moz-signature">-- <br>Daniel Spisak<br>
Network Engineer<br>
<a class="moz-txt-link-abbreviated" href="mailto:dspisak@agiosat.net">dspisak@agiosat.net</a><br>
</div>
</body></html>