From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: Doug C <the_wasp@game-nation.net.nz>
Cc: netfilter@lists.netfilter.org
Subject: Re: Remapping of starcraft UDP port 6112
Date: Wed, 20 Apr 2005 11:23:54 -0500 [thread overview]
Message-ID: <4266821A.1050500@riverviewtech.net> (raw)
In-Reply-To: <000901c5457c$14e461e0$3800a8c0@Dewasp>
> cheers for spoting that the rules were backwards, i think i must have
> stuffed them up when putting them into the email.
Thanks. It's what this list is for, to help people.
> is it actually possible for iptables/netfilter to redirect the packets the
> way i want it to?
I would think yes. I don't know of any reason why you would have to explicitly write rules for each system. The only reason I can possibly think of is that the NATing code *might*, however not likely, be getting confused by the fact that the traffic is RELATED in such that both internal clients would be talking to the same server.
> if it is possible i dont see why it shouldnt work because as i said in the
> first question warcraft can use any port it pleases therefor the protocol
> must be able to handle it
Can we see a copy of your entire firewall script to make sure that there is nothing just slightly off about it?
Grant. . . .
next prev parent reply other threads:[~2005-04-20 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 6:58 Remapping of starcraft UDP port 6112 Doug C
2005-04-19 14:24 ` Sebastian Docktor
2005-04-19 19:23 ` Taylor, Grant
2005-04-20 7:39 ` Doug C
2005-04-20 16:23 ` Taylor, Grant [this message]
[not found] ` <000601c54639$89ff0940$3800a8c0@Dewasp>
[not found] ` <42674EFD.90803@riverviewtech.net>
[not found] ` <000601c546d4$b32848e0$3800a8c0@Dewasp>
2005-04-22 4:31 ` Taylor Grant
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=4266821A.1050500@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@lists.netfilter.org \
--cc=the_wasp@game-nation.net.nz \
/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