From: Luca Maragnani <luca.maragnani@objectlab.it>
To: lartc@vger.kernel.org
Subject: [LARTC] Ip route cache problem
Date: Wed, 12 Oct 2005 08:46:08 +0000 [thread overview]
Message-ID: <434CCD50.3080104@objectlab.it> (raw)
Hello,
I need some help about a routing problem on a complex configuration.
The problem is that I can't reach from services outside from my DMZ.
The scenario is a gateway linked to three internet connections, so that
I used three distinct iproute2 tables for routing. The gw is running
ipvs for balancing over the dmz's servers.
DMZ servers are on 192.168.1.0/24 network, .
Every table has the route to reach :
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1
I'm using iptables to NAT a server on my DMZ to reach DNS services outsides:
iptables -t nat -A POSTROUTING -p tcp -s 192.168.1.0/24 -d 151.99.0.100
--dport 53 -j SNAT --to-source 81.77.88.99
Looking inside the cache I find only the route to reach the dns server,
but not the one that the dns needs to reach my server:
151.99.0.100 from 192.168.1.2 via 81.77.88.100 dev eth2 src 192.168.1.249
cache <src-direct> mtu 1500 advmss 1460 metric10 64 iif eth0
I experieced in the past that reentering the iptables nat command
worked, but it seems a random effect and not always works.
Thank's in advance,
Luca Maragnani
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-10-12 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 8:46 Luca Maragnani [this message]
2005-10-12 10:20 ` [LARTC] Ip route cache problem Ionut Popovici
2005-10-12 12:52 ` Luca Maragnani
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=434CCD50.3080104@objectlab.it \
--to=luca.maragnani@objectlab.it \
--cc=lartc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox