You also need to open some other ports to get HL Server to work.
try opening TCP ports 6003 and 7001. But I don't remember if these are for
the clients or the Server.
----- Original Message -----
From: Mark W. Windish <[EMAIL PROTECTED]>
To: Scott C. Best <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 11, 2001 9:33 PM
Subject: 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
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
