Ray, Response inline:
Ray Olszewski wrote: > Kory -- > > I haven't used EchoWall in some time now, and Scott's added a lot to it > (including *all* the support for game servers) since I last worked on it. So > I can't give you a direct answer as to what is wrong. But if you provide > some additional diagnostics, I (or Scott, when he sees this thread) may be > able to help. > > 1. What is the output of "ifconfig -a" or "ip addr show" (whichever command > your LEAF system has)? ip addr show reports: 1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope global lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:20:af:33:92:ec brd ff:ff:ff:ff:ff:ff inet 65.28.237.42/23 brd 255.255.255.255 scope global eth0 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:20:af:33:e2:3f brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1 > > > 2. In echowall.run, what do the lines in the "QUAKE" block look like (after > you've configured the package - look for any lines that reference port 4242)? I could not find echowall.run > > > 3. After you've run the script, what actual ipchains rules are in place for > port 4242? Probably, you can get the relevant entries with this command: > > ipchains -L -n -v | grep 4242 > I get 0 0 ACCEPT tcp ------ 0xFF 0x00 * 0.0.0.0/0 65.28.237.42 * -> 4242 > > Aside from these specific questions, I note that the header of the QUAKE > block in echowall.rules reads "Quake [still needs testing]". So some actual > debugging may be needed. To that end, can you provide any more details as to > what the failure mode seems to be when you say "When I start a dedicated > Quake2 or Quake3 server I am unable to connect"? Has anybody else on the > list tested a Quake server successfully with EchoWall? The failure is that the Quake console on the client says : connecting 65.28.237.42 connecting 65.28.237.42 connecting 65.28.237.42 connecting 65.28.237.42 connecting 65.28.237.42 But never connects. I am able to connect over my local net and the server works fine. Thank you, Kory <SNIP> _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user