Quote:
Originally Posted by drmozes
I have a Slackware64 server on 24x7. I hadn't thought of making it into a WiFi access point but it actually sounds like a good idea, particularly since the old WRT54G I have only does the slower wireless speeds. I also have enough NICs on the server do it.
|
But you have other reasons, appart from needing a heating device, for keeping it on 24x7 not just for having a fast AP. Well maybe a laptop makes a poor heating device
Quote:
Do you have to use dnsmasq? I already run dhcpd and bind. If that is configurable, that'd be great.
|
No ... I'm actually going to leave that out and just let the other init scripts deal with dhcp and dns.
I'm already using rc.dnsmasq that came stock with the package, just with modified dnsmasq.conf to suit my needs, if anyone likes the could possibly use udchcp and some other dns forwarder.
Quote:
What wireless card are you using? Is it USB?
|
Yes that's the only type of wireless network device I can have connected to my seagate plug like devices. It's an rt28xx based usb dongle ... you probably already know this but there are people who may not: currently master mode has been moved out of most (if not all) the wirless drivers and moved into userspace hostapd that in turn uses nl80211 interface, common to all mac80211 complient drivers. As a result you can run an AP even on hardware that previously did not support putting the device directly into Master mode.
As for the bus it makes no difference where the wifi device is connected (disregarding performance) as long as there's a working mac80211 driver for it.
Quote:
I actually don't have any spare ARM devices since they're all configured ready to be used for their purpose when needed: otherwise a Sheevaplug perhaps booting from NAND or SD card would do the job.
|
The Sheevaplug would beat the crap out of most of the low end AP ... why not try. But if you have an x86 machine on all the time anyway why not use that ... it will do one more usefull thing.
Quote:
I actually just had a crazy idea to ditch Slackware ARM soft float and do a hard float port instead since I already have all of the systems in place to build one, and that would free up the armv5 machines. Crazy ideas!
To clarify why that's a crazy idea - quite simply it'd take months of work to get a working system into the -current state, which would mean I would probably be divorced within 2 months ;-) In addition, ARM is going 64-bit so if any major re-porting work was to be done (by me) it'd be to 64bit systems. But if I win the lottery big time and don't need to work any more, I'll have a hard float port out within a few months.
|
Let's hope you win the lottery then

Well If I win the lottery I'll hire you to do it ok ?
I know how it works ... got wife and kids too ... I'm having a tough time just by making my own custom AP