From: ASC - Ronald Roeleveld <r.roeleveld@ascinternational.nl>
To: 'saint' <nagajuna@optushome.com.au>
Cc: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: RE: Port forward
Date: Tue, 4 Feb 2003 14:43:42 +0100 [thread overview]
Message-ID: <D007132BBC42D5118FD20002A52844414BCF34@ASC01> (raw)
Why I used telnet was just for testing. I wanted to test to make sure that
if I connected to port 25 with telnet to my firewall that it redirected me
to the mail server. And as it seems it doesn't work, because I get an error
that no connection can me estabslihed. And offcource for management purpose
I use SSH..:)
-----Original Message-----
From: saint [mailto:nagajuna@optushome.com.au]
Sent: dinsdag 4 februari 2003 14:31
To: ASC - Ronald Roeleveld; Netfilter Mailing List
Subject: RE: Port forward
I don't know what your setup is but I myself explicitly FORWARD
things to telnet:
e.g:
# Allow access to machines from the private LAN:
iptables -A FORWARD -i INTERFACE_CONCERNED -o OUTPUT_INTERFACE -p tcp \
-s $LAN_MACHINES --sport $UN_PRIVILEGED_PORTS \
-d $DESTINATION_ADDRESS --dport 23 \
-m state --state NEW -j ACCEPT
you get the hint.
Any way why use telnet? I recommend secure shell (tcp port 22).
Santos.
Security is a blessing.
next reply other threads:[~2003-02-04 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 13:43 ASC - Ronald Roeleveld [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 22:29 Messages to console Len L.
2003-08-19 10:58 ` André Valente
2003-08-21 13:38 ` Port forward Rimas
2003-02-04 13:20 Eugene Joubert
2003-02-04 13:11 ASC - Ronald Roeleveld
2003-02-04 13:28 ` Patrick Maartense
2003-02-04 13:31 ` saint
2003-02-04 10:56 ASC - Ronald Roeleveld
2003-02-04 11:53 ` Sven Schuster
2003-02-04 10:41 Eugene Joubert
2003-02-04 10:31 ASC - Ronald Roeleveld
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=D007132BBC42D5118FD20002A52844414BCF34@ASC01 \
--to=r.roeleveld@ascinternational.nl \
--cc=nagajuna@optushome.com.au \
--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.