If existing modules are compiled without an option, can't replacement modules be created, with (and I know this is ugly), some .deb compatible postinst which switches the existing modules with ones compile with that in, as well as the stock masq .ko files which is lacks altogether but which it's possible to compile and install in normal dpkg ways? Or, I know somebody who refuses (for h/ware reasons) to reboot a server he's had running for 15 years or so, where he insmods various catchup .ko files which patch together all the updates to the 2.2.*? kernel to keep it secure, you can essentially update most kernel internal symbols and capabilities, so adding nf_conntrack in a fresh module might be possible.

If it's been done it's been done. This might well work for my personal purposes, as it's not the stock kernel this is a nono for basically any packaging or providing for the community.

I want to use my PSP, ideally for RemotePlay when on 3G, and the PSP only works with Infrastructure. I think I'll need to backport the wlan80211 patches in .30 which brought global driver Infrastructure support. The later kernels brought in standardised stuff like this along with things like wpa_supplicant interfacing standards over the past months/years. It used to be a big steaming pile of poo with various drivers supporting a random mix of general wifi capabilities, making it quite a task to decide which h/ware you got. Now it all seems to be coming together Anyway the support is in a kernel, which I think I read somewhere, couldn't be made to work with the various driver blob firmware which will work with the phone, so back porting the support might be the only option. This is sadly beyond my current time/abilities. Even without NAT, running a squid proxy or similar should let the PSP at least browse.

I've used slirp about 15 years ago, I think it was old even then, used to be SLIP only (remember that), but had ppp support by then. It worked! However as that post mentions, it has drawbacks. Frankly, you'd be as well to just use a web proxy, ad-hoc already works, and I've done just that recently, I sshed in and then on from the phone via my n97 when I wanted to use its keyboard for a bit for my RSI.

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 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.

Thank you for this. Some of these threads to become hard to read through, especially on the n900 and with such small no.of posts per page.

Damion

PS if anyone wants to see Infrastructure support, or module overloading support, so this could potentially become a workable solution as a package for existing FW1.1 users, then I'll need a number of weeks of evening babysitting volunteered All my spare time got sucked up about 3.5 years ago when my 1st daughter was born.