From: lee on 1 Jul 2010 14:00 On Mon, Jun 28, 2010 at 03:26:25PM -0400, H.S. wrote: > First you need to make sure that your wireless card has the ability to > act as an access point. Next, you need to find which Linux driver > supports that card (madwifi or hostapd are my best bet). Then the final > step is just configure that card using the relevant driver. It's a Dlink card; I used it for a while to connect my computer to a router, but I switched to a wired connection because wireless sucks. > As an example, I have DLink DWL-G520 card working as an AP in my linux > router machine (running Debian). I am using hostapd as the driver. Cool --- sounds easy enough then. I'm just not sure yet if it's actually worthwhile and wanted see if there's much work involved. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100701175359.GJ8185(a)yun.yagibdah.de
From: H.S. on 1 Jul 2010 16:00 On 01/07/10 01:53 PM, lee wrote: > On Mon, Jun 28, 2010 at 03:26:25PM -0400, H.S. wrote: > >> First you need to make sure that your wireless card has the ability to >> act as an access point. Next, you need to find which Linux driver >> supports that card (madwifi or hostapd are my best bet). Then the final >> step is just configure that card using the relevant driver. > > It's a Dlink card; I used it for a while to connect my computer to a Which one? Can it be used as an AP? > router, but I switched to a wired connection because wireless sucks. I have a Windows 7 machine running only on wireless. The worst case is that I have to restart hostapd on my wireless AP machine. For the most part it appears to be working fine, though I am not getting my wireless connection at the max rates speed of 54 mbps (usually get around 1mbps). But wired lan is more stable any time compared to a wireless lan. > >> As an example, I have DLink DWL-G520 card working as an AP in my linux >> router machine (running Debian). I am using hostapd as the driver. > > Cool --- sounds easy enough then. I'm just not sure yet if it's > actually worthwhile and wanted see if there's much work involved. > > Install Hostapd and configure its file in /etc/ for wireless configuration. Further, I have the following in my /etc/network/interfaces file for the wireless card: auto wlan0 iface wlan0 inet static address 192.168.5.1 netmask 255.255.255.0 network 192.168.5.0 broadcast 192.168.5.255 And some of the most important options from my hostapd.conf are: interface=wlan0 driver=nl80211 ctrl_interface=/var/run/hostapd ctrl_interface_group=0 ssid=HSWirelessAP hw_mode=g channel=6 Put the wireless card on its own subnet. My wired lan is 192.168.0.x and wireless lan on 192.168.5.x. Install dnsmasq (or any other dhcp server), makes it easy to give IP addresses to WLAN clients. Allow forwarding for proper flow of network traffic, and allow traffic between different subnets if you have a firewall running (I do this with my iptables script, but other tools are equally good, shorewall?) Just post here if you are stuck on any of the above steps. -- Please reply to this list only. I read this list on its corresponding newsgroup on gmane.org. Replies sent to my email address are just filtered to a folder in my mailbox and get periodically deleted without ever having been read. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/i0irgc$qes$1(a)dough.gmane.org
From: Rob Owens on 1 Jul 2010 22:10 On Thu, Jul 01, 2010 at 07:50:53PM +0200, lee wrote: > On Tue, Jun 29, 2010 at 09:35:38AM +0200, Klistvud wrote: > > Dne, 28. 06. 2010 20:53:58 je Mark Allums napisal(a): > > > > > >The short answer is most "92-function-in-one" home WiFi routers > > >will act as an access point, > > > > I think that configuring your router as an access point is your best > > bet too: you'll hardly get the same signal range and stability from > > your add-in card -- even if it has an external antenna. > > Hm, I was hoping I might see better results than from the router. Even > when the computer connecting wirelessly is only about 4--5 meters > away, the connection comes and goes. Changing the channel in the > router manually sometimes helps --- I figure that the network card > they put into that Mac is of extremely poor quality. Due to the > retarded design they come with, it's even impossible to put in the > card I have instead ... Macs suck, they didn't even provide a half-way > useable keyboard, and a mouse with only one button is completely > useless ... > > Anyway, the other thing is that the router I have doesn't allow me to > set up a transparent proxy because it's not possible to reroute > traffic from computers on the LAN to another computer on the LAN. > I set up a Debian-based firewall/router recently. It doesn't have a wireless card in it, but if you need help with the firewall rules I might be able to help. I used fwbuilder to create it. I had lots of trouble with it when I used one of the built-in templates to create my firewall. (Maybe a bug, maybe my mistakes). When I created a firewall from scratch, it worked great. I used some of the templates as examples, but I did not build my firewall from a template. -Rob -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100702020309.GB8189(a)aurora.owens.net
First
|
Prev
|
Pages: 1 2 Prev: Need dependency bug workaround for pulseaudio. Next: Compiling source code with my own flags |