WRT54G/GS: run xlink without using the kaiStation image!

Posted: Thu Dec 09, 2004 11:29 pm

will anyone put out support for a linksys b router?

Posted: Thu Dec 09, 2004 11:30 pm

njhorn wrote:

tell me what I'm doing wrong?

hi, i guess you have to enter a game then hit play

i mean for example, halo2/USA/xxxx (11/12)
when you're in a game room, hit play

5L4Y3R wrote:

wait, I'm a dumba$$. Got it working. Great work and thanks for the quick tutorials.

do you get it working on daemon mode, or do you have to keep the telnet window open ?

Posted: Fri Dec 10, 2004 1:41 am

About daemon mode... did anyone tried "kaid -h"? is "kaid -d" not working for you?

Posted: Fri Dec 10, 2004 3:43 am

bernienoel wrote:

do you get it working on daemon mode, or do you have to keep the telnet window open ?

I got it to work with the telnet window open. When I tried daemon mode, kaid would not run.

Posted: Fri Dec 10, 2004 6:12 am

sorry for the noob question........
but is it possible for someone to integrate the kaid stuff into the existing Alchemy-6.0-RC1.w42 V2.04.4.8sv firmware? just so all the steps above could be avoided and so that its not in ram where it'll dissappear after reboot? then it'll be easy to just flash with new modified Alchemy-6.0-RC1.w42 V2.04.4.8sv firmware. or is this not possible since sveasoft hasnt released the gpl code for this release?

thanks

Posted: Fri Dec 10, 2004 8:15 am

i successfully connected to kai via the sveasoft firmware

is it supposed to continuously scroll TONS of crap while its connected?
It scrolls nonstop, even if the xbox is off. stuff like:

so i HAVE to execute via telnet everytime i want to connect? isnt that defeating the point?

BTW, which firmware do you guys recommend is better? sveasoft or alchemy?

Posted: Fri Dec 10, 2004 8:29 am

JAWS wrote:

sorry for the noob question........
but is it possible for someone to integrate the kaid stuff into the existing Alchemy-6.0-RC1.w42 V2.04.4.8sv firmware? just so all the steps above could be avoided and so that its not in ram where it'll dissappear after reboot? then it'll be easy to just flash with new modified Alchemy-6.0-RC1.w42 V2.04.4.8sv firmware. or is this not possible since sveasoft hasnt released the gpl code for this release?

thanks

ypi can go to
http://192.168.1.1
administration -> diagnostics
cut&paste your script then hit save startup

Posted: Fri Dec 10, 2004 8:46 am

THE WORKING DAEMON SCRIPT IS (at least on Alchemy RC3 lw03.1)

wget http://www.zbit.pt/kai/mips/fs/etc/kaid.conf -O /tmp/kaid.cnf
sed -e 's/00:50:f2:d4:f2:03/MAC_ADRESS/g' /tmp/kaid.cnf >/tmp/kaid.conf
wget http://www.zbit.pt/kai/mips/fs/usr/bin/kaid -O /tmp/kaid
chmod +x /tmp/kaid
/tmp/kaid -c /tmp/kaid.conf &

DON'T forget to type your xbox MAC adress in the script !!

to start up that script after every reboot,
1- http://192.168.1.1
2- Administration
3- Diagnostics
4- Run
5- copy and paste that script on the popup window
6- hit Save startup
7- the router reboots itself, you can switch on XBMC (make sure that you have set the router's IP, username, password on Kai config in XBMC

thanks TeamXlink, Frostbyte, Sveasoft, lonewolf

Posted: Fri Dec 10, 2004 9:41 am

^S^, the script i posted above is working except that if I quit a game = return to XBMC
kaid seems to be dead (there are still a lot of kaid process, but they don't send any data to xbmc... and i can't exit the current game room)

Posted: Fri Dec 10, 2004 1:37 pm

^b^ I used your script but with kaid -d for launch.

Was playing all lastnight. Jumping in and out of arenas was flaky now and then and required multipls B button pushes.

I will be adding the script to diag. tonight.

For the ^^^^ Sveasoft is the name of the company building the Alchemy firmware

Posted: Fri Dec 10, 2004 1:43 pm

Just occured to me. As long as the KAI team keeps that path for updates, we will always be getting the latest KAID on startup Laughing

Posted: Fri Dec 10, 2004 2:08 pm

Flyer007ma wrote:

Just occured to me. As long as the KAI team keeps that path for updates, we will always be getting the latest KAID on startup Laughing

i think that's the plan Smile

the most effortless update process : telnet and reboot Cool

(those with the kaistation image will have to reflash i think) Wink

Posted: Fri Dec 10, 2004 2:23 pm

Don't believe our hosts will be providing 1MB for each client everytime they reboot their box. Bandwith is expensive these days, if any of you wants to setup a mirror, I'll be glad to use it as binary repository for our releases.

I've had 7GB traffic just for kaibinary.bin in less than 24h... figures not far from that for mips/fs/.../kaid ... You do the math for every reboot, the 1MB download...

Cheers.

Joined: 30 Jul 2006 Posts: 0

We're going to make our changes to the Linksys source tree public (of course, we *must* as it's GPL) - they're mainly html changes in the UI, nvram things and a haxored broadcom.c

