On Jan 19, 2008 9:31 PM, Tom Eastep <[EMAIL PROTECTED]> wrote: > One think I think I can help you with. You report that ping 224.0.0.1 > doesn't work with Shorewall started. That's because you don't have a > route for 224.0.0.0/4 out of your local interface. So with Shorewall > started, I suspect that the default route is used and the pings are > being rejected out of your 'net' interface.
Hot damn, you got it. For future searchers out there... All linux multicast related docs on the net are at least 5 years old... some 9. I did add routes, but still can't ping the multicast responder address. But this appears to be a red herring, as it's now working. Here's the fix: On the box that is $FW: route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0 Thanks, Tom! ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
