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 I 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.
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. Thanks for the feedback.
Mark
P.S. Thanks to scott for an awesome package! It really makes life easy for us
newbies...
Alec Miller <[EMAIL PROTECTED]> wrote:
> FYI --
Remember that the HL engine will only use Public IP addresses in order to be
seen in a Game browser.
(GameSpy, or the HL server browser)
You can still launch the server but you will have to post the External IP
somewhere (webpage,e-mail) that will forward the packets to the internal IP
so people can connect to it.
the +ip option is if you have Multiple Nics/IPs on the same machine (or Nic)
so you can bind the game to that specific Nic or IP. It will not work if
the IP does NOT exist on that machines Nics.
----- Original Message -----
From: DPG
To:
Sent: Tuesday, September 11, 2001 12:44 AM
Subject: FW: [Leaf-user] echowall 1.3 released
There is a command line variable for the HL server to explicitly state the
IP address. The shortcut that starts your server should look something like
this:
\hlds.exe -game cstrike +ip
+maxplayers 10
Or, when you lose your baby teeth, and move up to Linux , it will look
like this:
./hlds_run -game cstrike +ip +maxplayers 10
All the goods on server admin are here:
http://server.counter-strike.net/howto.html
Makes me miss the old days, before Speakeasy moved my POP 800 miles further
down the copper, and raised my gateway ping from 100 ms. That move
put my servers out of business. :( Now I just have an expensive,
high-latency SDSL line ---- but no servers...
Did I mention Speakeasy is off my holiday greeting card list?
D
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott C. Best
Sent: Monday, September 10, 2001 9:58 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] echowall 1.3 released
Mark:
Heya. This sounds like it's either an interface problem,
or a problem with the CounterStrike server setup. In echowall.conf,
did you choose "ppp0" or "eth0" for IF_EXT? For PPPoE, I believe
it should be the first one.
The 169.254.0.0/16 address you speak about is actually
what a DHCP client will default to if a valid DHCP server doesn't
give it a lease when it asks for one. AFAIK, it shouldn't be a
usable address, so I'm confused where you're seeing it. Just in
the CStrike server, or do you see it in "ip addr show"?
Finally, perhaps there's a config setting in the CStrike
server, telling it whether to use static or DHCP addresses? I
could imagine that the server itself is asking for an DHCP lease
unless you tell it not to. Sorry that I don't know the particulars
of this server setup any better...
Lemme know what you find out!
cheers,
Scott
> 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.
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
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
