[crossfire] new metaserver

Brendan Lally B.T.Lally at warwick.ac.uk
Fri May 27 10:48:28 CDT 2005


>>>
     
     
      cerzeo at gmail.com
      
       05/27/05 16:33 PM >>>
     
     >
     
      And there is possible to create a metaserver using the port number 80 or 21 
     
     >
     
      (ftp port?).
     
     
>
     
      If not, can someone connect (extern to mi LAN), connect to my server?
     
     
>
     
      My LAN IP is 163.117.65.99, but when i visit this web www.whatismyip.com, it 
     
     >
     
      sas that my IP is 163.117.36.72. Can it be possible?
     
     Someone can explain me this?

>
     
      Me and sure many people are in a LAN, and proxy server have all ports closed, 
     
     >
     
      except 80, 21 and amsn port.
     
     
It looks like you mean that you have all ports other than 80, 21, and 6-whatever it is, blocked outbound. If this is the case, we would expect that you have all inbound ports blocked (otherwise such a measure isn't sensible.

Such configurations are normally only found in highly locked down environments.

The new metaservers will use HTTP, this means that a webserver is needed to be one. If you can run a webserver, you can run one, if you can access other web servers then you can use them (but crossfire doesn't use HTTP for server-client communications, so you won't be able to connect to a remote server.

You seem to be in a fairly large internal subnet though, so you should be able to run a server accessible in there quite easily. If you were to run a metaserver internally, you would be able to script the fetching of the server lists each day (or more frequently) and mirror them, propagating your own custom metaserver list.

This isn't useful though, since you wouldn't be able to connect to the remote servers....


    
    


More information about the crossfire mailing list