Re: [newbie] Firewall/Tcp-ip problem...
There was an article on Mandrake Forum some time last month telling you which files Bastille firewall uses to set up the firewall policy. If you can find it all should become clear. Enjoy derek On Wednesday 16 January 2002 04:03, Ronald J. Hall wrote: Okay, this morning I ran the basic (Bastille?) firewall setup from the Control Center. Went thru it easily, no problems there. I didn't lose anything like mail services, ability to hit websites, etc, etc... However...(you just knew there was a however in there somewhere, didn't you?) I did lose something. Before I ran it, I could play networking via Winex with Diablo 2: Lord of Destruction. Now, I can join any of the games run by the Windoze boxes in our 3 comp Lan, but no one can join a game if I host it. I poked around, found that some stuff had been dropped from /etc/resolv.conf, and I re-added it. The last 2 lines here were gone. nameserver 192.168.0.1 darkforce nameserver 192.168.0.2 darkforce2 nameserver 192.168.0.3 darkforce3 After adding these 2 lines back, then doing a ifconfig eth0 down, ifconfig eth0 up, followed by mount -a, I was able to join games again. Still couldn't host one though. Does anyone know what network related files the firewall changes? I'm sure its just a small file somewhere, something like hosts allow or deny thats stopping the Windog machines from being able to play via tcp/ip with mine. Thanks in advance! ;-) Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Firewall/Tcp-ip problem...
Michael Viron wrote: You could try opening all ports to your internal network while keeping the rules for your external connection the same. It could be that your firewall is blocking connection attempts on whatever TCP / IP port Diablo 2 uses. Michael Thanks for the reply, Michael. Well, I kinda figured that...(not being sarcastic here-the thought had occurred to me!), but I was hoping someone had run into this problem before and could point me to a specific file. I did a search of the Newbie mailing list archives, and found -tons- of info about firewalls, but nothing related to this problem. I also tried the Mandrake forums and .org...again, nothing related. Well, methinks I'll re-run the firewall tool, and leave one section open at a time, until it works again. That at least, should narrow it down to where. Thanks again! ;-) -- /\ DarkLord \/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] Firewall - Tcp/ip problem partially solved.
Just shoot me. One answer was right in front of me in the forums. The firewall starts on bootup by default. No problem, first thing I usually do is hit the 'Net and check mail, so I'm protected. Logoff, and stop the firewall since I don't need it now. To stop the firewall, as root: service bastille-firewall stop Then, Diablo2: Lord of Destruction networking with WineX works fine. If I need to log back on to the 'Net before I shutdown again, I just issue a: service bastille-firewall start and the firewall resumes. Of course, just looking at the Bastille config file tells me there is a way to allow access from my Lan with the firewall up (although I don't know exactly -what- to enter there) but this works for now so... Thanks to all who replied! PS Its also kind of reassuring to know that the firewall is -blocking-. ;-) -- /\ DarkLord \/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] Firewall/Tcp-ip problem...
Typically the ipchains / iptables files are found in /etc/sysconfig/ . Check there for a file listing the bastille rules. If it's not there, it should be somewhere under /etc . I don't know exactly, as I add firewall rules by hand. Michael -- Michael Viron Registered Linux User #81978 Senior Systems Administration Consultant Web Spinners, University of West Florida At 09:53 AM 01/16/2002 -0500, you wrote: Michael Viron wrote: You could try opening all ports to your internal network while keeping the rules for your external connection the same. It could be that your firewall is blocking connection attempts on whatever TCP / IP port Diablo 2 uses. Michael Thanks for the reply, Michael. Well, I kinda figured that...(not being sarcastic here-the thought had occurred to me!), but I was hoping someone had run into this problem before and could point me to a specific file. I did a search of the Newbie mailing list archives, and found -tons- of info about firewalls, but nothing related to this problem. I also tried the Mandrake forums and .org...again, nothing related. Well, methinks I'll re-run the firewall tool, and leave one section open at a time, until it works again. That at least, should narrow it down to where. Thanks again! ;-) -- /\ DarkLord \/ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
