From: "Jose Luis Hime" <jhime@synchro.com.br>
To: 'George Vieira' <georgev@citadelcomputer.com.au>,
jhime@synchro.com.br,
'Ray Leach' <raymondl@knowledgefactory.co.za>,
'Netfilter Mailing List' <netfilter@lists.netfilter.org>
Subject: RE: Problems with NAT
Date: Thu, 29 May 2003 20:02:33 -0300 [thread overview]
Message-ID: <004701c32636$640deeb0$010319ac@jhime> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A0D6D52@wardrive.citadelcomputer.com.au>
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
The addresses are the following:
LAN A: 172.25.0.0 / 255.255.0.0
LAN B: 172.28.0.0 / 255.255.0.0
LAN C: 10.0.0.0 / 255.0.0.0
LAN D: 159.254.172.0 / 255.255.255.0
LAN E: 164.137.0.0 / 255.255.0.0
LANs A and B are from the company I work for.
LANs C, D and E are from custommers of ours.
Thanks,
Jose Hime
-----Original Message-----
From: George Vieira [mailto:georgev@citadelcomputer.com.au]
Sent: Thursday, May 29, 2003 7:09 PM
To: jhime@synchro.com.br; Ray Leach; Netfilter Mailing List
Subject: RE: Problems with NAT
What is the IP ranges for the other networks? Are they the same subnet or different ones?
Ned more info so we can determine the needs..
PS: Nice drawing ;P
Thanks,
____________________________________________
George Vieira
Systems Manager
georgev@citadelcomputer.com.au
Citadel Computer Systems Pty Ltd
http://www.citadelcomputer.com.au
Phone : +61 2 9955 2644
HelpDesk: +61 2 9955 2698
-----Original Message-----
From: Jose Luis Hime [mailto:jhime@synchro.com.br]
Sent: Friday, May 30, 2003 3:15 AM
To: 'Ray Leach'; 'Netfilter Mailing List'
Subject: RE: Problems with NAT
The problem is that there are LAN C, LAN D and LAN E in other 3 cities,
also! So, the rule:
-t nat -A POSTROUTING -s LAN A -d ! LAN B -j SNAT --to Firewall_IP_address
would work for LAN B, but not for the other LANs.
All LANs are connected to the same router.
Thanks again,
Jose Hime
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Ray Leach
Sent: Thursday, May 29, 2003 12:55 PM
To: Netfilter Mailing List
Subject: Re: Problems with NAT
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2452 bytes --]
next prev parent reply other threads:[~2003-05-29 23:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 22:09 Problems with NAT George Vieira
2003-05-29 23:02 ` Jose Luis Hime [this message]
2003-05-30 1:59 ` Matt Hellman
2003-05-30 11:33 ` Problems with NAT - it worked ! Jose Luis Hime
2003-05-30 2:01 ` Problems with NAT Matt Hellman
-- strict thread matches above, loose matches on Subject: below --
2003-09-27 16:44 Adam Mercer
2003-09-28 3:30 ` Mark E. Donaldson
2003-09-28 7:36 ` Adam Mercer
2003-05-30 6:57 George Vieira
2003-05-30 2:30 George Vieira
2003-05-29 15:15 Jose Luis Hime
2003-05-29 15:55 ` Ray Leach
2003-05-29 17:15 ` Jose Luis Hime
2003-05-30 6:04 ` Ray Leach
2002-11-13 18:13 problems with nat Rahul Jadhav
2002-11-13 19:20 ` Ben Russo
2002-11-13 20:01 ` Rahul Jadhav
2002-11-16 18:58 ` Joel Newkirk
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='004701c32636$640deeb0$010319ac@jhime' \
--to=jhime@synchro.com.br \
--cc=georgev@citadelcomputer.com.au \
--cc=netfilter@lists.netfilter.org \
--cc=raymondl@knowledgefactory.co.za \
/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