Routine WHO traffic causes martian source errors

UPDATE:

I think it’s a bug in the bonding driver:

dustpuppy's own SMB BROWSER ANNOUNCE packets caused the errors

dustpuppy's own SMB BROWSER ANNOUNCE packets caused the errors

I noted that Horde (192.168.0.146) has been pumping out WHO broadcasts all morning and dustpuppy didn’t log a Martian Source error.  It’s also been sending SMB broadcast packets with no errors.  As soon as dustpuppy sent an SMB broadcast, it logged a Martian Source error.  It seems that the bonding driver has a bug where broadcasts originating on one of the interfaces cause an error when they’re heard on the other interface.  It’s analogous to a radar antenna equipped with dual feedhorns picking up its own reflection on the other horn.  The question is how do I stop the kernel from logging these errors?

Since I enabled bonding on my two ethernet cards in the server, I’ve been getting martian source errors in the server’s kernel log.  These errors line up with routine WHO packets:

The "martian source" errors line up with the WHO traffic in the Wireshark window

The "martian source" errors line up with the WHO traffic in the Wireshark window

Ignore the yellow BROWSER packets – they’re fine.  So I disabled the rwho and rusers daemons.  I can just finger if I want userinfo from another box.

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: