Notices


Reply
Thread Tools
Posts: 515 | Thanked: 259 times | Joined on Jan 2010
#81
Originally Posted by rambo View Post
Joikuspot was working fine with titans kernel but stopped working after installing mobilehotspot ? That would be interesting but I cannot see how the hotspot would mess joikuspot up in any permanent way. The frontend does nothing but set some configuration variables and run the backend script, the backend does insert some kernel modules on start and might not be able to remove all of them on stop (due to interesting interdependencies), said modules might interfere with Joiku (but in that case Joiku has serious issues to begin with) but reboot will always solve that.
That's why I'm asking the question. If I knew the answer I wouldn't be asking. Joikuspot was working fine, the next day I installed Mobile Hotspot and auto-disconnect and it stopped working. Both were immediately removed and Joikuspot re-installed and now I have not been able to get it working since. I don't know what could have screwed things up.

As for the kernel comment I have no idea what if anything the kernel has to do with it. Someone gave a suggestion to check it and I did. I'm open to all suggestions.
 
Posts: 515 | Thanked: 259 times | Joined on Jan 2010
#82
Originally Posted by rambo View Post
Edit: If you want to get rid of titans kernel run "apt-get install --reinstall kernel kernel-flasher && reboot" as root (this will reinstall and flash stock kernel).
I didn't know I had installed a titan kernel. I tried it and it didn't make any difference. I'll probably just reflash my phone and start from scratch.
 
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#83
Originally Posted by geohsia View Post
I didn't know I had installed a titan kernel. I tried it and it didn't make any difference. I'll probably just reflash my phone and start from scratch.
Ok, this explains a lot. Titans kernel got installed because mobilehotspot depends on kernel-feature-netfilter (which titans kernel provides). Reinstall stock kernel and you should be good to go (uninstalling just mobilehotspot will not uninstall titans kernel and I'm not 100% titans kernel automatically reflashes stock kernel after uninstall [which would be kinda smart to do]).

I kinda suppose (yes, supposion is the mother of all f*ckups) that people testing stuff from extras-devel seeing the package description (where it's stated that a custom kernel is required and might be installed automatically) know what it means.

edit: Do you mean reflashing stock kernel made no difference to Joikuspot ? Interesting but can't really help with that.
 
Posts: 323 | Thanked: 180 times | Joined on Oct 2009 @ Gent, Belgium
#84
Just wanted to tell how impressed I am. I was a more-or-less happy user from Joikuspot. There were issues with not connection linux boxes, extensive CPU usage (far more than seemed needed, even in the lo-fi client screen) but all got worse during my OC kernel trials.

I couldn't correctly get it to run anymore. So I decided to give mobilehotspot a chance and I must say : amazing. very little config (just enough for me), using the latest Titan kernel (power25) and it just works.

Very low overhead, no compatibility issues so far (eg. DHCP server not working), straight connection from my linux box ... Only thing I might like is a sort of 'connected clients' screen, to monitor a bit what's happening. low-fi is ok, CPU cycles sometimes quite scarce

Anyway, one word : super !! I don't think I'll go back to try to get Joikuspot working again unless I REALLY have to ... I just hope whenever PR1.2 comes out, Titan will update his kernel ASAP. I'm getting addicted to these enhanced community kernels
 
Posts: 61 | Thanked: 21 times | Joined on Jan 2010
#85
AFAIK Titan's Kernel is already based on PR1.2 source tree so it's PR1.2 kernel with enhancements.

EDIT: My only concern is that WEP seems to always be off even if I activate it via the frontend. If someone have a solution for that, I'll be glad to read it.

Last edited by BlackDiamond; 2010-04-16 at 13:12.
 

The Following User Says Thank You to BlackDiamond For This Useful Post:
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#86
Originally Posted by BlackDiamond View Post
AFAIK Titan's Kernel is already based on PR1.2 source tree so it's PR1.2 kernel with enhancements.

EDIT: My only concern is that WEP seems to always be off even if I activate it via the frontend. If someone have a solution for that, I'll be glad to read it.
Post screenshots of the config (remember to change the key to something to style of "example" first), then if you know how to read gconf data from the python shell read values

/apps/mobilehotspot/encryption_algo
/apps/mobilehotspot/encryption_key

and post them.

Then from terminal run hotspot_backend manually (via sudo) and post output.
 
Posts: 61 | Thanked: 21 times | Joined on Jan 2010
#87
Here is what I get:
Nokia-N900-02-8:~# gconftool-2 --get /apps/mobilehotspot/encryption_algo
WEP
Nokia-N900-02-8:~# gconftool-2 --get /apps/mobilehotspot/encryption_key
Test0
Nokia-N900-02-8:~# mobilehotspot_backend start
DEBUG: executing uname -r
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
DEBUG: executing lsmod
ERROR:dbus.proxies:Introspect error on :1.100:/com/nokia/icd2: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unsupported interface or method
icd2_state_listener got args:

(dbus.String(u''), dbus.UInt32(0L), dbus.String(u''), dbus.String(u'GPRS'), dbus.UInt32(83886080L), dbus.ByteArray('Orange World\x00'), dbus.String(u'GPRS did not find network for link_post_up'), dbus.UInt32(0L))
state['icd']:

{}
icd2_state_listener got args:

(dbus.String(u''), dbus.UInt32(0L), dbus.String(u''), dbus.String(u'GPRS'), dbus.UInt32(117440512L), dbus.ByteArray('Orange MMS\x00'), dbus.String(u''), dbus.UInt32(2L))
state['icd']:

{'old_connection_type': 'GPRS', 'old_connection_name': 'Orange MMS'}
DEBUG: executing ifconfig wlan0 down
DEBUG: executing iwconfig wlan0 mode ad-hoc
DEBUG: executing ifconfig wlan0 up
DEBUG: executing iwconfig wlan0 key restricted
DEBUG: executing iwconfig wlan0 essid "ManuN900"
DEBUG: executing ifconfig wlan0 10.238.164.1 netmask 255.255.255.0 up
DEBUG: executing /usr/sbin/dnsmasq -i wlan0 -a 10.238.164.1 -I lo -z -x /var/run/dnsmasq.wlan0.pid --dhcp-range=10.238.164.10,10.238.164.100,6h --dhcp-option=3,10.238.164.1 --dhcp-option=6,10.238.164.1
DEBUG: executing iptables --flush
DEBUG: executing iptables --flush -t nat
DEBUG: executing iptables -P FORWARD ACCEPT
DEBUG: executing iptables -P INPUT ACCEPT
DEBUG: executing iptables -P OUTPUT ACCEPT
DEBUG: executing iptables --table nat --append POSTROUTING --out-interface gprs0 -j MASQUERADE
Nokia-N900-02-8:~#
The strange part is that 'iwconfig wlan0 key restricted' is executed (I verified it wasn't here for an open connection)
 
Posts: 75 | Thanked: 78 times | Joined on Jan 2010 @ Germany
#88
@rambo: this is a simple bug in helpers.hex_encode… there is
"for char in output_str:" when is should say "for char in input_str:"
 
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#89
Originally Posted by hcm View Post
@rambo: this is a simple bug in helpers.hex_encode… there is
"for char in output_str:" when is should say "for char in input_str:"
Figured as much as soon as I saw that 'iwconfig wlan0 key restricted' , but I'm sure I fixed that typo "somewhere", it seems I never committed that change...

I'll be rolling a new package later today, meanwhile get r168 of helpers.py and overwrite the old one (or just use vi to fix that line...)

Edit: package built by autobuilder has landed to the repo.

Last edited by rambo; 2010-04-16 at 20:07. Reason: update, package in repo
 

The Following 2 Users Say Thank You to rambo For This Useful Post:
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#90
Originally Posted by Netweaver View Post
Just wanted to tell how impressed I am. I was a more-or-less happy user from Joikuspot. There were issues with not connection linux boxes, extensive CPU usage (far more than seemed needed, even in the lo-fi client screen)
The "hudge cpu consumption" complaints of Joiku makes me think that they do screen updates even when background which would be a monumental mistake, of course doing NAT in userspace is an overhead but I have no idea of the magnitude (yet... we'll be using weks approach for that with mobilehotspot soonish)

Originally Posted by Netweaver View Post
Only thing I might like is a sort of 'connected clients' screen, to monitor a bit what's happening
I have been thinking about that too and maybe some sort of simple data counter. But since both of those you can check from the terminal (ifconfig and iwconfig are your friends) if you're really interested I think I won't be adding them anytime soon (feel free to submit patches though).

Another idea I have floated around in the back of my head would be to add a led-pattern that the hotspot backend would use when active (this is one reason why I wrote mceledpattern)
 
Reply


 
Forum Jump


All times are GMT. The time now is 01:59.