All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Stian Bergheim" <bjartebe@eunet.no>
To: netfilter@lists.netfilter.org
Subject: iptables multiple clients internal network warcraft3
Date: Sun, 11 May 2003 15:24:28 +0200	[thread overview]
Message-ID: <000001c317c0$a94de540$0200a8c0@knighthawk> (raw)

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Hi!
 
I'm playing warcraft behind a firewall (iptables) which runs on redhat8.
 
It works fine for me, but other clients on my internal network
(192.168.0.x) can't join me.
I guess this is because the packets they reply with have a different
source adress. So the solution should be fairly simple using iptables.. 
But I've tried many things, with no luck...
 
My server has two eths, one for the dsl connection, the other one for
the local network.
 
Anyone got a working setup with this or anything?
 
Thanks,
 
-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

[-- Attachment #2: Type: text/html, Size: 6072 bytes --]

             reply	other threads:[~2003-05-11 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 13:24 Thomas Stian Bergheim [this message]
2003-05-11 23:06 ` iptables multiple clients internal network warcraft3 P.Italiaander
2003-05-12  3:27 ` Myles Uyema

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='000001c317c0$a94de540$0200a8c0@knighthawk' \
    --to=bjartebe@eunet.no \
    --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.