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
