Re: [Leaf-user] (no subject)
Scott, OK...I can ping the server machine from the LRP box. When I checked the log, the only thing in there even close to the time I tried to connect to the server is this: Sep 12 22:26:17 My_LRP_Friend kernel Packet Log: input DENY ppp0 PROTO=17 195.5.80.139:2739 my ext ip:27018 L=40 S=0x00 I=64313 F=0x T=109 (#55) Sep 12 22:30:22 My_LRP=Friend /USR/SBIN/CRON[1728]:(root) CMD (etc/multicron -p) It doesn't look like anything to me except that the one at 22:26 tried to connect to port 27018...strange. I know I did not try to connect to port 27018 as I tried several times from a dial-up connection. What I did is try to add the server to my favorites within CStrike. The server shows up with ?...meaning it's unavailable. I tried to connect anyway and it just times out. Also...I noticed today that my LRP package starts my adsl connection, then when echowall starts...I get a message saying There already seems to be an ASDL connection... and then echowall continues to load. Everything seems to work just fine otherwise. I don't know if that means anything at all. We are getting close...thanks again. Mark - Original Message - From: Scott C. Best [EMAIL PROTECTED] To: Mark W. Windish [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, September 12, 2001 12:39 AM Subject: Re: [Leaf-user] (no subject) Mark: Okay, so the server allocates the correct IP address, that's a start. Can I ask though: from the LEAF firewall box, can you ping this 192.0.0.0 machine successfully? Perhaps you just meant that IP address as an example, but perhaps not. Also, importantly, type this after you try to connect to your server and fail: tail /var/log/syslog. The firewall *should* be logging any packets that are not getting passed on to your game-server properly. Sure, they'll be other noise in those logs (CodeRed remnants, for instance), but every time you try to connect and fail, a repeatable patch of packet logs should be created. If you could email those along, that'd help. Lastly...don't add 27016 into echowall.conf. Rather, add it into echowall.rules. Open that file for edit, scroll down to the HLIFE section, and copy the 2 lines that have 27015 in them, and repeat them using 27016. So the new lines would look like: #HLIFE#$IPCHAINS -A input -s 0.0.0.0/0 -d $IP_EXT/32 27016 -p udp -j ACCEPT #HLIFE#$IPMASQADM portfw -a -P udp -L $IP_EXT 27016 -R $HLIFE_HOST 27016 Try those, try the firewall check, and keep me posted. Getting close! -Scott I tried the +ip command and no go...I get a message from the server couldn't allocate dedicated server ip port. Now if I just run it without the +ip command it starts and allocates a server IP address of 192.0.0.0 which is my internal ip. I can connect to the server from my other internal machines (by pointing to the internal ip of the server) but nobody can connect from outside of the firewall. When echowall starts is says the the HLIFE service is started on 192.0.0.0 which is correct. I changed the echowall conf to allow port 27016 ( and added the command -port 27016 to the server exe) also so that I can run the server and play from the same machine if needed (the server will use 27016 while the client uses 27015). This shows up in my firewall rules so I'm assuming I did it correctly. I know there is a way to make this work...and I am sure it's all in the HLife server end. I'll keep you posted. Thanks again. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] (no subject)
Scott, I tried the +ip command and no go...I get a message from the server couldn't allocate dedicated server ip port. Now if I just run it without the +ip command it starts and allocates a server IP address of 192.0.0.0 which is my internal ip. I can connect to the server from my other internal machines (by pointing to the internal ip of the server) but nobody can connect from outside of the firewall. When echowall starts is says the the HLIFE service is started on 192.0.0.0 which is correct. I changed the echowall conf to allow port 27016 ( and added the command -port 27016 to the server exe) also so that I can run the server and play from the same machine if needed (the server will use 27016 while the client uses 27015). This shows up in my firewall rules so I'm assuming I did it correctly. I know there is a way to make this work...and I am sure it's all in the HLife server end. I'll keep you posted. Thanks again. Mark - Original Message - From: Scott C. Best [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, September 11, 2001 5:59 PM Subject: [Leaf-user] (no subject) Mark: Hope your HL problems are getting better. Two quick thoughts: Thanks for the replies...I believe the problem lies in the CStrike server config, since this is where the 169.254.0.0 address shows up. When try to run a server on another machine without a WAN adapter...it shows as having the Internal network IP address (192.0.0.0) of the LAN adapter. I believe the echowall config is correct...HLIFE is specified in services, the MACID is there (i even tried to specify all just for the hell of it), and I did change IF_EXT to ppp0 instead of eth0. When I use weblet to see the firewall rules, it appears as though the rules are applied, which is why I agree that I am missing something on the server end. When you echowall start, what it tells you at the end, about which services have been enabled to which IP addresses, is true. :) I guess I would want the server to show the internal LAN IP address (as opposed to the 169.254.0.0), then post the external IP address for people to connect. I will fool around with it more tonight. Right, exactly. Try using the +ip command that Alec suggested when you start the server. Then, from a different ISP altogether, point a CStrike client to your firewall's external interface. It should connect. Since it's a PPPoE setup, this IP address could change frequently, but we can talk about dynamic-DNS once you get the initial connection going. Good luck! -Scott ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] echowall 1.3 released
I am trying to get a CounterStrike server going using this release. The firewall seems to work and the new additions to the services are great. The problem is, when I start the server, it keeps trying to use a 169.254.*.* IP address which is the bogus address assigned by Windows when one is not found. This is the address of my WAN Adapter, and if I disable it, the server then tries to use the Internal Ip address of my LAN Adapter...both of which are not seen from outside of the firewall. I know the external IP address...but I use PPPoE, and am using Kenneth Hadley's PPPoE package. I added HLIFE to the Wanted Services, and added the MAC Address for the machine acting as the server, and it shows the services directed to the correct machine (when starting Echowall), using the correct Internal IP address. Any ideas what I am missing? Any help would be appreciated. Mark - Original Message - From: Scott C. Best [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, September 08, 2001 4:05 AM Subject: [Leaf-user] echowall 1.3 released Heyaz. I found a spare pair of hours over the last few days, and so the latest version of echowall has now been posted to the usual places: ftp://ftp.echogent.com/EchoWall/echowall.lrp http://leaf.sourceforge.net/devel/sbest/echowall/ Here are the changes from 1.22: 1. Basic DMZ support. If you want the HTTP server to be treated with DMZ considerations, simply put HTTP into the DMZ_SERVICES list. More details in the README file. 2. Added support for Half-Life, its descendant Counter Strike, and Unreal Tournament. Whole list of masq apps directly supported is now over 30. 3. Added the all designation for port forwarding. So if you want to enable IPSEC to all of your LAN members, put all into the IPSEC_HOST_MACID line. Works for both PPTP and IPSEC, so far. Hope it proves useful! Feedback welcome. cheers, Scott ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
