View Single Post
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#96
Originally Posted by damion View Post
If existing modules are compiled without an option, can't replacement modules be created, with (and I know this is ugly)
...
so adding nf_conntrack in a fresh module might be possible.
I wonder if this is any less ugly than a custom kernel, we can flash the kernel OTA directly from deb anyway so from user-experience POV it's the same (except reboot vs no reboot).

Originally Posted by damion View Post
If I'm limited to ad-hoc I'd put up with sshing in and onwards, and/or using an http proxy, job done, let's move on.
I personally want a full NAT solution, ad-hoc or infrastructure does not matter much (in fact if the devices in the private net talk to each other [think Bonjour] ad-hoc is better since those packets do not need to go trough the n900). But of course infrastructure mode would be cool in case of devices that refuse to work ad-hoc.

Originally Posted by damion View Post
I want to keep investigating getting infrastructure working. I read up about this and found our wifi driver supports all the right things, we're just a couple of kernel revisions behind the support which adds this. We're in the new world of standardised wifi drivers.
Cool, hopefully someone with the right expertise has the time to look at backporting (or we can try to convince Nokia that this would be a good thing for them to do).

I was in fact also pondering whether to open a brainstorm to request for NAT capable kernel from Nokia (so that the kernel has support for the modules and an "kernel-modules-nat" package that can be installed via dependency to get the actual .kos).