Notices


Reply
Thread Tools
aboaboit's Avatar
Posts: 129 | Thanked: 60 times | Joined on Jul 2009 @ Castello d'Argile (BO)
#61
Originally Posted by rambo View Post
edit: also INVALID, not WONTFIX, major difference...
Yes, I assumed iwconfig's error was fatal, my bad. However, it still doesn't work. Anyone else wants to take a pass at it?
 
Posts: 36 | Thanked: 20 times | Joined on Nov 2009 @ Austin, TX
#62
Originally Posted by aboaboit View Post
Yes, I assumed iwconfig's error was fatal, my bad. However, it still doesn't work. Anyone else wants to take a pass at it?
This isn't entirely unexpected: according to this the wl12xx driver series is not known to work in AP mode. Seems like you may have determined that it doesn't work. I will try to take a stab at setting it up this weekend (along with trying to finish compiling mupen64plus)
 
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#63
Niels pointed out this mockup http://www.facebook.com/photo.php?pi...d=253209882786

I wonder how they intent to handle NAT (supposing they do not wish to flash the kernel)
 
speculatrix's Avatar
Posts: 880 | Thanked: 264 times | Joined on Feb 2007 @ Cambridge, UK
#64
Originally Posted by rambo View Post
Niels pointed out this mockup http://www.facebook.com/photo.php?pi...d=253209882786

I wonder how they intent to handle NAT (supposing they do not wish to flash the kernel)
simply compile up a bunch of kernel modules which can be loaded when the program starts - you don't even have to have them in the /lib/modules/n.nn.... directory, just insmod rather than modprobe
__________________
Fujitsu U820, HTC Vision/G2/DesireZ, Nokia N800 770 E71, Zaurus 6000, Palm T3, Zaurus C3100 - stolen
 
Posts: 355 | Thanked: 566 times | Joined on Nov 2009 @ Redstone Canyon, Colorado
#65
Originally Posted by speculatrix View Post
simply compile up a bunch of kernel modules which can be loaded when the program starts - you don't even have to have them in the /lib/modules/n.nn.... directory, just insmod rather than modprobe
The NAT modules can't be used this way with the existing kernel (at least as shipped with PR1, I haven't confirmed with PR1.1).
 
qole's Avatar
Moderator | Posts: 7,109 | Thanked: 8,820 times | Joined on Oct 2007 @ Vancouver, BC, Canada
#66
Originally Posted by speculatrix View Post
simply compile up a bunch of kernel modules which can be loaded when the program starts - you don't even have to have them in the /lib/modules/n.nn.... directory, just insmod rather than modprobe
According to this thread, no. That's not going to work.

Originally Posted by micalil View Post
Hi all.
After two days of pajama hacking I'm now sure that stock 2009.42-11 kernel cannot support NAT modules in a proper way, because the netfilter core is compiled in without CONFIG_NF_CONNTRACK or CONFIG_NF_CONNTRACK_MODULE (see line 214 of net/netfilter/core.c).

So, no matter how hard we try to get a "debian-polite" way to add needed modules to this kernel, they will simply not work.

I'm posting this to see how other people involved in tethering projects would think about what we are in front of, specifically:

* Build a new, more modulable, kernel without getting too far from the rx51_defconfig and go with it.
* Go completely userland via proxies of any sort, even heavily tweaked for low resource usage.
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
 
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#67
Originally Posted by jebba View Post
I haven't confirmed with PR1.1).
Got latest "apt-get source kernel" few days ago "make rx51_defconfig" yields config that does not have conntrack symbols enabled.

So no NAT modules for PR1.1 stock kernel, when I have more time I'll make a script that will build a hotspot version of the latest kernel in repos (basically "apt-get source", patch a bunch of things, rename directories and packages and run dpkg-buildpackage)

this post outlines userland approach that might be worth considering (OTOH it's possible to flash the kernel from a .deb. I just consider it more than a bit sleazy to do that without showing some large disclaimers [other than the nokia default one] firsty).
 

The Following User Says Thank You to rambo For This Useful Post:
Posts: 2,014 | Thanked: 1,581 times | Joined on Sep 2009
#68
Assuming you have seen this

http://www.allaboutmaemo.com/news/it...a_WiFi_hot.php

Looks like if we hold out a little while there will be a nice little graphical interface that does this for us.
__________________
Class .. : Power Poster, Potential Coder
Humor .. : [*********] Alignment: Chaotic Evil
Patience : [***-------] Weapon(s): +2 Logic Mace
Agro ... : |*****-----] Relic(s) : G1, N900

 
R-R's Avatar
Posts: 739 | Thanked: 242 times | Joined on Sep 2007 @ Montreal
#69
 

The Following User Says Thank You to R-R For This Useful Post:
Posts: 355 | Thanked: 566 times | Joined on Nov 2009 @ Redstone Canyon, Colorado
#70
Have you worked around this yet? I haven't poked at a PR1.1 kernel due to this. I haven't investigated it deeper yet though:

"Kernel in PR1.1 build-depends on fiasco-gen which is nowhere to be found"
https://bugs.maemo.org/show_bug.cgi?id=7972
 

The Following User Says Thank You to jebba For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 16:05.