Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It will depend on how you rules are currently set up. Are you currently filtering outbound traffic?
When you say in and out does that mean that battle.net connects to your host on ports 4000, 6113:6119 or does in and out just mean that reply packets on your session need to get back in? Also do you have a network/ip list for the battle.net servers?
The following will allow inbound and outbound connections on the port ranges listed TO THE WORLD.
iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 4000 -j ACCEPT
iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 6113:6119 -j ACCEPT
iptables -I INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -I OUTPUT -p tcp -m state --state NEW -m tcp --dport 4000 -j ACCEPT
iptables -I OUTPUT -p tcp -m state --state NEW -m tcp --dport 6113:6119 -j ACCEPT
iptables -I OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
These rules may or may not make sense depending on your current configs. If when doing iptables -L you see that the current OUTPUT chain is empty then ignore the three OUTPUT commands above. If your firewall rules already have an accept rule for related and established then ignore the related/established rule above and add an index after INPUT that is below the existing related/established rule.
But honestly you may be best off using the firewall config utility shipped with your distribution. It will add rules in the proper chains in the proper fashion as the other rules.
>>When you say in and out does that mean that battle.net connects to your host >>on ports 4000, 6113:6119 or does in and out just mean that reply packets on >>your session need to get back in? Also do you have a network/ip list for the >>battle.net servers?
I think other players need to connect to my host on ports 4000, 6112:6119 through linux box
I searched ip list for battle.net didn't yield result.
ok these commands open the ports on linux box but problem is now I can't connect to battle.net server
is something wrong with these commands to open the port and play game at battle.net?
How come this works with bittorrent but not with battle.net server?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.