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=0x0000 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
