2005/6/30, Rober Morales <[EMAIL PROTECTED]>: > > > Marshall escribió: > > Hola, el xLink kai es un programa para jugar Xbox on-line esta es su > > pagina web http://www.teamxlink.co.uk/ tiene su version para Linux > > i386 y me la e bajado para usarla con mi Debian Sarge, > > > > Este es el fichero README del programa > > > > 10-May-2005 > > WARNING: don't use the old version of kaid.conf > > > > - Edit kaid.conf and put your username and password > > - Do other changes on kaid.conf (instructions inline on that file) > > - Start kaid with (root required): > > ./kaid -c kaid.conf > > - The flag -h should help you with more options (./kaid -h) > > > > **Compiled by Cyborgas for TeamXlink** > > > > cuando ejecuto ./kaid -c kaid.conf me sale este mensaje en la consola > > > > > > ./kaid -c kaid.conf > > KAID: Kai Engine for Linux is initialising... > > KAID: Kai Engine for Linux is starting... > > THREAD: Engine thread started... > > KAID: Failed to create UI socket... > > > > Y no se habre el programa... > > > > esa hache es dolorosa > > > > > este es una copia del archivo kaid.conf > > > > ################################################################################ > > # Kai Engine Configuration File > > # > > # This file contains the configuration options for Kai Engine. > > # There are some fields which can be modified, the descriptions of these > > fields > > # and their default values are listed below > > # > > > > # Verbosity : Debug output verbosity. Options are as follows: > > # 0 - Silent apart from starting / stopping messages, and > > init failures. > > # 1 - As 1, but shows import events such as UI > > attach/detach, console detection, > > # orb connection / loss. > > # 2 - As 2, but more detailed, showing thread start/stop > > events, DHCP > > # events, and other important information. > > # 3 - Debug - same as 2, but with lots of extra information > > - useful > > # for diagnosing segfaults etc. > > Verbosity = 3 > > > > # UIBind : Specifies which ip/port kaid will use to listen > > for controller > > # UIs > > # Ex.: 192.168.0.138 <http://192.168.0.138>, 10.0.0.1:34522 > > <http://10.0.0.1:34522>, :34522 (default) > > UIBind = :34522 > > > > # OrbPort : Specifies which port kaid will use to probe(UDP) and > > talk to > > # Orbitals (TCP) > > # Ex.: 34525 > > # Default : 34525 (default) > > OrbPort = 34525 > > > > # EngineBind : Specifies the IP:port to listen for the engine > > (UDP socket); > > # (port should be forwarded in your router if > > using NAT) > > # Ex.: 69.69.69.69 <http://69.69.69.69>, > > 69.69.69.69:37500 <http://69.69.69.69:37500>, :37500 > > EngineBind = :0 > > > > # Engine PAT : Tells the orbital server to use your perceived UDP > > port, as opposed to the > > # one specified in EngineBind. Ignored if EngineBind is 0. > > EnginePAT = 0 > > > > # SniffDevice : NIC to sniff for console traffic (eth0, ethX, > > ...). Will be used > > # for packet injection too. > > # Ex.: eth0 (default), en0 (Mac OSX), > > SniffDevice = eth0 > > > > # MacLearningMode : Tells the engine how it should learn about your > > console(s). > > # There's still the old, legacy mode: Manual, where you > > should enter you > > # console(s) mac address(es) under ConsoleMacs. > > # New options are: Auto and FirstFound. > > # * Auto: Using this mode, each and every packet > > on your network is > > # sniffed and analyzed by Kai Engine. Those who > > come from remote hosts > > # are tagged using a mac cache mechanism and > > passed to the Ethernet > > # frame handler. Inside that handler, if ether > > src doesn't correspond > > # to any of the remote mac addresses, engine > > assumes its local and adds > > # to local device cache. Keeps doing it for the > > engine lifetime, and > > # behaves the same way all the times it runs. > > Uses more CPU than any > > # other mode (Except FirstRun that behaves in the > > same way for the first > > # time it runs). > > # This mode allow you to use any number of consoles. > > # * FirstFound: Now, this one is tricky and maybe > > the most balanced option for > > # those using only one console. The engine will > > behave in auto mode until 1 > > # *ONE* local device is found. After that point, > > the pcap sniffer is restarted > > # using that mac adddress as pre-filter. All this > > happens in real time, no > > # restart is needed. No fs cache file is used, > > and it will behave like this > > # everytime it runs. After the device is found, > > the engine will behave exactly > > # like Manual mode. This mode will have the same > > CPU load until it finds a > > # local device. Will be very fast if you already > > had your console turned on. > > # * Manual: Finally, Manual mode. This legacy mode > > should be used whenever > > # performance is an issue. You'll have to specify > > your console(s) mac address(es) > > # yourself. No processing is done for sniffed > > packet besides sending to > > # remotes. This is the Turbo Boost Mode. > > MacLearningMode = Auto > > IgnoreMacs = > > > > # *** If using MacLearningMode = Manual, make sure to use this option *** > > # ConsoleMacs : You can and should specify your console(s) mac > > address(es) > > # here. They'll be used as pcap filters reducing > > CPU load > > # processing each packet. It will also avoid > > sniffing > > # incoming/injected packets to be caught. Format > > must be > > # standard tcpdump format: Ex.: 00:ff:dd:5b:31:ac > > # You can specify more than one mac address in a > > ; separated > > # list. Will be parsed and "OR'ed" in filter. > > List should end > > # with ";" or last element will be discarded. > > ConsoleMacs = > > > > # ConfigURL : URL where orb list is published (and extra stuff) - > > best not to mess with this. > > ConfigURL = www.teamxlink.co.uk/connector/clientgetconfig.php > > <http://www.teamxlink.co.uk/connector/clientgetconfig.php> > > > > #Authentication - set username and password and AutoLogin=1 for an easy > > life... > > Username = > > Password = > > AutoLogin = 0 > > > > # Xbox DHCP setting - please leave alone, unless playing with emulators > > or DoomX etc. > > XBoxHomebrew = 0 > > > > > > Quien me ayuda plisssss , Gracias > > ¿a qué? > A mi se me hace que es problema de NAT, porque no se pudo crear el socket, seguro el server esta enviando una respuesta a ese socket pero no lo encuentra.
Solucion: Esta en tu mismo archivo de configuracion :) Para otra vez RTFM primero ;) Saludos, -- Diego Quintana Linux Registered User #382615 - http://counter.li.org/ Estudiante Ing de las Telecomunicaciones PUCP telf:+51197159419 ****** Sal del lado oscuro, usa Linux! ******
