*AIO* All-in-one box
-
My first thought was to use an internal (PCI) wireless card for setting up my own WiFi (with CP) and then use an USB-wireless-stick for connecting to the open WiFi…
Which components should I use for this to work?
Or is there any other way? -
With the correct one a single physical card can be virtualised to become many virtual wireless interfaces - https://docs.google.com/spreadsheet/ccc?key=0AojFUXcbH0ROdHgwYkFHbkRUdV9hVWljVWl5SXkxbFE&hl=en#gid=0
How well this will work for you is another matter, I have never tried wireless on pfSense other than HostAP or infrastructure client, never both at the same time, and my requirements for it have always been trivial and for my own (single user) purposes. Many people here I think see wireless on pfsense as something that technically works but is not something they rush to advertise as a feature. I have also never tried putting one captive portal behind another.
-
Tanks for your reply!
I think I will try this out.As I can see in the document the Marvell 802.11N or Atheros would be a good card to try…?
one captive portal behind another
The first CP is on the original WiFi and binds the ticket to the MAC-address, so that authentication is only made one time.
If I set up a repeater for this WiFi and login over the CP the result is that all new connected clients on the repeater have automatically access with this ticket because it is bound to the MAC-address of the repeater-hardware and not the client pc/phone/… -
I think you'd ultimately be much happier having separate wireless devices. One bridging to the other building and another one acting as an access point. You'll end up with much better and more reliable wireless connectivity… just my experience.
-
I have tried to connect to the WiFi in the other building with EDIMAX USB adapter (EW-7811Un as OPT1 in IS mode), but can't get a stable connection.
Sometimes the interface connects and 1 minute later is disconnected and showing "autoselect" in the status.So getting 2 PCI cards is better?
Then I would need to split (riser card) the PCI port, because I only have one.Do you have a favourite PCI card model?
There are so many… :o -
I thought I would just point out the possibility of virtualised wireless adaptors - I have never tried it myself and I probably can't be a great deal more help to be honest, the only ones I have used are the ones I was lucky enough to pull out of laptops and found were supported (Atheros AR9285 card).
Believe me I absolutely understand the desire for AIO, but with wireless on pfSense I think rjcrowder's advice is going to be the typical response. I don't like to discourage experimentation which can be rewarding for its own sake, but I based on what I have read of other people's experiences I would work on this with a solid Plan B in mind.
Edit - see this thread, most of it repeats the warnings but the last post is a call for testing the development release which may have improved the situation https://forum.pfsense.org/index.php?topic=89340.0
-
With the correct one a single physical card can be virtualised to become many virtual wireless interfaces
Even though this can be done, it is the worst case.
Remember that even the air we send signals through only has limited bandwidth. Using multiple SSIDs on the same wireless NIC (one incoming, one sending) means each packet has to travel twice on the same channel and polluting it.
Better receive on one channel and re-transmit on another. For b/g/n networks stick to channels 1, 6 and 11 only. Conduct a site-survey about channel usage first.
Try to get your gear on 5GHz if possible since this space is a) bigger and b) less crowded. -
Thanks for all your answers and tipps!!!
Unfortunately I haven't found any (supported) wireless PCI card on amazon or ebay.
I will try with 2 separate USB adapters (Ralink RT3072), which hopefully arrive tomorrow. -
Don't use internal or usb solution. Get an AP that attaches to your LAN with rj45 or just enjoy the pain…
-
Mh, I only have 1 port (RJ45)… so I will have to use at least 1 usb/internal solution.
-
Get a switch!
-
I get the impression this is an experiment for MrCount with a low or zero budget, which may develop in to something if it can be proved to work - correct me if I have jumped to conclusions. jahonix is entirely right, my idea is not a good one especially for what you want to achieve, but if you are trying to do this on the cheap it is an option.
-
Depending on current channel saturation it might not even be an option.
If there are already numerous hosts using this channel (not necessarily this AP), it might not even be worth considering. You would just worsen the situation - for all of them!
But maybe he's nearly the only one and nobody cares. -
I get the impression this is an experiment for MrCount with a low or zero budget
Yes, this is a "low-budget"-experiment.
Used hardware:
- HP Compaq t5720 Thin Client (1GHz CPU & 512 MB RAM) (~ $20)
- 4GB USB-stick for booting pfSense (~ $5)
- 2x wireless USB-adapter (~ $20 each)
So if this is going to work the costs for this silent "AIO-box" would be at around $65.
If not… bad luck 8)Get a switch!
I want to have a small box without any other external switches/APs/cables/…, so that the only thing I need is a power outlet and some screws.
If there are already numerous hosts using this channel
This solution would first be for a small group of users (~ 5-8).
Thanks for all your ideas and "warnings"!!
The USB-devices should arrive today and I will test and report back later. -
@MrCount:
The USB-devices should arrive today and I will test and report back later.
Not all wireless devices support HostAP, so fingers crossed for you they work. What do they show up as in pfSense? (ath0, for example). I didn't realise you were going to order them already so apologies if this advice comes too late.
I looked at the thin client, you have a PCI slot but no bracket on the case to mount a card in so I suppose you really had no choice but USB. Even if you could fudge something with a low profile card and removing the bracket it looks like the NIC+USB sockets would be touching or blocking the card.
If you are lucky enough to get this working with what you now have then I congratulate you, but tempting though it may seem to see this through I really would recommend you decide now not to put any more money behind this and go to Plan B.
-
You don't have to apologise, that is still in my planned budget. ;)
Right, there is not enough space inside the thin client. The USB+NIC block the card.
Only solution would be to try with a PCI riser card…So the USB adapters have arrived and I plugged them in..... and... surprise surprise.... they seem to work... ;D
They show up as run0 and run1 (firmware RT3071 ver. 0.33).run0 connects successfully to the WiFi with DHCP (192.168.178.1 is the WiFi AP)
run1 acts as AP and seems to work, only the DHCP does not give IPs to connecting clients (192.168.1.1 is the AP with new SSID), so I had to enter it manually on my connected laptop.The next thing is, that I had no connection to the internet through the AP, but I think this is cause I have no firewall rules set for the devices.
If anyone could give me some tipps.... 8) -
I bought a cheap AIO myself and was thinking of turning it into a wireless rig. It has two full mini-pciE slots. I was planning on wifi/cellular but with two separate radios your project is doable. Make sure to separate the two wireless networks the most you can. Put one on channel 36 and one on 165. For example. Maybe consider one network on 2.4 and one on 5ghz if your congestion is low on 2.4ghz.
Here is the AIO i got for 40 bucks.
http://www.ebay.com/itm/371262352319 -
@MrCount:
run0 connects successfully to the WiFi with DHCP (192.168.178.1 is the WiFi AP)
run1 acts as AP and seems to work, only the DHCP does not give IPs to connecting clients (192.168.1.1 is the AP with new SSID), so I had to enter it manually on my connected laptop.The next thing is, that I had no connection to the internet through the AP, but I think this is cause I have no firewall rules set for the devices.
If anyone could give me some tipps…. 8)Am at work, must be brief, how are your interfaces (WAN, LAN, OPTx) assigned? Also - https://forum.pfsense.org/index.php?topic=89045.0
-
If you think its a firewall rule issue you can turn of the firewall and use upstream firewall until you get it configured correctly.. Under System:Advanced:Firewall/NAT
Obviously this is less than safe but it works.
-
MrCount, can you post a link to EXACTLY what you purchased and also tell me how well its functioning.
I'm pretty down on USB wireless with pfsense but if it works well for you and is stable then I'd probably grab one for my own use. If the cost isn't too much.