With this, im sure someone will see if theres room on the svea flash to add kaid..

TD

Posted: Fri Dec 10, 2004 3:10 pm

^S^ wrote:

I've had 7GB traffic just for kaibinary.bin in less than 24h... figures not far from that for mips/fs/.../kaid ...

Cheers.

OMG

Posted: Fri Dec 10, 2004 3:30 pm

I am using the WRT54g, Frimware: Alchemy-6.0-RC1.w42 V2.04.4.8sv. I get segmentation faults in most situations: ./kaid -o kaid.log will produce an immediate segmentation fault, ./kaid won't.
But after connecting the XBMC UI I get the next segmentation fault:

Quote:

/tmp # ./kaid
KAI: Reading settings from kaid.conf
CONFIG: Downloading settings from http://www.teamxlink.co.uk/connector/clientget
config.php...
CONFIG: 4 orbital(s) available...
KAI: Kai for KaiStation now starting...
KAI: Listening for UI's on :34522
KAI: Added 2 device(s) to engine cache.
PKTSNIFF: Setting up packet sniffer...
PKTSNIFF: Applying pcap filter 'ether src XX:XX or ether src XX:XX
PKTSNIFF: Everything set with packet sniffer...
UI: Received: KAI_CLIENT_DISCOVER; (20 bytes)
UI: Received: KAI_CLIENT_ATTACH; (18 bytes)
UI: Sending msg 'KAI_CLIENT_ATTACH;' to controller UI.
UI: Received: KAI_CLIENT_GETSTATE; (20 bytes)
UI: Sending msg 'KAI_CLIENT_NOT_LOGGED_IN;username;pwd;1;' to controller UI.
UI: Received: KAI_CLIENT_LOGIN;username;pwd; (34 bytes)
UI: Sending msg 'KAI_CLIENT_STATUS;Querying orbital mesh...;' to controller UI.
ORBDGRAM: Sent Orb Probe to 212.26.219.228:34525
ORBDGRAM: Sent Orb Probe to 64.81.178.4:34525
ORBDGRAM: Sent Orb Probe to 81.27.99.53:34525
ORBDGRAM: Sent Orb Probe to 64.27.6.84:34525
ORBDGRAM: Elected orb is 212.26.219.228
ORBSTREAM: Sending authentication to orbital...
ORBDGRAM: Now waiting for Orb datagrams.
Segmentation fault

username and pwd are correct.

Any ideas?

P.S.: The PC kai GUI is not able to connect to the kaid engine on the WRT54G. kaid reports

Quote:

..
UI: Received: KAI_CLIENT_DISCOVER; (20 bytes)
UI: Received: KAI_CLIENT_DISCOVER; (20 bytes)
UI: Received: KAI_CLIENT_DISCOVER; (20 bytes)
..

endlessly, but the PC GUI can't connect.

Posted: Fri Dec 10, 2004 4:13 pm

you may try the script I posted above.

Kai Regular Joined: 21 May 2004 Posts: 85 Location: Canada

As for sveasoft and integrating kaid into it, only the previous version of source is released (5.3 current source?) even thought it's gpl'd and someone maybe able to patch that to include kaid.

To get it into the main distribution, that would have to be submitted to sveasoft and take time.

Posted: Fri Dec 10, 2004 5:16 pm

bernienoel wrote:

you may try the script I posted above.

I don't see the difenrence in using your script and installing kaid manually? What's the point?

P.S.: I flashed KaiStation now, and it is working... Missing some features from the Alchemy 6 ROM, the static IP setup was very nice... Hmm.. Can live without it, if I have to...

Posted: Fri Dec 10, 2004 6:12 pm

kai is running on my alchemy setup, with all the new features (wds, static dhcp ip, qos...)

so i don't know why you're using the kaistation if you like alchemy's features Smile

the script allows to close the telnet window without closing the kaid process
and allows the kaid process to start after a reboot of the wrt