From: Ionut Popovici <ionut@topall.ro>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Ip route cache problem
Date: Wed, 12 Oct 2005 10:20:16 +0000 [thread overview]
Message-ID: <434CE360.7070608@topall.ro> (raw)
In-Reply-To: <434CCD50.3080104@objectlab.it>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
>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
Have u try to use DNAT from iptables because dnat is in PREROTING , and if u have a dns service u need to make the outside service connection to connect 2 your dns server !
>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
[-- Attachment #2: ionut.vcf --]
[-- Type: text/x-vcard, Size: 836 bytes --]
begin:vcard
fn:Popovici Ionut
n:Ionut;Popovici
org:ISP TOPALL SRL;IT & Network Administrator
adr:Bl.13;;Stefan cel Mare ;Roman;Neamt;5550;Romania
email;internet:ionut@topall.ro
title:Administrator
tel;work:+40-233-742419
tel;fax:+40-233-744881
tel;home:+40-233-720881
tel;cell:+40-746-251059
note;quoted-printable:.........................................................................=
=0D=0A=
Privileged/Confidential Information may be contained in this message. If=0D=0A=
you are not the addressee indicated in this message (or responsible for=0D=0A=
delivery of the message to such person), you may not copy or deliver this=
=0D=0A=
message to anyone. In such a case, you should destroy this message and=0D=0A=
kindly notify the sender by reply e-mail.
x-mozilla-html:FALSE
url:http://www.topall.ro
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-12 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 8:46 [LARTC] Ip route cache problem Luca Maragnani
2005-10-12 10:20 ` Ionut Popovici [this message]
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=434CE360.7070608@topall.ro \
--to=ionut@topall.ro \
--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 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.