Hi Corvin, For "martian source" partial reference jump to the following, it is illuminant!! =:`) "[SLE] martian source in dev eth0" from Carlos Illana (cillana@teleline.es) http://lists.suse.com/archives/suse-linux-e/2000-Jul/0221.html and related Eilert Brinkmann's (eilert@Informatik.Uni-Bremen.DE) reply: http://lists.suse.com/archives/suse-linux-e/2000-Jul/0282.html HTH Best regards, Eduardo Carriles [-- Better a smile than a flame --] (Long time SuSE-Linux [prefered distro] user). [-- Se me nota mucho? -- Notices me much?] [-- Have a lot of fun...] ---- Corvin Russell wrote:
Hi,
I know this suject was brought up first in Jan, then in July again. However, there is nothing in the way of documentation (I think I found about three lapidary lines) to really let one know, as another questioner wanted to, whether this is at all a security issue. Put another way, what is the utility of this obscure kernel function? How are we to use the information so gained?
Twice now I have had kernel messages like the following:
Jul 20 12:20:42 raven kernel: martian source 09da30d0 for ca3fd1d8, dev ppp1 Jul 20 12:20:42 raven kernel: ll header: 45 00 00 28 Jul 20 12:22:42 raven kernel: martian source 09da30d0 for ca3fd1d8, dev ppp1 Jul 20 12:22:42 raven kernel: ll header: 45 00 00 28 Jul 20 12:24:42 raven kernel: martian source 09da30d0 for ca3fd1d8, dev ppp1 Jul 20 12:24:42 raven kernel: ll header: 45 00 00 28 [snip...]
This is probaly a trivial issue,
Not so trivial, thought!! =:`)
so sorry for time-wasting. However as it has come up more than once, perhaps someone knowledgeable could provide a little information, for the record, as to how we might evaluate such messages. If there are no such criteria, then I guess I will just disable this logging "feature".
Better follow the previous links first. =8`)
Thanks,
Don't need to...
Corvin
[snip...] -- Corvin Russell