[Xorp-users] OpenBSD IGMP/PIM Issue

[Stegen Smith]

Sweet!

I didn't even think of checking pf.  That was the trick!  I'll update CVS in the morning and use it with the new fixes.
For now, though, disabling pf worked.  I'm now seeing the igmp packets coming and going.  This is excellent news...

thank you very much for the help and I'll let you know how the update works in the morning (which I'm sure it'll work gloriously. ;) )

stegen

Pavlin Radoslavov wrote:
> Further update on the subject.
> 
> Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> wrote:
> 
>> Stegen,
>>
>> I was able to replicate all of the issues so here is a quick update:
>>
>> * The "RTM version mismatch: expected 4 got 3" error.
>>   I will look into that and submit a fix to CVS.
>>   Right now I doubt this is related to the rest of the problems.
> 
> Those error messages can be ignored. Apparently, OpenBSD sends each
> routing message twice, once as RTM_VERSION and once as RTM_OVERSION.
> Anyway, the problem is fixed in CVS:
> 
> Revision  Changes                                Path
> 1.17      +12 -2;  commitid: 12b3148ed5b5541a7;
> xorp/fea/data_plane/fibconfig/fibconfig_entry_parse_routing_socket.cc
> 1.17      +12 -2;  commitid: 12b3148ed5b5541a7;
> xorp/fea/data_plane/fibconfig/fibconfig_table_parse_routing_socket.cc
> 1.27      +11 -1;  commitid: 12b3148ed5b5541a7;
> xorp/fea/data_plane/ifconfig/ifconfig_parse_routing_socket.cc
> 
>> * The fib2mrib coredump seems to be triggered by the FEA failing to
>>   read the forwarding table.
>>   If you remove the click block in the fea configuration this
>>   problem should go away.
>>   In any case, this seems a bug in the FEA, because disabled click
>>   statement shouldn't trigger that. Hence please submit a Bugzilla
>>   entry with your original configuration (fib2mrib and click
>>   included), and a copy of the output log messages.
>>
>> * The "No route to host" error message seems to be triggered only
>>   for IGMP messages (PIM messages seem to be fine).
>>   I will try to investigate the issue, unless Bruce beats me to that
>>   if you give him a temp. OpenBSD account :)
> 
> The problem was that the FEA unconditionally enabled the OpenBSD
> pf(4) firewall on startup, and by default the pf(4) drops IP packets
> with the Router Alert IP option (included in the IGMP packets).
> 
> The problem is now fixed in CVS:
> 
> Revision  Changes                               Path
> 1.21      +7 -1;  commitid: 1346248edb08f41a7;  xorp/fea/fea_node.cc
> 1.8       +7 -1;  commitid: 1346248edb08f41a7;  xorp/fea/firewall_manager.cc
> 
> Please get the latest code from CVS and see whether it works for
> you. If using the CVS code is not an option, a possible hackish
> work-around is to disable the firewall AFTER XORP is started by
> using the following UNIX command:
> 
>     pfctl -d
> 
> Pavlin
>