Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "P.Italiaander" <pc-secure@home.nl>
To: netfilter@lists.netfilter.org
Subject: Re: iptables multiple clients internal network warcraft3
Date: Mon, 12 May 2003 01:06:53 +0200	[thread overview]
Message-ID: <200305120106.53047.pc-secure@home.nl> (raw)
In-Reply-To: <000001c317c0$a94de540$0200a8c0@knighthawk>

Op zondag 11 mei 2003 15:24, schreef Thomas Stian Bergheim:
> 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,

The clue is, use Nat

It's possible ,I did it with Counterstrike 3 games at the same time was max.
You have to use Nat or Masquerading .
The limit of 3 was because the Counterstrike server won't let me connect
with more then 3 games, since we use  Nat or Masq, the game-server sees
3 connections from the same IP number. loading game 4 was denied.

The firewall/router himself knows how to deal with the different IP's.

- make sure you authorize tcp/udp ports above 1024: outbound

I don't have specific rules for you , I have @home broadband , but this
is what your looking for.

Pascal


  reply	other threads:[~2003-05-11 23:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-11 13:24 iptables multiple clients internal network warcraft3 Thomas Stian Bergheim
2003-05-11 23:06 ` P.Italiaander [this message]
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=200305120106.53047.pc-secure@home.nl \
    --to=pc-secure@home.nl \
    --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