I have been playing starcraft on battle.net with 2.2.x kernels and have
had no problems at all. I don't even have to set up any special rules, it
works fine with plain masquerading. Looking at your setup I don't see any
rules for forward, only input and output, maybe you need to change that.
My ipchains rules are simply deny all forwarding except from my masqed
box, nothing needed for input and output.
Andrew Gaskill
[EMAIL PROTECTED]
On Wed, 17 Mar 1999, Jeffery Jones wrote:
>
> I have successfully played SC on Battlenet for many months on the older
> kernels without a hitch. Both ipautofw and ipportfw worked very well. After
> upgrading to 2.2.1 and ipchains performance is spotty at best...ditto with
> 2.2.3. Everything else seems to work fine through the masq. Here's some
> details:
> Port 6112 is open and forwarding tcp and udp to the internal machine
> ----------------------------------------------------------------------------
> ------------------------
> EXTERNAL_INTERFACE = "eth0"
> ANYWHERE = "any/0"
> UNPRIVPORTS = "1024:65535"
> IPADDR = "<my ip>"
> WINBOX = "<my internal machine>"
>
> ipchains -A input -i $EXTERNAL_INTERFACE -p UDP \
> -s $ANYWHERE $UNPRIVPORTS \
> -d $IPADDR 6112 -j ACCEPT
>
> ipchains -A output -i $EXTERNAL_INTERFACE -p UDP \
> -s $IPADDR 6112 \
> -d $ANYWHERE $UNPRIVPORTS -j ACCEPT
>
> ipchains -A input -i $EXTERNAL_INTERFACE -p TCP \
> -s $ANYWHERE $UNPRIVPORTS \
> -d $IPADDR 6112 -j ACCEPT
>
> ipchains -A output -i $EXTERNAL_INTERFACE -p TCP \
> -s $IPADDR 6112 \
> -d $ANYWHERE $UNPRIVPORTS -j ACCEPT
>
> #ipmasqadm portfw -a -P tcp -L $IPADDR 6112 -R $WINBOX 6112
> #ipmasqadm portfw -a -P udp -L $IPADDR 6112 -R $WINBOX 6112
>
> ipmasqadm autofw -A -r tcp 6112 6112 -h $WINBOX
> ipmasqadm autofw -A -r udp 6112 6112 -h $WINBOX
> ----------------------------------------------------------------------------
> --------------
> I can connect to Battlenet and only host a game...joining doesn't work.
> I can host Fsgs (bnet emulator) on my internal machine but cannot host a
> game...only join.
> As you can see I've tried both autofw and portfw with the same results. A
> tcpdump doesn't point out anything glaring to a rookie like myself.
>
> I've chased lots of threads only to find general help on getting SC to work
> through masq. Any ideas?
> Much appreciated...
> Jeff
>
>
>
>
>
> _______________________________________________
> Masq maillist - [EMAIL PROTECTED]
> http://tiffany.indyramp.com/mailman/listinfo/masq
> Admin requests can be handled by web (above) or [EMAIL PROTECTED]
>
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
