Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Ashley M. Kirchner" <ashley@pcraft.com>
To: netfilter@lists.netfilter.org
Subject: iptables problem
Date: Tue, 01 Nov 2005 11:06:29 -0700	[thread overview]
Message-ID: <4367AEA5.7080501@pcraft.com> (raw)


    I have three machines on our private network that need unrestricted 
access to and from FTP.  These are little photo kiosks that periodically 
connect to the master service machine elsewhere through ftp to send 
files and then receives information back.

    The machine running iptables has eth0 with our public ip and eth2 
with the internal (192.168.x.x) ip (where the three machines are on.) 

    Help anyone?



             reply	other threads:[~2005-11-01 18:06 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 18:06 Ashley M. Kirchner [this message]
2005-11-02  0:31 ` iptables problem Buddy wu
2005-11-02  1:29   ` Ashley M. Kirchner
2005-11-02  1:37     ` Buddy wu
2005-11-02  5:56     ` Rob Sterenborg
2005-11-02  7:20     ` Nikolai Georgiev
2005-11-02  8:01       ` Rob Sterenborg
2005-11-02 22:49         ` Ashley M. Kirchner
2005-11-03  6:19           ` Rob Sterenborg
2005-11-03  6:45             ` Ashley M. Kirchner
2005-11-03 15:21               ` Re: iptables problem (nfcan: addressed to exclusive sender for this address) Jim Laurino
2005-11-03 16:02                 ` Ashley M. Kirchner
2005-11-03 16:23                   ` Sven Schuster
2005-11-03 17:17                     ` Re: iptables problem (nfcan: addressed to exclusivesender " Rob Sterenborg
2005-11-03 17:00                   ` Re: iptables problem (nfcan: addressed to exclusive (nfcan: addressed to exclusive sender for this address) sender " Jim Laurino
2005-11-03 19:57                     ` Ashley M. Kirchner
2005-11-04  5:00                       ` Re: iptables problem (nfcan: addressed to exclusive (nfcan: addressed to exclusive sender for this address) " Jim Laurino
2005-11-04  5:06                         ` Ashley M. Kirchner
2005-11-04  6:04                           ` Rob Sterenborg
2005-11-03 21:54             ` Re: iptables problem R. DuFresne
2005-11-04  0:51               ` Ashley M. Kirchner
2005-11-04  3:18                 ` R. DuFresne
2005-11-04  4:26                   ` Ashley M. Kirchner
  -- strict thread matches above, loose matches on Subject: below --
2008-09-05 11:12 Cam Bazz
2008-09-05 12:39 ` Matt Zagrabelny
2008-09-05 15:35 ` Grant Taylor
2007-10-06 16:28 IPtables problem Per Jørgensen
2007-10-06 18:25 ` Pascal Hambourg
2007-01-26 11:19 Iptables problem Saurabh Mehrotra
2007-01-26 13:53 ` Ted Phelps
2007-01-26 14:17   ` Saurabh Mehrotra
2007-01-26 15:17     ` Ted Phelps
2007-01-26 15:49       ` Saurabh Mehrotra
2007-01-26 15:55         ` Ted Phelps
2006-10-19  4:52 tarak
2005-11-08 17:08 IPTABLES PROBLEM Micol lupen
2005-11-08 18:56 ` Rob Sterenborg
2005-11-08 19:08 ` /dev/rob0
2004-08-25 20:04 Iptables problem Jason Opperisano
2004-08-25 19:52 Marcelo Sinhorini
2004-08-26  0:24 ` Jose Maria Lopez
2003-08-13 17:09 Glenn Hancock
2003-08-13 17:36 ` Rob Sterenborg
2003-05-14 11:45 IPTables problem Tech
2003-05-13 15:13 iptables problem hare ram
2003-05-13 17:02 ` Guilherme Viebig
2003-05-14 11:17   ` hare ram
2003-05-14 11:38     ` Bikrant Neupane
2003-03-13  9:57 Iptables problem De Jager Laubscher
2003-03-13 10:16 ` Maciej Soltysiak
2002-12-12 11:52 IPtables Problem Amit Kumar Gupta
2002-11-27  3:26 iptables problem 김도균
2003-01-17  5:32 ` Raymond Leach
2003-01-18  0:35 ` Diego Sarasua
2002-10-04 17:55 IPTables Problem Niel Harper
2002-06-25 11:55 Iptables problem Paulo Andre
2002-06-25 11:57 ` Ramin Alidousti
2002-06-25 10:47 Paulo Andre
2002-06-25 11:51 ` Ramin Alidousti
     [not found] <CC845BB8BC74D6119934000347DD23E87C0C09@jhbmail.autopage.co.za>
2002-06-24 16:03 ` Antony Stone
     [not found] <CC845BB8BC74D6119934000347DD23E87C0C07@jhbmail.autopage.co.za>
2002-06-24 14:26 ` Antony Stone
     [not found] <CC845BB8BC74D6119934000347DD23E87C0C01@jhbmail.autopage.co.za>
2002-06-21 14:44 ` Antony Stone

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=4367AEA5.7080501@pcraft.com \
    --to=ashley@pcraft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox