Hi Norm,
I would say, get rid of the bridge first. Most problem usually comes
with bridge + hostap + wpa. This normally exists with new wireless drivers.
Yes, you can use 2.6.34 from debian experimental, and that should no
harm but only disk space.
Regards,
Punky
On 7/9/2010 4:49 PM, Norman Henderson wrote:
Thanks Punky, I'm not 100% sure what you mean - my system IS doing NAT
for its various wireless clients, the actual Internet connection via a
3G USB device. That's the whole purpose of the project.
Are you saying that bridging wlan0 with (wired) eth0 in order to serve
both worlds may be a problem? Or are you saying that the wireless
drivers simply aren't reliable enough to use as an AP?
In the latter case, do you think it would be a good idea to upgrade to
kernel 2.6.34 from debian/experimental? Do you know if there other
things in Voyage that will break with 2.6.34?
And/or should I try the latest drivers from wireless.kernel.org?
Appreciate your help!
Norm
On Fri, Jul 9, 2010 at 9:27 AM, Kim-man 'Punky' TSE
<[email protected]> wrote:
Hi Norm,
I myself would suggest to NAT'd wireless client instead of bridged access
point.
I see ath9k is not at production quality at 2.6.30.
Regards,
Punky
On 7/7/2010 10:23 PM, Norman Henderson wrote:
--
Regards,
Punky
Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
- Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
- Network Engineering, Development Platform and Consultation
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
