From: <netfilter@sbgit.com>
To: netfilter@lists.netfilter.org
Subject: Still having problems with forwadding
Date: 15 Mar 2004 08:36:00 UT [thread overview]
Message-ID: <DIIE.000000FE00002A57@sbgit.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
Hi,
i still having a lot of problems with the forwading of my vpn tunnel.
Now i can't connect to my system anyway?
The rest of my script (emule) has problems to, after i aplied the pptp patch with pom
and copiled the newest iptables version to my kernel.
Systemcheme:
http://support.sbgit.com/Firewall.jpg
Firewall Script:
http://support.sbgit.com/firewall
Thanx Peter
[-- Attachment #2: Type: text/html, Size: 1010 bytes --]
next reply other threads:[~2004-03-15 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 8:36 netfilter [this message]
2004-03-15 8:50 ` Still having problems with forwarding Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 13:26 Still having problems with forwadding peter.gehle
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=DIIE.000000FE00002A57@sbgit.com \
--to=netfilter@sbgit.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