Re: weird message in logs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Peter Marshall wrote:
Below is a message I get in my messages file.  Basically, there is a company
going to lease space from us.  I know it would have been easier to just
stick another card in my firewall and give them a subnet, however, that is
not possible for our setup (long story).  Anyway, I bult another firewall
for them.  This firewall sits within our internal network (physically) and
has 2 network cards.  The firewalls internal network card is for their
netowrk; 192.168.90.0/24,  The external card has a network of its own
10.90.0.2.  My internal firewall has a sub interface eth0:1 with the number
10.90.0.1  (eth0 is 192.168.200.1 and is the gateway to my companys internal
network).

What I am doing at the moment is ssh'ing to the newly created firewall
called rubidium on port 15422.  I get the following in my messages file.
Does anyone know how to correct this problem.  It does not prevent me from
sshing, however, I would prefer to not have errors in my log files.

Oct 19 14:46:05 rubidium kernel: REJECT: INPUT IN=eth1 OUT=
MAC=00:50:04:9b:7a:ee:00:50:04:68:df:06:08:00 SRC=10.90.0.1 DST=10.90.0.2
LEN=484 TOS=0x10 PREC=0xC0 TTL=64 ID=58050 PROTO=ICMP TYPE=5 CODE=1
GATEWAY=192.168.202.73 [SRC=10.90.0.2 DST=192.168.202.73 LEN=456 TOS=0x10
PREC=0x00 TTL=64 ID=7787 DF PROTO=TCP SPT=15422 DPT=2510 WINDOW=8576
RES=0x00 ACK PSH URGP=0 ]

What happened is that your internal firewall got packet from rubidium for a host on your local network. It found out that it needs to route it back to the interface it came from (eth0), so it generated ICMP host redirect packet (PROTO=ICMP TYPE=5 CODE=1) telling rubidium to talk to 192.168.202.73 directly (GATEWAY=192.168.202.73). The thing in square brackets is copy of the packet that caused this ICMP redirect (it is part of it).


If putting 10.90.0.1 onto separate physical interface is not an option, than the only thing you could do is disabling generation of ICMP redirects on your internal firewall.

To disable them on the running host, do:

for a in /proc/sys/net/ipv4/conf/*/send_redirects
do
   echo 0 > $a
done

To have them disabled on next reboot, place this into /etc/sysctl.conf:

net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.default.send_redirects = 0

Of course, instead of disabling them on all interfaces, you can disable them per interface too.

--
Aleksandar Milivojevic <amilivojevic@xxxxxx>    Pollard Banknote Limited
Systems Administrator                           1499 Buffalo Place
Tel: (204) 474-2323 ext 276                     Winnipeg, MB  R3T 1L7


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux