From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: ssh connection is not allowed in NAT, SUSE 9.2
Date: Tue, 19 Jul 2005 11:06:38 +0200 [thread overview]
Message-ID: <42DCC29E.5000603@mnemon.de> (raw)
In-Reply-To: <20050718132109.88338.qmail@web50210.mail.yahoo.com>
Fatih TURKMEN schrieb:
> Hi everybody,
> I am trying to create small NAT network on SUSE 9.2
> computers.I don't know what is missing in my iptables
> policy but I have added three rules for SNAT:
>
> 1) iptables -t nat -A POSTROUTING -o eth0 -j
> MASQUERADE
> 2) iptables -A FORWARD -i eth0 -o eth1 -m state
> --state RELATEd,ESTABLISHED -j ACCEPT
> 3) iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
>
> I stopped firewalls on local computers, and installed
> ssh server/client on all computers.I can ssh to local
> machines from locals.But I can't ssh to nat
> server.Also I can only ping one computer from NAT
> Server.
> When I try to ssh to local clients from NAT server I
> got either "No route to host" or "Connection refused"
> although I stopped firewalls on locals and set the NAT
> server as the default gateway for local clients.
Would you mind to provide the full ruleset of your nat box ? Preferably
the output of iptables-save ? A description of your network layout could
be helpfull too (networks, NICs,...). As there is "No route to host" the
routing table could give some enlightment. There are at least two
interfaces, so - is ip-forwarding enabled ? What does
netstat -tulpn | grep ':22'
give on the respective boxes ? When trying to connect via SSH to no
avail, what does
tcpdump -ni <respective_inerface>
give (try reducing other traffic) ? Questions over questions :)
Have a nice time,
Joerg
next prev parent reply other threads:[~2005-07-19 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 13:21 ssh connection is not allowed in NAT, SUSE 9.2 Fatih TURKMEN
2005-07-19 9:06 ` Jörg Harmuth [this message]
2005-07-19 14:59 ` R. DuFresne
2005-07-21 12:41 ` Fatih TURKMEN
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=42DCC29E.5000603@mnemon.de \
--to=harmuth@mnemon.de \
--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.