There is no difference in ascii or hex keys (other than the way you input them), the hotspot UI always takes "ascii" key (as in: you input the key bytes as is and hex-encoding is done by the backend script when it passes they key to iwconfig), it will also automatically 0-pad/limit the key to correct size.
I didn't talked about the N900 app, I was talking about the drivers of some other machines. some of them only accept WEP keys only in hex form, others only as ASCII even if all should be able to use both. I also have a device that allows me to use WEP keys with one single ASCII character! And no it is not filled with some dummy dater afterwards.
It's just a bad coded driver... that's why I don't like WEP encryption, but it is better than nothing.
what ever that shouldn't be your problem... or maybe it could be.
Would it be hard to implement a counter to show the user how many characters are left for a specific WEP encryption? I mean there are WEP64, WEP128 and even a WEP256. All of them are available as hex and ASCII. So it would be cool if there would be a pop up that tells you "you reach the right length for an ASCII-WEP-64 key" or something like that.
at least a message that informs you that you got a valid length for a WEP key.
Try running "sudo /usr/sbin/mobilehotspot_backend start" manually in terminal and post the output, it will show for example the exact commands used to configure kernel etc.
maybe it is the time... but how do i copy in the x terminal?! ctrl+c doesn't work and i can't use a remote ssh connection.
what ever that shouldn't be your problem... or maybe it could be.
Would it be hard to implement a counter to show the user how many characters are left for a specific WEP encryption? I mean there are WEP64, WEP128 and even a WEP256.
It's not hard, just not done yet, iwconfig supports only WEP64 and WEP128.
Thanks rambo and all who contributed! This is exactly what I was hoping for when I was looking into joikuspot; something that simply tied together netfilter, kernel nat, wireless tools, etc.
hmm ok i slowly got pissed because the update for kernel-flasher-maemo 2.6.28-maemo23 was shown but i couldn't install it. the previous version and mobilhotspot was blocking some files.
so i had to deinstall mobilhotspot first and then the kernel-flasher app... then I was able to install the new version of the kernel-flasher and after that the mobilhotspot.... and now everything is working again :-)
hmm ok i slowly got pissed because the update for kernel-flasher-maemo 2.6.28-maemo23 was shown but i couldn't install it. the previous version and mobilhotspot was blocking some files.
so i had to deinstall mobilhotspot first and then the kernel-flasher app... then I was able to install the new version of the kernel-flasher and after that the mobilhotspot.... and now everything is working again :-)
do i have to do that everytime from now on?
Probably not, kernel-maemo got renamed to kernel-power and that probably caused interesting depedency issues. hotspot itself does no depend on specific version of anything.
hey. I have a slight issue regarding this app. dont worry, ive searched two of the threads and found no cure..
a few days ago, when i installed mobilehotspot, it worked perfectly but noticed my cpu freq is capped at 600mhz (i was using lehto's 900mhz kernel)..
two days later, i decided to flash my device back to 900mhz and ever since, my mobilehotspot stopped working: it gives me a "hotspot failed to start" error message.
tried reinstalling, rebooting, the whole nine yards... still no difference.
