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
