To Cable, or Not to Cable
-
@travisdh1 said in To Cable, or Not to Cable:
@scottalanmiller I'm curious, which AP were you thinking of in this video? By the nature of how radio and wifi work, I don't expect any kind of performance after around 15-20 active clients per radio (most AP have a minimum of 2 radios). Yes, keyword is active. You can have thousands of clients per AP radio if most of them aren't doing anything.
None in particular. APs are dirt cheap, so you can always add more. I only mentioned around that number per machine. You can have roughly one AP for every user for the cost of Ethernet drops, anyway!
-
@scottalanmiller said in To Cable, or Not to Cable:
@travisdh1 said in To Cable, or Not to Cable:
@scottalanmiller I'm curious, which AP were you thinking of in this video? By the nature of how radio and wifi work, I don't expect any kind of performance after around 15-20 active clients per radio (most AP have a minimum of 2 radios). Yes, keyword is active. You can have thousands of clients per AP radio if most of them aren't doing anything.
None in particular. APs are dirt cheap, so you can always add more. I only mentioned around that number per machine. You can have roughly one AP for every user for the cost of Ethernet drops, anyway!
Yep. Or if you're building didn't get structured wiring put in when it was built, it's much cheaper to run a cable to each AP than it is 2 to 4 cables per room! Which is exactly what my plan is for next year just before the Sophos license runs out, and cheaper for more radios (much less APs) than another year of a license.
-
@travisdh1 said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@travisdh1 said in To Cable, or Not to Cable:
@scottalanmiller I'm curious, which AP were you thinking of in this video? By the nature of how radio and wifi work, I don't expect any kind of performance after around 15-20 active clients per radio (most AP have a minimum of 2 radios). Yes, keyword is active. You can have thousands of clients per AP radio if most of them aren't doing anything.
None in particular. APs are dirt cheap, so you can always add more. I only mentioned around that number per machine. You can have roughly one AP for every user for the cost of Ethernet drops, anyway!
Yep. Or if you're building didn't get structured wiring put in when it was built, it's much cheaper to run a cable to each AP than it is 2 to 4 cables per room! Which is exactly what my plan is for next year just before the Sophos license runs out, and cheaper for more radios (much less APs) than another year of a license.
That's one of the many places where the original article just didn't make sense. Their assumed "wired is free, wireless is expensive" pricing just doesn't hold up. That can be true, if one is already paid for and one isn't, but that's about equally likely to be either one.
-
And over the years I've dealt with a lot of companies that had cabling problems and needed cables ripped out of the walls and fixed at great expense. That can get expensive really quickly.
-
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
-
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Yeah, sorry I missed that
-
@dbeato said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Yeah, sorry I missed that
LOL, there are lots of infrastructure things I'd not do on wifi. But the original article was pretty much written from an "all IT is the end user" perspective as if there was no tech involved anyway.
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
There's some new wireless about that I wouldn't be afraid to use as interconnects with servers, but it's not wifi. mm wave beamforming and 40Gb/s if I remember right.
-
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
-
@eddiejennings said in To Cable, or Not to Cable:
|can|———string———|can|
I win security!
*snip, hides scissors*
-
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
SAN is even worse.
-
@dafyre said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
|can|———string———|can|
I win security!
*snip, hides scissors*
Curses! Foiled by the script kiddie who googled
how to compromise a yarn-based connection.
</silliness>
-
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
-
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
-
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
-
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I think so.
-
@eddiejennings said in To Cable, or Not to Cable:
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
Actually, that's exactly what's happening and what Dash meant. A "real" DB connection is via a DB protocol, never via a mapped drive.
-
@scottalanmiller said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dashrender said in To Cable, or Not to Cable:
@eddiejennings said in To Cable, or Not to Cable:
@dafyre said in To Cable, or Not to Cable:
@scottalanmiller said in To Cable, or Not to Cable:
@dbeato said in To Cable, or Not to Cable:
The only thing I would not run over wifi is VoIP phones, not because of security but stability on the network.
I'd be hesitant to do SAN or database connections over Wifi, too
Can't speak to SAN over WiFi, but databases over Wifi will suck big time -- even if your wifi is reliable.
We have an accountant that comes in every payday to do tasks in Sage. It was decreed she will work in X room on a laptop. I made sure I had a cable that would reach the nearest drop. Just imagine talking to the PervasiveSQL Sage database over wifi.
Ug, does the DB actually get transferred to the endpoint, like QB?
I've never dealt with Quickbooks, but to my knowledge, Sage talks to the DB that lives on a mapped drive, so I don't think any DB files are transferred to the individual workstations.
Actually, that's exactly what's happening and what Dash meant. A "real" DB connection is via a DB protocol, never via a mapped drive.
Exactly.
-
Or to put it into really tech terms, it's a shared database file, a system lacking a DBMS.
