All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Messages in log with SNAT target
Date: Mon, 24 Jul 2006 12:17:47 +0300	[thread overview]
Message-ID: <44C4903B.3080004@gmail.com> (raw)

Hi!

I've been using this kind of configuration on my Linux router for a few
years:

eth0	80.223.77.223, public internet ip
eth0:0	10.0.0.1, private network ip

IP forwarding enabled.

And a rule for iptables:
-A POSTROUTING -s 10.0.0.0/255.255.255.0 -d ! 10.0.0.0/255.255.255.0 -j
SNAT --to-source 80.223.77.223

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
10.0.0.0        0.0.0.0         255.255.255.0   U     10     0        0 eth0
80.223.64.0     0.0.0.0         255.255.240.0   U     10     0        0 eth0
0.0.0.0         80.223.64.1     0.0.0.0         UG    10     0        0 eth0


However, I get lots of this kind of messages in the dmesg while routing:
host 10.0.0.4/if2 ignores redirects for 70.35.xxx.xxx to 80.223.64.1.
host 10.0.0.4/if2 ignores redirects for 68.219.xxx.xxx to 80.223.64.1.
host 10.0.0.4/if2 ignores redirects for 193.88.xxx.xxx to 80.223.64.1.
host 10.0.0.4/if2 ignores redirects for 80.81.xxx.xxx to 80.223.64.1.
host 10.0.0.4/if2 ignores redirects for 80.81.xxx.xxx to 80.223.64.1.

10.0.0.4 is a Windows machine in the private network set to use 10.0.0.1
(router) as a gateway. 80.223.64.1 is the ISP gateway. The third ip
number in the log message is the ip number of a server, to which the
10.0.0.4 is connected.

Note that the routing itself works just fine, there is just this log
message flood.

Please advise.

-- 
Anssi Hannula



             reply	other threads:[~2006-07-24  9:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24  9:17 Anssi Hannula [this message]
2006-07-24 10:15 ` Messages in log with SNAT target Sietse van Zanen
2006-07-24 10:24 ` Pascal Hambourg
2006-07-24 10:49   ` Sietse van Zanen
2006-07-25 13:21     ` Pascal Hambourg
2006-07-25 13:37       ` Sietse van Zanen
2006-07-24 11:03   ` Anssi Hannula
2006-07-24 11:33     ` Sietse van Zanen
2006-07-24 12:01       ` Anssi Hannula
2006-07-24 12:39         ` Sietse van Zanen
2006-07-24 12:55           ` Anssi Hannula
2006-07-26  0:40         ` R. DuFresne
2006-07-26  8:16           ` Anssi Hannula
2006-07-26  9:17             ` Sietse van Zanen
2006-07-26 11:21               ` Anssi Hannula
2006-07-26 11:22                 ` Sietse van Zanen
2006-07-26 11:54                   ` Anssi Hannula
2006-07-27 19:09                     ` R. DuFresne
2006-07-27 19:46                       ` Anssi Hannula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44C4903B.3080004@gmail.com \
    --to=anssi.hannula@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.