All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Daniel Chemko <dchemko@smgtec.com>
Cc: alucard@kanux.com, netfilter@lists.netfilter.org
Subject: RE: forwarding
Date: Tue, 18 May 2004 15:15:44 -0400	[thread overview]
Message-ID: <1084907744.7259.62.camel@localhost> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF567934A@alderaan.smgtec.com>

On Tue, 2004-05-18 at 14:23, Daniel Chemko wrote:
> iptables -t nat -A POSTROUTING --destination ${server2} -j SNAT --to
> ${server1_internal_ip}
> 
> This is the last time I try to respond to you since you've been ignoring
> the rest. SNAT traffic from server 1 to server 2. Period. There's no
> magic. Put it in, then the system will magically work. Well, replace the
> ${}'s with the actual values first.
> 
> If you even get this email, let me know cause I feel like I'm falling on
> deaf ears.
Daniel, that was a problem but he has changed the default gateway to
ensure that the packets do make it back to the gateway.

From a previous post:
[root@linserv root]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.0     *               255.255.255.0   U     0      0        0
eth1
10.73.216.0     *               255.255.252.0   U     0      0        0
eth0
169.254.0.0     *               255.255.0.0     U     0      0        0
eth0
127.0.0.0       *               255.0.0.0       U     0      0        0
lo
default         192.168.0.1     0.0.0.0         UG    0      0        0
eth1

I believe 192.168.0.1 is the gateway.
-- 
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com



  parent reply	other threads:[~2004-05-18 19:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 18:23 forwarding Daniel Chemko
2004-05-18 18:42 ` forwarding Antony Stone
2004-05-18 18:50 ` forwarding alucard
2004-05-18 19:15 ` John A. Sullivan III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-26 17:48 forwarding amir_sarbazi
2004-05-18 20:48 forwarding Daniel Chemko
2004-05-18 21:15 ` forwarding John A. Sullivan III
2004-05-18 20:33 forwarding Daniel Chemko
2004-05-18 18:04 forwarding Daniel Chemko
2004-05-18 17:04 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:33 forwarding CPD - David Cardeñosa Rubio
2004-05-18 15:47 ` forwarding John A. Sullivan III
2004-05-18 15:51 ` forwarding Antony Stone
2004-05-18 14:22 forwarding alucard
2004-05-18 14:39 ` forwarding John A. Sullivan III
2004-05-18 14:49   ` forwarding alucard
2004-05-18 14:51     ` forwarding John A. Sullivan III
2004-05-18 14:56     ` forwarding Antony Stone
2004-05-18 14:57   ` forwarding alucard
2004-05-18 14:58     ` forwarding John A. Sullivan III
2004-05-18 15:12       ` forwarding alucard
2004-05-18 15:53         ` forwarding John A. Sullivan III
2004-05-18 16:38           ` forwarding alucard
2004-05-18 17:02             ` forwarding John A. Sullivan III
2004-05-18 18:21               ` forwarding alucard
2004-05-18 18:28                 ` forwarding Antony Stone
2004-05-18 18:42                   ` forwarding alucard
2004-05-18 19:22                 ` forwarding John A. Sullivan III
2004-05-18 21:33                 ` forwarding Antony Stone
2004-05-19  4:56                   ` forwarding Juan Hernandez
2004-05-18 15:09     ` forwarding Antony Stone
2004-05-18 15:40       ` forwarding alucard
2004-05-18 15:53         ` forwarding Antony Stone
2004-05-18 14:44 ` forwarding Antony Stone
2002-07-08  3:25 forwarding Tim
2002-07-08  0:30 ` forwarding Antony Stone
     [not found]   ` <003801c22632$521c93a0$1606d6d1@nebuchadnezza>
2002-07-08  0:53     ` forwarding Antony Stone
2002-07-08  4:03       ` forwarding Tim

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=1084907744.7259.62.camel@localhost \
    --to=john.sullivan@nexusmgmt.com \
    --cc=alucard@kanux.com \
    --cc=dchemko@smgtec.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.