Mailinglist Archive: opensuse-security (334 mails)

< Previous Next >
AW: [suse-security] martian source messages
Hi,

I had a similar problem with a friends router, got hundreds of martian
source packets from 10.0.0.1 on ppp0. After trying to locate the problem on
the router with no results we've called the provider. The next day the
problem was gone! I think it was a misconfigured router on the providers
side.

Mike



> -----Ursprüngliche Nachricht-----
> Von: Pep Serrano [mailto:mylists@xxxxxxxxxxxxxxxxxxxx]
> Gesendet: Mittwoch, 17. September 2003 17:20
> An: suse-security@xxxxxxxx
> Betreff: [suse-security] martian source messages
>
>
> Hi all
>
> I am getting the following martian kernel messages since I
> changed my ISP:
>
> martian source 81.56.221.174 from 127.0.0.1, on dev ppp0
> ll header:
> 45:08:00:28:da:b8:00:00:7d:06:b5:27:7f:00:00:01:51:38:dd:ae:00:50
>
> Now here is the configuration of my box:
>
> I have an ADSL/Ethernet modem on ppp0:
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:81.56.221.174 P-t-P:192.168.254.254
> Mask:255.255.255.255
>
> The modem is connected to eth0:
> eth0 Link encap:Ethernet HWaddr 00:60:97:4B:82:AA
> inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
>
> Additionally I have the loopback interface(127.0.0.1) and one
> more interface
> for local network:
> eth1 Link encap:Ethernet HWaddr 00:60:97:75:B4:28
> inet addr:192.168.0.254 Bcast:192.168.0.255
> Mask:255.255.255.0
>
> I am running SuSEfirewall2 as FW and NAT router. Here are the
> main config
> parameters:
>
> FW_DEV_EXT="ppp0 eth0"
> FW_DEV_INT="lo eth1"
> FW_ROUTE="yes"
> FW_MASQUERADE="yes"
> FW_MASQ_DEV="ppp0"
>
> I don't see where I am getting these "martian packets" from.
> I need some
> help.
>
> Cheers
> Pep Serrano.
>
>
> --
> Check the headers for your unsubscription address
> For additional commands, e-mail: suse-security-help@xxxxxxxx
> Security-related bug reports go to security@xxxxxxx, not here
>



Gesendet über Mailserver: begros.de! Trotz sorgfältiger Virenprüfung können wir für eventuelle Schäden, die durch nicht erkannte Computerviren entstehen, keine Haftung übernehmen.0
>

< Previous Next >
Follow Ups