Hi, See /usr/src/linux/Documentation/networking/ip-sysctl.txt for an explanation of parameters that can be set for networking, specifically "log_martians". The current settings can be found by typing (as root): sysctl -a | grep martian (if there multiple interfaces their will be an entry for each one net.ipv4.conf.XXXXX.log_martians plus the "default" and "all" Two way to implement this: 1. From the command line (needs to be re-done each time you reboot): echo 0 >/proc/sys/net/ipv4/conf/all/log_martians echo 0 >/proc/sys/net/ipv4/conf/default/log_martians 2. Automatically at startup, by editing /etc/sysctl.conf and adding: net.ipv4.conf.default.log_martians = 0 net.ipv4.conf.all.log_martians = 0 To activate the changes without rebooting type: /etc/rc.d/boot.sysctl start Rgds, Simon -----Original Message----- From: Tarjei Huse [mailto:tarjei+a_lists.suse@nu.no] Sent: Tuesday, August 02, 2005 12:57 To: suse-security@suse.com Subject: [suse-security] Martian problems Hi, I'm having problems with a SuSE 9.2 box. The box is set up with two interfaces on the same subnet. The interfaces has been set up as normal with static ip's 10.9.1.3, 10.9.1.2 , netmask 255.255.255.0 and broadcast 10.9.1.255. I'm getting errormessages saying Aug 2 12:33:41 mail2 kernel: martian source 10.9.1.255 from 10.9.1.3, on dev eth1 Aug 2 12:33:41 mail2 kernel: ll header: ff:ff:ff:ff:ff:ff:00:c0:9f:2c:2d:f7:08:00 Is this related to the usage of two nics on the same subnet? If so, is there a way to solve this? It seems the martians are stopping cups from doing broadcasts. Kind regards, Tarjei