Re: N900 as a Wifi Hotspot, part 2
 

That IS titans kernerls afaik.
Make sure it's updated, and reinstall mobile hotspot.
It should work imho.

I can't assist further, so if that doesn't work you will still need the OP (;

Re: N900 as a Wifi Hotspot, part 2
 

you apparently didn't reboot after the kernel installation.
if its active it should read /lib/modules/2.6.28.10-power37

Re: N900 as a Wifi Hotspot, part 2
 

Still i am getting the same.... error

Re: N900 as a Wifi Hotspot, part 2
 

Exact same output from terminal start ? Then you're not actually running the power kernel (or any other kernel that provides NAT), try reinstalling it (quickest way is from terminal as root: "apt-get install --reinstall kernel-power-flasher && reboot")

Re: N900 as a Wifi Hotspot, part 2
 

installed the custom kernal and im not seeing iptables or wireless tools in the package manager. repos arent showing any errors. tried installing iptables from http://maemo.org/packages/package_in...ables/1.4.6-5/ the package manager reports and incompatable version. what am i overlooking? thanks!

Re: N900 as a Wifi Hotspot, part 2
 

They are not in the user/* section and thus not shown as invidually installable packages in the HAM (Hildon Application Manager).

The hotspot itself should have failed to install if iptables and wireless tools could not have been installed, check with "dpkg -l 'iptables'" the available (and possibly installed) versions.

But are you getting errors when starting the hotspot or what is the higher level problem ?

Re: N900 as a Wifi Hotspot, part 2
 

problem is im fairly new with linux and am still learning :/

youre saying iptables and wireless-tools are not in the package manger and im to download them and dpkg in xterm, correct?

the iptables deb is http://repository.maemo.org/extras-d....6-5_armel.deb, but where is wireless-tools?

i downloaded the iptables deb with microb and saved to documents but navigating around directories in xterm im not able to locate the downloaded deb.shouldnt it be something like home/user/documents?

Re: N900 as a Wifi Hotspot, part 2
 

$ sudo /usr/sbin/mobilehotspot_backend start ; echo $?
DEBUG: executing uname -r
DEBUG-read_previous_state: setting state key 'gconf' to value: {'wlan_search_interval': 600}
DEBUG-read_previous_state: setting state key 'kernel' to value: {'loaded_modules': {'x_tables': False, 'nf_nat': True, 'nf_conntrack': True, 'ipt_MASQUERADE': True, 'nf_conntrack_ipv4': True, 'ip_tables': False, 'iptable_nat': True, 'nf_defrag_ipv4': True}}
DEBUG-read_previous_state: setting state key 'icd' to value: {'old_connection_type': 'GPRS', 'old_connection_name': 'bsnlmobiltv'}
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.85:/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('bsnlmobiltv\x00'), dbus.String(u''), dbus.UInt32(2L))
state['icd']:

{'old_connection_type': 'GPRS', 'old_connection_name': 'bsnlmobiltv'}
DEBUG: executing ifconfig wlan0 down
DEBUG: executing iwconfig wlan0 mode ad-hoc
DEBUG: executing ifconfig wlan0 up
DEBUG: executing iwconfig wlan0 key 3132333030 restricted
DEBUG: executing iwconfig wlan0 essid "MobileHotSpot"
DEBUG: executing ifconfig wlan0 10.97.195.1 netmask 255.255.255.0 up
DEBUG: executing /usr/sbin/dnsmasq -i wlan0 -a 10.97.195.1 -I lo -z -x /var/run/dnsmasq.wlan0.pid --dhcp-range=10.97.195.10,10.97.195.100,6h --dhcp-option=3,10.97.195.1 --dhcp-option=6,10.97.195.1
DEBUG: Command output:
dnsmasq: failed to bind listening socket for 10.97.195.1: Address already in use
Traceback (most recent call last):
File "/usr/sbin/mobilehotspot_backend", line 14, in <module>
sys.exit(backend.cli())
File "/opt/mobilehotspot/libs/backend.py", line 395, in cli
backend.start()
File "/opt/mobilehotspot/libs/backend.py", line 134, in start
self.start_run_dnsmasq()
File "/opt/mobilehotspot/libs/backend.py", line 258, in start_run_dnsmasq
helpers.exec_cmd(dnsmasq_command + dnsmasq_options)
File "/opt/mobilehotspot/libs/helpers.py", line 12, in exec_cmd
raise Exception("Command '" + cmd + "' returned with code " + str(return_code) + " (" + str(expect_code) + " expected)")
Exception: Command '/usr/sbin/dnsmasq -i wlan0 -a 10.97.195.1 -I lo -z -x /var/run/dnsmasq.wlan0.pid --dhcp-range=10.97.195.10,10.97.195.100,6h --dhcp-option=3,10.97.195.1 --dhcp-option=6,10.97.195.1' returned with code 512 (0 expected)
1

now getting the above error Rambo***

Re: N900 as a Wifi Hotspot, part 2
 

Ok, so no problems actually running the hotspot ?

Yes and no, the HAM by default shows you only the user/* categories since that's what the users are interested in, libraries and low-level system software are not shown as not to confuse the normal user.

It still knows about all the software in the repositories and can automatically install any dependencies.

To install stuff (from repositories) via terminal use apt-get:

Installing from plain debs is painfull for any piece of software with nontrivial dependencies and everything you need (unless you compiled it yourself but then you know what you are doing [i hope]) is available in some repo if it's available in packaged form at all (there are good reasons why 3rd party repos are frowned upon but certain members of this community do run their own repos for various defendable reasons).

Do note that apt-get caches a bunch of data that HAM does not, this "wastes" space on the 2GB partition and in general you should either stick with HAM or educate yourself on details of how the Debian package management tools work (so that you know which caches should be removed manually and which not).

/home/user/MyDocs/.documents probably (the "dotfiles" are not sown with ls by default and this special naming convention is used to allow the file manager et co to localize the names of these standard locations).

Re: N900 as a Wifi Hotspot, part 2
 

For some reason there is already something (probably another dnsmasq instance) bound to the interface in the ports that we try to use, try rebooting (or killing whatever if binding the ports [this requires some specialist Linux and networking knowledge, "does not fit in this margin"]) and then try to start via termial (don't start the frontend at all)