Wifi AC
-
@mcc85
Op... The fork that shall not be named is also based on FreeBSD, so has the same wireless functionality. I understand the sentiment, but most business or home setups use a mix of technology. I see no problem using a firewall that is focused on it's role and having a separate WiFi solution. For the immediate future, BSD is simply not the best choice for access points. I've used WRT routers in the past, but UniFi has great functionality for it's price point. -
Isn’t unity based on FreeBSD or some version of Linux? Do they not have the same roots? If it works on Linux, why doesn’t it work on BSD?
Maybe I’m at a loss when you bring up those points... but I’m not saying Unify isn’t a good way to go, I just fail to see why pfsense is ready to throw in the towel to it.
Perhaps you see that I am trying very hard to advocate for some “sense” in this world, whether it’s a small wrt router, or it’s a mega enterprise gateway... I really like using it and the fact that it’s free leaves me to believe that it’s worth making it work somehow without making a compromise that jumps ship.
Just my two cents.
-
The whole point is that I should be able to integrate as many services into one device as I see fit that don’t require virtualization, more equipment, other software packages, or another monetary investment.
I see a way to have the sense box run Apache or web server for other sites not just the config panel, since it has the software libraries for it and happens to be deadly in security... using that in combination with vpn tunnels and everything else, I see no reason why it couldn’t be a hell of a lot more than it already is.
This is just one example, and maybe the engineers and devs arent ready for that kind of commitment... but sense is very scalable and I like the product that it is enough to try and ask the questions that others haven’t.
-
UniFi is Linux based. I don't see it as throwing in the towel- more like concentrating on core strengths. Putting the AP on the firewall is a compromise anyway, most enterprise firewalls don't have built in wireless. Using the right tool for the right job is not jumping ship. There are enough alternatives for running an access point that very few people are concerned about the poor wireless support in PfSense. My guess is that the greatest push for AC would be coming from desktop FreeBSD users, and that's a fairly small group as well.
-
So you’re saying it’s not worth the trouble?
Having an integrated WAP would only be a compromise if you didn’t know how to secure it.
As it is, wireless is another beast, but sense does support non-ac... right?
Not to mention, those little zotac boxes come with this little adapter that has wireless but I’ve had to turn it off or disable it every time I’ve had to install sense onto them... simply because I did have another access point to use.
But a lot of access points suck. Would be nice to load them up with something that makes sense. Cisco equipment can have its firmware iOS changed too right?
I guess what I’m saying is that with enough talent, knowledge, and dedication, one could turn any networking device into something completely different if it has the capabilities. We’re not building things out of LEGO’s, these are highly capable networking switches and it’d be nice to apply the same software to them all, especially if they’re doing that already with the commercial grade equipment by Netgate.
Idk. I don’t see myself as very complacent... and rather than mitigate my curiosity, maybe someone could provide a better explanation, unless it’s already been stated... then it does indeed sound like throwing in the towel.
-
supported AC. It's gonna be around for a while longer...
We'll shortly have AX which will do a far better job in HF crowded places. So AC/AC wave2 won't last longer than other wireless standards before.
Does anyone see what's wrong with this picture?
pfSense is a router. You're looking for an AccessPoint.
I'm glad I don't have those all-in-one boxes anymore because I can update/replace the component needed and I have my APs where they belong (high up on the ceilings) and the router deep down in a closet. -
Hey maybe you install access points in every place you do installations. That’s great. I’m proud of your strong sensibility... But for places where you want to access the web console from say, a phone, or laptop without an Ethernet port, might make sense to have one since it’s actually hardcoded into the system... but maybe the access point is not pulling an address or conflicts with the router, so you spend a lot more time trying to configure it than you should. Maybe you’ve forgotten, they actually do support WiFi in the same system. Hmmm.
Just because you do something a certain way doesn’t mean that others have the same requirements. Just seems like people are making a lot of excuses not to do it or give it the attention it deserves. Which sounds a lot like throwing in the towel. Maybe the dd-wrt router I wound up using can do just as good of a job, but that’s besides the point. Let’s keep voicing our opinions about how you do your installs rather than answering the original question.
-
I’m proud of your strong sensibility... But for places where you want to access the web console from say, a phone, or laptop without an Ethernet port, ...
My New Year's resolution will not contain making you proud.
If I need to access the console of a device not properly configured I use this: https://www.get-console.com/shop/en/27-airconsoleWhich sounds a lot like throwing in the towel.
Nobody is throwing in anything, except for experience maybe. If you do some research on FreeBSD and 802.11 you'll find that this combination doesn't have a track record worth mentioning.
If you want an AiO device then get one. Fritz!Box-es are a common choice in my vicinity. It's fine when you don't want/need dedicated devices and it isn't threatening anyone if you think DD-WRT would be a better choice for you. -
@jahonix well I’m glad you were sensible enough to see my sarcasm... thanks for the link, but that solution is too expensive. Yeah it looks like a great piece of hardware, but paying that much for the feature set leaves a lot to be desired. Why it doesn’t seem to power itself over USB or PoE makes it even less desirable for the price point, especially when I could use a Cisco aironet or ruckus zoneflex which does the same thing for literally a fraction of the price of the base unit... maybe we have different priorities. I’m trying to commercially deploy these boxes to smaller businesses that don’t have a huge budget, not so much the mega conglomerates that have plenty of cash to burn. Perhaps you don’t see what I’m tryin to do here, but that’s ok. The thing about sense is that it’s literally a matter of installing software on a box and then plugging in an adapter, and bam. An enterprise grade router with no real expense. Adding on a WiFi point, even with the aironets or zoneflexes just make life more difficult... sure would be nice to flash them with some sense and make them more cohesive. That was the point.
-
-
@nogbadthebad said in Wifi AC:
The Airconsole is RS232 over Wi-Fi it’s not an access point.
I have one.Basically you're right. It's my tool to access a console etc. It's not an alternative to a decent AP.
PoE? Nope, it has a battery built-in!
And you only have one AirConsole? Well, ...
-
Sounds like the principle of RS232 is about as old as the year 1960.
I'd rather use SSH or telnet over an access point that uses PoE that way I don't have to use a separate adapter to charge the battery in my overpriced lightweight tool that, while I'm sure some may find useful, defeats the purpose of less expensive methods. If you have cash to burn, great. Some people, like me for instance, fail to see it's usefulness when I can literally use a wifi to usb adapter that does the same exact thing as well... only i'm not trying to do it that way. Why get one of these if I could buy a unify? Defeats the purpose of using the sense box.
I mean, if money isn't an object then why use pfsense at all? Sounds like a pretty strange contradiction...
and just saying, never said that it was an access point. i'm saying that an access point is a lot more useful than this overpriced gadget that you were swindled into buying.
-
Sounds like the principle of RS232 is about as old as the year 1960.
A serial console is sometimes needed, if you can't connect via IP. Many routers have a serial port, connected to a dial up modem, to use as a "back door" for management. I carry a USB - RS232 adapter in my computer bag for when I configure equipment. You need it if you work with routers, switches, etc., from Cisco and others.
-
You really don't understand what the device is actually used for, I'd suggest you look at the device specifications.
Tell me how you can use an access-point to configure a Cisco switch or router out the box.
One minute your talking about 802.11 AC that doesn't exist under FreeBSD, then talk about installing pfSense on the WRT1900AC.
-
I did. I know what RS232 is for. Probably been doing network management a lot longer than you.
I looked at how much the device costs, you would know that if you read what I said. You would also know that I'm making an argument about why the lack of AC support is a thing. N works. So does every other version of it.
I studied for my CCNA back in 2003, so I have a pretty good idea what RS232 is for. I'm saying that if you're using legacy COM ports then you're using dinosaurs. Most people use things like "ethernet" and "usb", which cisco routers and switches use a lot of these days, and although I am more than well aware of the fact that other ports use that protocol, using straight up COM ports means you're likely using something built prior to 2003... Using RS232 with a device that costs 150 dollars and doesn't use a cable to keep it charged sounds like an expensive waste of money. But hey, maybe I'm wrong and ignorant... the point of all this is because I want to know why no one cares to develop the capability, and you're sitting there wondering if I'm being a troll, when it's a matter of no one answering the question.
I don't want to use dd-wrt, or other access points, I want to merge the equipment. I don't want to use an external adapter, I want to be able to put a lock on the box and never need to open it. I want to be able to distribute it to people who don't have a huge budget, and I'd like it to be impenetrable to intrusion. So far, I haven't seen anyone make the comment that says it's a worthless investment of time and resources to develop, just a lot of excuses and redirects.
-
Just a word of advisement, if you're using these devices, then you're essentially opening up a can of worms when it comes to security. All it would take to crack your network is to plug in a device that captures your input, they're actually a lot cheaper than this magic device you're saying I don't understand... but understand pretty well. What an expensive vulnerability you've advocated for, at least with ethernet and wireless, there's mac address filtering that would prevent that level of mitigation.
-
I did. I know what RS232 is for. Probably been doing network management a lot longer than you.
Started in networking in1990 for a large American multi national where I looked after 60 Unix workstations and the associated networking.
First router installed Cisco AGS.
If you want Wi-Fi in a pfSense box your stuck at 802.11n if you want 802.11ac you need to look elsewhere.
-
Ok. So I was wrong, but it's still a vulnerability to use RS232, its very easy to fool, it still uses IRQ# for direct CPU access.
Look, I apologize for the overextension. I've been pretty frustrated and it just seems like everyone's just fine with the way things are. Like I gotta go buy unify to get it workin. Not what I want to do. I appreciate the information I really do, but maybe i'll have to write the drivers myself is what I'm seeing here. Not something I have the time to do...
-
I studied for my CCNA back in 2003, so I have a pretty good idea what RS232 is for. I'm saying that if you're using legacy COM ports then you're using dinosaurs.
Try configuring a Cisco router or switch out of the box. You need to use the serial console to do that, though some models now have a built in USB converter.
BTW, I first started working with RS-232 back in the early '70s.
Just a word of advisement, if you're using these devices, then you're essentially opening up a can of worms when it comes to security. All it would take to crack your network is to plug in a device that captures your input
In my work, a serial port is only used when network access is not available, that is when configuring equipment from scratch, though it could also be used if locked out of the network connection due to misconfiguration. It is not used for normal management, in the manner one would use SSH.
BTW, ever use Wireshark to look at network traffic? Unless encrypted protocols are used, it's all plain text. Several years ago, I showed my manager how I could plug into the network and read ID's and passwords (this was on a network that used hubs, not switches).
-
Serial is still kind of dead simple OOB/console access. Just because it's "old" doesn't mean it's bad in this case. You can never rely on a network stack being functional for configuration, period. That's how you end up with braindead things like having to reset the firmware completely to work around a simple network setting glitch. If you are worried about serial port access, then fix your physical security.
