From: "Emilio Lombardo" <emiliokatia@terra.com.br>
To: RODRlGO <ro.garcia@gmail.com>,
netfilter@lists.netfilter.org,
Jason Opperisano <opie@817west.com>
Subject: Re: Fw: Upgrading kernel 2.4.26 cuts out DNAT --to rules.....!!??
Date: Wed, 2 Feb 2005 16:51:51 -0200 [thread overview]
Message-ID: <007701c50958$41a45d30$1d01000a@cingo.net> (raw)
In-Reply-To: 20050202162051.GA331@bender.817west.com
thanks Jason :-)
this procedure you passed was exactly what the people did....
I'm beginning to think that the bug could be originated from the fact that
we installed the new iptables up on the other and probably this merging
didn't fit good or some /bin directory of the old one still stands there
The idea was to remove the content of all the iptables and reinstall the new
one with the apt-get after having deleted all manually
You guess it may work out ?
I hope so...:-)
Any suggestion is well accepted !
thanks again!!
----- Original Message -----
From: "Jason Opperisano" <opie@817west.com>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, February 02, 2005 2:20 PM
Subject: Re: Fw: Upgrading kernel 2.4.26 cuts out DNAT --to rules.....!!??
> On Wed, Feb 02, 2005 at 02:02:51PM -0200, Emilio Lombardo wrote:
>> So what we did was upgrading to iptables 1.2.11 on kernel 2.4.26 and
>> recompiling it whithin patch-o-matic and it worked out !
>> Now we got simultaneous and various vpn on gre protocol perfectly working
>> passing by the firewall whitout any problem (and of course it was really
>> the firewall because we tested the vpn's bypassing it and they worked.all
>> toghether...)
>> Well...now when everithing looked working but than debugging the internal
>> rules we saw that any attempt to add a "DNAT --to" always got an answer
>> of
>> Invalid Argument ..........the same rules that before was working
>> ....!!!!!And here came the problem.....
>> How is it possible for us making both instances (The VPN's and the
>> DNAT --to rules) work togheter...is there any linux guru...:-) who can
>> lend a hand and help us to find a way out in this maze ?
>
> it sounds like you didn't compile iptables *after* applying POM and
> recompiling your kernel. steps are:
>
> apply patches from POM
> recompile kernel
> recompile iptables
>
> -j
>
> --
> "Simpson, Homer Simpson, he's the greatest guy in his-tor-y. From
> the town of Springfield, he's about to hit a chestnut tree....D'oh!"
> --The Simpsons
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 27/1/2005
>
>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 27/1/2005
next prev parent reply other threads:[~2005-02-02 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 16:02 Fw: Upgrading kernel 2.4.26 cuts out DNAT --to rules.....!!?? Emilio Lombardo
2005-02-02 16:20 ` Jason Opperisano
2005-02-02 18:51 ` Emilio Lombardo [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 18:54 Gary W. Smith
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='007701c50958$41a45d30$1d01000a@cingo.net' \
--to=emiliokatia@terra.com.br \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
--cc=ro.garcia@gmail.com \
/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