Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: NAT and openvpn
Date: Sat, 28 Mar 2009 09:22:43 +0100	[thread overview]
Message-ID: <49CDDE53.9040305@chello.at> (raw)
In-Reply-To: <1238220237.911422960@192.168.1.202>

% iptables -t nat -A PREROUTING -s $VPNIP -j SNAT --to-source $PUBIP
> % iptables -t nat -A POSTROUTING -s $PUBIP -j DNAT --to-destination $VPNIP 


>hanks for the reply ... when I try that I get:

>	mothership:~# iptables -t nat -A PREROUTING -s 10.8.0.2 -j SNAT --to-source <ip omitted>
>	iptables: Invalid argument



jason.faulkner@mailtrust.com wrote:
>> iptables: Invalid argument
>>     
>
> Perhaps this? http://www.netfilter.org/documentation/FAQ/netfilter-faq-3.html#ss3.20
>
> --
> Jason Faulkner 
> Linux Systems Engineer
> Mailtrust, a division of Rackspace
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   
good morning guys:
   DNAT
       This  target  is  only  valid  in the nat table, in the 
PREROUTING and OUTPUT chains

   SNAT
       This  target  is  only  valid  in the nat table, in the 
POSTROUTING chain.

not the kernel suddenly breaking.
RTFM! :)

everybody sleeping? ;-)

greets

Mart

  reply	other threads:[~2009-03-28  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 21:14 NAT and openvpn G. Skillen
2009-03-28  2:39 ` jason.faulkner
2009-03-28  2:51   ` G. Skillen
2009-03-28  6:03     ` jason.faulkner
2009-03-28  8:22       ` Mart Frauenlob [this message]
2009-03-28  9:24     ` Nikolay S. Rybaloff
2009-03-28 14:49       ` G. Skillen
2009-03-28 11:04 ` G.W. Haywood
2009-03-28 14:51   ` G. Skillen

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=49CDDE53.9040305@chello.at \
    --to=mart.frauenlob@chello.at \
    --cc=netfilter@vger.kernel.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