The Art of Network Engineering

Ep 111 – Wireless Networks

February 01, 2023 The Art of Network Engineering Episode 111
Ep 111 – Wireless Networks
The Art of Network Engineering
More Info
The Art of Network Engineering
Ep 111 – Wireless Networks
Feb 01, 2023 Episode 111
The Art of Network Engineering

In this episode, we talk wireless network with Rowell Dionicio, from  @ClearToSend ! 

More from Rowell: 

Clear to Send: 
YouTube: Website: 

Find everything AONE right here:

Show Notes Transcript

In this episode, we talk wireless network with Rowell Dionicio, from  @ClearToSend ! 

More from Rowell: 

Clear to Send: 
YouTube: Website: 

Find everything AONE right here:

This is the Art of Network Engineering podcast.

In this podcast, we'll explore tools, technologies, and talented people. We aim to bring you information that will expand your skill sense and toolbox and share the stories of fellow network engineers. Welcome to the art of network engineering, where we try to be that intersection between the tech and the people. I just made that up, Andy. What do you think? Is that our new tagline? Don't tell AJ. He'll hate it.

Anyway, I am Tim Bertino at Tim Bertino and I'm very excited this week because we didn't record last week. So I haven't seen my buddy Andy in over a week and you'll have to check out our YouTube channel because he's got a whole Scruff Lumberjack thing going on and it's fantastic. Thank you, Tim. How are you, buddy?

Uh, I'm good, man. Um, it's always good to see you. I wish we lived closer. You know what I mean? Nebraska is just too far from. Yeah, it's great. Everything. Yeah. Yeah, I'm good, man. Uh, you know, the house is decorated for the holidays. Um, work is, work is great. Uh, very fortunate to be where I'm at doing what I'm doing. Um, I'm going to say it again. You just hit a year, right?

Yeah, yeah, I have hit a year. I made it a year. I'll tell you, the first six months were tough. And Mike told me that. We're all gonna have to be a little uncomfortable for a while, right? Because I had never done that type of job. What did I say? Like, fortune favors the bold. I mean, you gotta take some chances. And I feel like every job I've taken in tech has been a leap and uncomfortable and full of uncertainty.

But I trust the leadership and I trust the process. And yeah, after about six months, I started to kind of groove in. And now a year in, I have a couple things that I own that feel really good to be working on. And yeah, man, can't complain. How's Tim's world? Oh, you know. I mean, you look great. I love your new look. Thank you. This doesn't just happen overnight, Andy.

Takes a lot of work and perseverance. My wife hates it by the way. I can't wait till we get together again in real life. I'm going to rub your head. I might lick it. Things are good. It's getting to be the end of the year. It's a time where you want to be around your family and just kind of enjoy everything. So it's...

Starting to slow down for the end of the year, kids are all getting excited. It's Christmas every day. We got to find the hidden elf every day. I still don't understand that. That's the worst thing. Give parents more crap to do. I feel like it's harder for me to find than the kids, but they must have like a sixth sense for that kind of thing. I want to put out there in the universe for all you married guys, right?

So I'm the guy for 10 years that had been letting my wife do everything because she's so good at it and probably not helping as much as I should with things like Christmas or birthdays. She'll buy all the presents and she claims to like it and she does it all. And then I come in at the end and wrap some stuff and I'm a big hero. And I have reasons and excuses why. But this year I decided, you know what? So we actually set a date and we had a date where we went out like shopping. I mean, we...

which really was just us walking around Target and Coles like with shopping carts. It's the most unromantic date I've ever had. But she said this is the first Christmas since we've started a family that like she's not stressed out, she's not obsessing about, you know, did I get enough? Like, because I've been way more involved, so. That's awesome. Support the moms out there, husbands. I'm trying to lead by example here. I'm, you know, yeah. Well, you got a leg up on me, man. We have done...

Granted, we have done tons of laps walking around Um, but no, it's, it's been good. Like I said, it's a, it's a fun time of year and, and just trying to, to enjoy it. Has it snowed there yet? You're in like snow. It did today. Not, not a ton. Um, but I did get, I did get a snowblower this season, so it'll probably never snow again, which honestly is okay. Right. But.

Hey, that's the way it goes. I got one last year, man. I'm left to trade some snowblower stories. All right, who we got tonight, man? This poor person has been staring at us for five minutes, just talking the crap that we talk. You know, we've received feedback like, why do you guys just have the host sitting there talking while you guys banter? But then we have other people say, we like the banter. So you can't make anybody happy. You can't win. No, you can't win. All right, so who we got today? I am very excited to introduce Roel Dionizio.

Roel is the host of the Clear Descend podcast, all about Wi-Fi. Roel, how are you? I'm doing wonderful. Thanks for having me. You know, we're really glad to have you because we kind of sat back as a group and thought we're like, okay, we are, what, two and a half years into this as a group. We are over a hundred plus episodes. We have yet to do, you know, about network engineering.

Wi-Fi is a big part of network engineering. We've yet to do an episode on Wi-Fi. And I think a big reason of that is between the group of us, none of us are really SMEs on Wi-Fi. A few of us have experience. We have it in our networks, and we're responsible to an extent. But none of us are really hands-on in it every day. And I have listened to Clear Descend multiple times over the years. And

You actually did, it was about this time last year, you ran a Twitter space where you just kind of invited a bunch of people on and were talking WiFi, things that are coming up in the industry, and you were really open. I think I jumped on for a minute and asked a question. It was really cool. So I thought, hey, if we're gonna talk wireless, we gotta get Roel on here. So if you don't mind, Roel, can you kind of give us a background on yourself where you...

got the interest or the itch in technology in general and, and what, why wireless? Yeah, I've always had a thing about tech. Um, I started out like my, my first role was helped us. So I've came from the help desk, become a sys admin. I've done, uh, I was an IT manager for a short time, then went into network engineering. So I, I've, I've done all of it.

Maybe touch a little bit of everything. And I like technology in general. I like tinkering with things. I like putting things together, trying to troubleshoot. But the one thing, I don't know what it is about WiFi. I think I was working somewhere and no one knew how to do WiFi. But where I was working at, one of our clients, the MSP I was working at, no one knew what to do and it was such a critical thing to them.

So that's when I just started to learn and pick up Wi-Fi in general. I learned pretty quickly. I was doing it wrong. So I figured I'll be the one to help others on the team in regards to Wi-Fi and kind of take a lead there. So you turn the game all the way up on everything, right? I mean, that's what I do. I was surprised when somebody told me that's bad, right? It can be bad. Yeah.

It's not always bad. I think in our industry, a lot of Wi-Fi people will say, don't ever put it at max power. Um, but I mean, you're gonna put it on max power sometimes it happens, right? If you hopped onto my network and looked at our, um, you'll see some things on max power, but what it really comes down to are people able to work on that Wi-Fi network or they will do what they need to do. Then then it's done its job.

Yeah, I'm glad you brought that up about seeing a gap. We have a lot of listeners to this show that are either trying to break into technology, either they're younger in their career or they're making a shift. And I think that's a good piece of advice is to show some initiative that you're willing to pick up something that is either nobody else is really an expert in or it's an underappreciated

skill set. That's how you can get ahead. That's how you can show initiatives. So I find that really interesting. That's how you got your start in wireless. Yeah, it was just something I put myself out there. And like what you were saying earlier, Andy, about taking risks, you got to take those calculated risks. And it doesn't have to be Wi-Fi in general. If you see a technology or area that no one seems to be an SME in, maybe that's something you can take.

as an opportunity to become that person. I mean granted, you should probably like it, but I've seen some opportunities and I'm like, no, I'm not doing that. And we talked about this earlier, Tim, like voice is one of those things I won't do, or SharePoint. And so those are two specific technologies I've removed from my resume, just so nobody can talk to me about this.

Don't tell anybody. You're interviewing for a wireless engineer position and you end up becoming the exchange person. It doesn't mean it's not useful to know, right? I think one of the things that's helped me a lot is being in help desk and sysadmin rules because as a network engineer, when you're troubleshooting, it does help to know how

engineer is trying to get connected or try to access resources and makes it easier or faster for you to troubleshoot. Yeah, having that first hand first person experience with the end user is just invaluable. I mean I spent five years as you know as a cable guy. Similar to help desk, right? Like everybody's calling me every day with stuff not working and I'm out there like, all right, you know, what are the symptoms? What's going on? You know, what can we do? Like you really get good at

troubleshooting. So you were you were at a place that they had wireless and they needed help? Like was there one person doing it and they needed help? Like how did you know it's just it was just a look. I mean, the team I was on they all had to do wireless but no one really knew how it worked. So if I go back to how I did Wi Fi and maybe a lot of you guys will relate is you have this access point and it's

It's very easy to set up. Turn it on, plug it in, have an SSID. If you can connect to it, great. If you can't connect to it, I need to add another one somewhere, right? As I walk further. That's generally how people start off. But once you get into more complicated environments, then it becomes a lot more trickier that way. Small Office is relatively easy to deploy Wi-Fi for.

A lot of times people will think they need to do a design for a very small office and I'm like, one access point, five people, you're gonna be fine. Guarantee you'll be okay. But it's about knowing what to look for when you're doing WiFi. And so just like with network engineering, right? If I'm getting into networking, what do I need to know? So same thing with WiFi, it's just a different medium, right? Networking and switches, routers, we're dealing with.

cables, wires, right, and protocols. It's the same thing with Wi-Fi, it's just, there's no wires, there's radios, but there's also Wi-Fi protocols. So I had to shift my mindset from different protocols and different physical mediums to dealing with the Wi-Fi side. So I wanna tap into that because I think that that was one thing that even to this day has gotten me nervous about wireless is with

traditional, what I call traditional wired route switch. Everything's there, everything has those physical connections. And when you get into wireless, things get a little bit more nebulous. There's a lot of science and physics behind that. And my question for you is, is really becoming a wireless engineer, how much of the physics do you really need to understand to be able to build, maintain, and support wireless networks?

I think you'll get pretty far not knowing too much physics. If you just understand how light bulbs work, you could get ahead pretty far. If you've got a light bulb, you got one in the room, go on the other side of the wall. How much of that light actually goes through the wall or through a curtain? That's kind of the same thing with with Wi Fi. You lose the intensity of that light when you put something in front of it, right?

Lampshade that's very similar to using something like an antenna to shape the signal To a specific area. So if you understand that kind of physics where Wi-Fi is much better and much more reliable Closer to the user you'll you'll get pretty far, but there is physics involved That's when things get Said more complicated. I Like that light analogy. Yeah, I I agree Andy. I've actually never heard it

Described as that before as an analogy. That's interesting Same with your microphones. Your microphones are the same way My voice my mouth is pretty much right on top of this microphone but if I move to the side my voice gets a little bit weaker because The shape of that microphone is really just right here. That's the same thing with the antennas. I Love the light analogy because we can see light

You know, but with our voices and with wifi, it just seems magic. Like I can't see it, but it's there and my stuff is working. So here's my one silly talking about physics as a cable guy. Every, every time, and you'll probably know right away, Roel, but so I get a call and I'm like the 10th guy there. Every time these people's, every time their phone rings, the wifi goes out. Their phone. Oh.

using some old cordless phones then. you know, microwaves and old cordless phones but this is like some nerdy crap, right? that came in is like, this customer's crazy. customer-owned router, it links this,

Soon as the phone rings, all the lights, you know, like it just, it just went out. Like it just, it killed it. I was like, Oh, well you got to replace your router. Like, and they didn't believe me. And they called my boss the next day and like, he told me I need a new router. I'm like, listen, man, it's, and I think I even looked it up and it was like on the same frequency, you know, whatever. But yeah, but that's my one, you know, I worked in very small environments, one access point, you know, it's centrally located wherever I was the office or the house that was usually sufficient. Some of the bigger houses.

plug in the awful range extenders, which I don't think anybody should do. No. Yeah, they're all terrible. So the one question I have for you, because I say this real well, and I don't know if it's true, but I think it's true, is all wireless half duplex communication? Yes, Wi-Fi is half duplex. Which is why I hardwire everything I can. I wouldn't say all wireless, right? Wireless will encompass a lot of different technologies, but Wi-Fi is half duplex.

Duplex isn't as good as full duplex, right? It's not. And marketing does its magic on those boxes, right? You go to Best Buy, you see the latest, I don't know, spider looking router thing and it's like 9.6 gigabits per second. But what they don't tell you is it's an aggregate of the five gigahertz total max capability, the aggregate with the 2.4 and then that's...

you know, if you can get full duplex to it's half duplex. So, you know, cut that in half. And I guess it doesn't matter because I can pull like 180 megabits a second, you know, off my local, you know, I mean, it's fine, right? Like, but, but in, as a network engineer with wires, I know full duplex is better. I'm like, you know, wire everything. Full duplex is better. I'm a network engineer. And I will admit that my wifi is currently disabled. I'm hardwired for this one.

I'm hardwired as much. Tim's probably on Wi-Fi, aren't you Tim? I'm usually wired, but yeah, tonight's different. I'm sorry. It's because of Roel. I had to show off. Wait, do you have a wire sitting there and you're not using it on purpose? It's a long story. I don't want to talk about it. It's alright. The wired guy is using Wi-Fi and the Wi-Fi guy is using wired.

So you really took to wifi, I guess. Go ahead, Tim. Yeah, I do want to, I want to get into some more in depth like wireless design, but what I wanted to talk about real quickly, because I want to make sure we don't forget it for our audience, but Raul, in your experience working in the wireless space, what are some of the different career opportunities or job roles that are out there? Is it really just?

wireless engineer and you're in charge of everything from design, implementation and support or are there different types of roles for people focusing on wireless that are out there? Yeah, I think the most common is just a network engineer and you have Wi-Fi as part of your wheelhouse. Then you have the dedicated Wi-Fi engineer, which will probably encompass everything from doing the design, the configuration, the

Troubleshooting and also what we call validation service where you go on site and use specialized software and hardware to gather data of the Wi-Fi network. So that's probably the most common one. And then sometimes larger organizations will split those roles where you have someone who just does the design, someone who just does the configuration and troubleshooting. And then you have...

some people who just do the validation survey and that's a lot of walking around and using either a tablet or computer to tap where you are. So that was something that I wanted to spend a good deal of time on this podcast talking about. I think we hear so a lot of end users, customers, people walk into buildings and the wireless is just there, right? You can

you can tell who the IT people are when they walk into a retail space or something, because they're always looking straight up at the ceiling trying to find out what model of AP that the store's using. But usually when we see those things, they're already implemented, they're already done, they're already working. We hear this term that's called, in the design phase, that's called a site survey. Can you kind of talk about what a site survey is, what the importance is, and why we need to do them?

Yeah, I think the term site survey just gets thrown around all over the place. Sure. So I do have to ask questions on what exactly does somebody mean with a site survey? Like do you need a design? Do you need a I like calling it validation survey because if it's already been deployed and you just need what they call like a heat map, you know, heat map, that's a validation survey.

requirements that you're meeting or not meeting, you know, whatever those requirements are that that the end user defines. But yeah, site survey can also mean somebody going on site and let's say it's nothing's been deployed yet. So there's something called like an AP on a stick. So basically you take a tripod, there's an access point on it. And you take it take it to proposed locations to kind of make the design a lot more accurate than just

predictive design. Predictive design, we're just using a software to place access points on the floor plan. It's all simulation and it takes a lot of different parameters from our characteristics of different access point models and we try to be as accurate as possible, but I like to emphasize I do tell people that that is a predictive model. It's not going to be 100% accurate and that's why we do the validation survey afterwards to see

exactly what the coverage looks like. Are we meeting capacity? Do we have other settings that need to change? In your experience, is the predictive survey done more often than somebody actually going out on site and doing that pre-survey? No, I find that most people do not do predictive designs. It's one, you need pretty good

accurate software to do that and a lot of times an organization is just going to do this once so they're not going to invest in the application to do that so they'll guess or they'll let their salesperson guess how many access points they need. So I find that most people do the validation part where they say hey I think we have a coverage gap but I'm not sure because I can't see the Wi-Fi so I just need you they need someone specialized to go do that for them and

So we're all, I think I, I think I already know the answer to this, but are all spaces created equally? And I'm talking interior spaces. Are there, do we need to treat, um, walls and cubicles or open offices different than like, uh, large auditoriums or theaters or that kind of thing. Yeah, there, you know, some interior office carpeted space tend to have similar

characteristics, but a lot of times, yeah, they'll be very different because of the layout, the walls. A lot of times, I might guess that it's a drywall, but it happens to be drywall on top of a brick wall, those kinds of things. And so that changes the signal strength, you know, or the attenuation attenuates a signal much more stronger than there. So that's where we find those kinds of things in a validation survey.

and I'm able to use that information to tell whoever the end user is, like what they need to do to make it better. Either adding a new access point or just maybe moving some, chopping them down from the ceiling where it's hidden. Typically it's like hidden access points. And I don't like that for a lot of different reasons is because when you place an access point on the ceiling tile or like this is the ceiling tile right here, right?

all the desks and then they place the access point right on the top. The propagation pattern of that access point is typically like a down tilt omni-directional. When you place it right on top. It doesn't go like up into the... It is but yeah it's going up. There's nothing behind, there isn't much behind it right. So if you got the plate on the back there it doesn't really propagate as much behind it. Gotcha. So when people lay them on top of the ceiling tile it's great signal for the HVAC.

for the... Yeah, that's interesting. So you talked about signal propagation and I think we know that there's a bunch of different types of APs out there and a bunch of antenna types. So how do we know what type of AP to pick for a, and antenna for that matter for a specific area? And then how many to put in, right? Cause I'm thinking like a huge auditorium.

I would have no idea. Like, is that a predictive software thing? Are you guys walking around with sticks in an auditorium? Like, how do you figure? Like, it seems like black magic. Somebody said in the chat, like, Wi-Fi is black magic. Yeah, Wi-Fi is black magic. You know, how would you figure out? Hey, you know, I can say the same thing about BGP. I don't do it that often. Oh, yeah, yeah, yeah. It's black magic. It's like, it's the pipes for the internet, right? But how do you pick the AP and the antenna types and how many? Like, is it an art? Does it take a while to?

So a lot of that depends on the requirements. And so I always ask people, show me, tell me about this space, show it to me. You have a floor plan because there's a lot of the things that go into it like aesthetics, bounding capabilities, like can I place an access point there, can we run cabling to the access point? If that's not possible then alternative. But in the very, very beginning, we talk about, okay.

How many devices are going to be here? I always start with people, because most of the time, whoever I'm talking to doesn't even know what kind of devices. So we'll take higher ed, for example, because I'm a network engineer at a university. We have a lot of lecture halls, and a lot of times, there's no one I can talk to to say, hey, what are the requirements you need for Wi-Fi in this lecture hall? I may get lucky and talk to a professor, and they tell me how exactly they interact with the students and what they do over Wi-Fi.

But a lot of times I'll count the number of seats. I do that with office space too. I count the number of desks. So if I got an area with 30 people, I already know there's gonna be minimum 30 devices. Especially if this is a office or lecture hall, 30 devices are gonna be used, right? And then everyone carries about two or three devices so you can multiply that. But in the design software that we use, there is a lot of math involved with.

physics. So there is a capacity to Wi-Fi, which is all due to the physics. It's like a pie, right? Think of a 5 GHz radio as a pie. If there's one device, they're gonna have, you know, everything of that radio. Just like when you walk into the kitchen in the office, there's one pie there on the table. I can eat all that pie if I wanted to. But you know, if 10 people showed up, I got a

divvy up the pie 10 slices so I get a much smaller slice. So that's how Wi-Fi is in terms of capacity is like, okay, how many devices are going to be here? And also when a lot of people don't think about is what kind of applications are going to be used because if you got 30 people and they say, you know what, all 30 people are going to do Zoom, that's going to be a problem because with all the video that you're uploading and downloading, that's going to eat up the capacity.

And then if most people are just doing email, that's typically fine. And so in the application that we use, there's different applications. They can do capacity planning, and you can put in the number of devices, what kind of applications you think they're gonna use to determine if the number of access points you have is gonna meet those requirements, the capacity requirement. And that is a lot more involved, but so does that, does that take into account?

that then takes into account not just the capacity, but the coverage area as well. Cause I think that's- Yeah, I mean with wifi nowadays, coverage is a given. It's just 100% including the restrooms. That's what I wanted to highlight because when I was really first starting out, coverage was what you worried about. You wanted to make sure that everybody had a good experience and what I always thought of a good experience was we had to have coverage and that I think has changed into like Taylor,

was asking how do we plan for capacity? Because that's a big part of this now is, like you said, it's not just one device per person anymore. You need to plan for that. And that's how I was wondering, and I'm glad that you walked into that of that software. Design is super critical. Yeah. Design is gonna be most important because in the offices I've been in,

Almost everybody is wifi and now people aren't adding as many ethernet drops. So not everyone will be hardwired. And a lot of times I, not a lot, but there are a few times where I have recommended that certain people go ethernet. I've been in an environment where everyone was over wifi, but this environment, it was like almost like a cubicle farm, but they weren't like in a warehouse.

So there's a lot of desks, no one moved. These were all desktops with a WiFi adapter. But they were downloading high resolution photos, uploading high resolution photos, videos, all at the same time, all day. And WiFi just couldn't meet the capacity because everyone was so close to each other that even if I added more access points to try to meet that capacity, the physics of RF, because it propagates very...

far in an open space. It just we ran into capacity RF issues, physics issues with co channel interference, things like that. And so I even I in that scenario, I recommended that they hardwire their, their computers. And they told me that they want they they wanted me to make it work over Wi Fi. And I showed them the design. I'm like, Look, this doesn't mean

we're not going to meet your capacity requirements. Even if I picked 30, if I just said 30 of these devices will upload high res images and videos, it still doesn't meet the requirements. Well, if I just couldn't meet all the bandwidth requirements, right? Yeah, it was just an RF physics capacity issue there. And eventually I just stopped working with them because they didn't want to believe me. And when one of the engineers left, I spoke to him saying, hey, what'd you guys end up doing there? And they're like.

Oh, we ran ethernet cables. You're getting me excited with code channel interference. I really want to get into the nerdery. Can we get into the nerdery yet, Tim? Go for it. Let's go. So I remember from 2.4 gigahertz, you have those three channels you can use that don't interfere with each other, right? Is it one, six and 11? In the US, yeah. Oh, fancy.

So does that mean if you put one access point here and then you need another one, I don't know, X amount of feet away, this one should be on channel one, the next should be on six. Like do you stagger them like that so that they don't fight with each other? Yeah. And it's not... Wi-Fi is pretty nice as a technology. It doesn't really fight, it just backs off. So the way Wi-Fi works is because it's half duplex.

the RF on the medium before it even transmits. That's with APs and devices. And so it listens and goes, do I detect a signal? If I do, I'm just gonna wait. And there's- It wasn't detection. That was like the old switching we used to do, the CSMDA, whatever the hell it was. Remember? Yeah, but it's avoidance in Wi-Fi. Huh. Because on ethernet, you can detect signal and be able to recover. But in Wi-Fi, it is possible for

multiple devices to transmit at the same time and then that signal gets all jarbled up because it's in the same frequency. So with 5 GHz, is there co-channel interference? Let me back up. What's the difference between 2.4 and 5? Like what's the big... why is 5 so much better and faster? So 2.4 GHz is a lower frequency and it propagates farther. It doesn't attenuate as much through materials like...

drywall. But there are not as many channels that we could use in 2.4. And like you said, there's only three non overlapping channels. You can put APs on the same channel. What happens is actually, I'll table that in five gigahertz, there's a lot more channels, right? So because it's a higher frequency is like a physics thing. No, it's it's not that it's because the I'll just say the FCC.

allowed a certain amount of frequency that we could use in 5 GHz for Wi-Fi. And so with 2.4, with three non-overlapping channels and 5 GHz in the same amount of configuration like a 20 MHz wide channel, we get about 20, 24, 25 channels that we can use that are non-overlapping. So you have more capacity that way. Oh, in 5 GHz. Now there's channel bond, yeah, there's in 5 GHz. Now there's channel bonding and all that. And that gives you more higher throughput.

But think about co-channel like having a meeting in the office. How many of you have had two different meetings in the same room? It doesn't happen. No one, right? No one does that. Yeah, you would never understand what the heck's going on at that meeting. So having two meetings in the same meeting room is like having two APs on the same channel, operating on the same channel. Okay.

And if they can hear each other, if they're in close proximity, like in a meeting when two people talk at the same time, you have to wait. Only one person can talk in order to understand what that person is transmitting or saying. So you can receive it and comprehend it. The same way in Wi-Fi. We try to avoid or minimize code channel. It's not always negative, right?

If you've got an empty office and all the APs are on the same channel and a few people are there, it's not going to be a big deal. It becomes a challenge when there's a lot more devices on the network, a lot more APs operating on the same channel, they're all in the same close vicinity area, then they share the same capacity of that channel. And that's why co-channel can be bad. The five gigs is faster, there's less interference, there's more channels, but it doesn't go as far.

Yeah, it attenuates more. But in five gigahertz, you could do channel bonding. So you can take two channels, combine them into one channel. But then you minimize how many non overlapping channels that you have. What we call magic and a six gig here yet. It's here. I have I have about three P's I am testing with six gigahertz. I have three six gigahertz clients, but that's about it. So it's here. Are we using it?

No, not yet. So even though there's a whole- It's better than 5G hell, more bandwidth, more channels. There's a lot more frequency there. So a lot more channels. I don't even have those numbers memorized. That's how many channels we have. Okay, so- So we're in 5 GHz. In 5 GHz, we recommend 20 MHz wide channels, maybe even 40 MHz wide. With 6 GHz, they're saying that's gonna be, you'll start off at-

80 megahertz wide channels. That's how many channels are available. And then we may see... And the bandwidth will be much faster, right? Yeah, we should see more potential with Wi-Fi, like see those actual capability of Wi-Fi. Does it still have the attenuation issue that 5GIG does as opposed to 2.4? In my initial testing, I'm seeing that the signal is actually lower in 6 GHz. It's a higher frequency.

So the higher frequency you go, the, it gets attenuated more. Last nerd question I have, and then I'll give it back to you, Tim. So I have a relatively big house I'm trying to cover. I have one century-located guy in the kitchen, and he seems to do a pretty good job.

Security, I'm not asking you to design my network. I'm going somewhere with this. So I have some live troubleshooting. I have a security camera, wireless security camera on the other side of the house and it wasn't getting a good signal. It was choppy. So anyway, I just I ran an Ethernet out to there and you know ran an outlet and put an access point. Autonomous. I don't have any controls or anything. So that's working fine. But you know, the coverage in my yard is bad. So like I'm eventually gonna have to figure out a better solution.

Cause like we gotta pull out back. So now like, you know, you might want to get on your phone out there and like the wireless is crappy. So where I'm going with all this is I got into like mesh systems. I started looking into like the mesh stuff. But what I was reading and you know better than I would, do they all use, like are they backhauling? Yeah. They'll use a radio to backhaul. And that's not good, right? Like there's a, No, it's because it's still half duplex. So it's your, your

you're not getting much. I mean, you're pretty much just getting coverage is what you need, right? But hey, if you need to do it at home, it's no problem. I try to make sure all the APs have at least ethernet, but I know it's not always the case, right? So mesh is convenient for us when you need to get wifi in an area, but you don't have the infrastructure cabling to bring it there.

So you use Wi-Fi as your backhaul, which we call mesh, where an access point will connect to another access point and will also at the same time simultaneously serve clients, maybe on another radio. Sometimes we do see APs that mesh where the radio that's a backhaul will also serve clients as well. And that's also much worse because instead of being a dedicated backhaul mesh connection,

It has to do multiple things, right? So it has to go, all right, let me help you. Okay, now I need to go send your data back to the root AP. So I mean, you sacrifice throughput, bandwidth, but you get coverage. Right, which is why I haven't done it, because I'm obsessed with bandwidth for some reason. So I wouldn't go mesh. So like a person like me,

who needs multiple access points in their environment. I mean, do I need a controller? Do I need to buy into some system? Because right now they're both autonomous, they're on different SSIDs. Somebody on Twitter is yelling at me saying, well, just put them on the same and it'll roam seamlessly. But I think I tried that and I had problems or it didn't work. Yeah, it's not gonna roam seamless because they are autonomous. They don't know of each other, so they won't roam seamlessly.

And then the iPhone seemed to stick to the first one they're on, even if it's a lower signal, right? I mean, is that a known thing with them? Yeah, Apple devices are known to be sticky. Apple does have documentation, good documentation on how their devices look for new access points. But because you're running an autonomous system, it looks like three separate Wi-Fi systems, but they just have the same as a site. So if I put both of those autonomous APs and

on the same SSID that doesn't solve the problem, right? No, I mean, you maintain the same SSID so it can rejoin to another access point, but it's just not a seamless handoff. So how do I get a seamless handoff? Do I need a controller like an enterprise? You would need like, you can do a controller or you can go get one of those cloud manage APs nowadays. Like even Eero does a great job. I run Eero at home for my family.

And then in my lab, I use the enterprise gear. But yeah, you can use Aero. There's the Google mesh stuff. If you hardwire a lot of those, the roaming is pretty good. It's more seamless than having autonomous APs. So seamless roaming means I don't have to keep, drop it. Like so with my sticky Apple devices, if I have seamless roaming, will it be less sticky? Will it not be still holding on to the, right, right. Like it's still.

Okay, I'm in the ER. That's more of a coverage thing. So devices, we haven't talked about this, but devices are what decide what they wanna do on the WiFi network. We just kinda help, we can try to help influence them or manipulate what values look like to them, but ultimately a device decides whether it wants to roam or not. So Apple devices, because I work a lot of WiFi networks with Apple devices,

they tend to look for a new access point somewhere around negative 72, something like that. And so if your signal is still negative 72, you'll be good. It'll stay on that access point.

So it's really about the thresholds of the device. Those devices, like even a non-Apple device, some of those aren't documented. So it's really the magic sauce of whoever made the phone, the OS.

Yeah, I do think that's something that definitely adds a wrinkle into both the design and troubleshooting is that because a lot of that decision making is left up to the clients. Like you said, Royale, we can try to influence things with certain protocols on the wireless side, but it's ultimately up to the device. So you can have Andy, like you were saying, that issue with sticky clients where you can have fantastic coverage. A client can see.

can have a poor signal, it can see an AP at a much better signal string signal quality, but the client doesn't move. And that's not the infrastructure's fault, that's just the software, the driver, or the type of client that it is. And that definitely can add some confusion and frustration into day-to-day operations. I don't know how you do it every day, Roy. That's.

That shit drives me nuts. Now there is such a thing as too much coverage where I've been in many environments where I've seen access points like every 10 feet. And so when I do a validation survey, I can show them what coverage looks like for each access point. So I'll show them like, look, you have one access point in the middle, you have another access point 10 feet away from it. If I just show you the signal of that one access point, it actually covers the whole floor.

you want to plan it for capacity, which is why they add more access points, right? But I was trying to explain to them that if one person went from one desk to their laptop and went to the other side to their colleagues desk, they wouldn't even roam to another access point because the signal strength is still very, very strong on the opposite end. So they had deployed, I don't know, maybe if I remember correctly, like four or five for an area where maybe.

two or three would be sufficient even for the capacity, but it just becomes one of those things where you need to know the devices that are gonna be on your network. Now I know there are some areas where universities, schools, you don't know what those devices are, but if you can understand maybe generally what kind of device is gonna be there, you can design to the worst capable device. So if you look at warehouses, for example,

you have laptops, but then what is the most crappiest device on that network? It's gonna be those handheld scanners. So you need to design the wifi network to maybe those handheld scanners or even IOT devices if they're gonna be on moving structures. So kind of that you need to design to that least common denominator kind of thing? Yeah, so if you can design to, and that's why these requirements always come up.

is knowing what exactly is going to be used, right? What is the mission critical device that's going to be used on that network? So for hospitals, like maybe it's these little ASCOM devices that doctors and nurses wear around their necks. You need to know how that works on the wifi network. What is its minimum signal strength that it needs? How does that look like when someone's walking? It's in front of them, right?

And if you think about us, we are just bags of water walking around. So we attenuate. I've been called much worse, Roy. I love that.

It's funny because I never tell that to clients. I try to tell them how... You're a bag of water dude. You're just a bag of water. Get out of my face. If you guys weren't such big bags of water, we'd have better signal in this office. I actually ran into that situation not too long ago where this guy was... The access point was behind him, then he sat at his desk and the laptop was in front of him. And he's like, yeah, my Wi-Fi signal is just...

that great. And I'm like, what if we just move to the side? You know, the laptop can see that AP. And then I was just trying to explain to him that, you know, if you put something in front of the device, it's going to get a week or so. Sir, you're a big bag of water. You need to lose some of that water. So we've talked about the requirements. We, we, we kind of talk about the different device types and how there's, there's a lot of uniqueness.

in our networks and it seems I've come across over the years where you'll get vendors of these different device types and Sometimes they'll want their own SS IDs. We're special. We need to be separate from everybody else We need our own SS ID, but you you go back to vendor documentation and best practices on the infrastructure side and You know the vendor documentation is like you really want to limit the amount of SS IDs that that you're throwing out there is that a is that

due to performance and we want to reduce the amount of, or increase the amount of air time that each individual SSID has and the clients have more time to talk. What's the reasoning behind that? Yeah, for every SSID that gets broadcasted, there's something called a beacon. And that's how you're able to see that SSID on your device. And so an access point will broadcast

beacon for every single SSID. If you've got 10 SSIDs, that's 10 individual beacons that get broadcasted out, and that takes up airtime. So airtime is our most precious resource here. And if there's a lot of devices and a lot of SSIDs being broadcasted, you'll have this issue where management frames, which are just the overhead communications of saying here's a Wi-Fi network, tend to occupy most of the airtime.

So there have been some really, Andrew Vonage has been a really great resource for people, especially in my Wi-Fi career. He built this SSID overhead calculator that goes into the math and tells you, you've got this many SSIDs, here's how much airtime that eats up. And so that's why we want to limit the number of SSIDs. So Taylor has a good question.

Does hiding the SSID improve airtime because it limits the beacon? No, because you still have to know about the SSID, right? If it's hidden, how do you know that you can connect to it?

So in a way... I should be asking you that question. I know. How do it know, Orwell? So hidden SSIDs still get broadcasted. They just... it's a frame that just doesn't show anything. The SSID doesn't show... Oh, so it's a null SSID. Yeah, if I do a sniff on Wi-Fi and it's hidden, I see it. I just don't know the SSID name. But the moment your device that's configured for that SSID, once it connects to that SSID, I can then see the SSID.

Because the device will say, hey, I want to connect to this hidden SSID. So that's how it gets exposed. It's so interesting to me the different terms that you're throwing around and like how it... So we talked about coverage. You said capacity earlier that OneOffice put in a bunch of access points to increase their capacity. I'm surprised to hear... I mean, is capacity a big issue you run into a lot? Like how...

Because then I go to like a sports stadium, you got like 70,000 people sitting in a stadium. How the hell would you handle that capacity without having one every 10 feet? So what, can we talk about capacity for a second? I mean, I would think our hardware has gotten to the point where one access point can handle a hell of a lot of bandwidth. Is bandwidth and capacity the same thing, or am I not even in the right ballpark? Yeah, you've got, so even I get confused on these terms, right? So the way I think about capacity is,

how many devices can sufficiently do what they need to do over on that access point over the air, given the application that they're trying to use. So I always go back to, all right, you've got 30 devices, they all need to do Zoom. Like if you just do the math of like five megs requirement per device, and there's these calculators that you could use online that determine

how many, I go back to Andrew Vonage, he created an Excel sheet that helped calculate how many access points you need to sufficiently cover the types of applications are being used per number of devices. Going to the stadium example, those are much tougher environments. So usually it's not the best performing WiFi networks, but you have this, what I call a take rate. Not everyone.

is going to be using Wi-Fi simultaneously at a stadium. You're there to watch an event. You may get more people just trying to record something and upload that to social media. But they're not sitting there. You've got to publish those selfies, Raul. I was here. Yeah, exactly. Yeah, you've got to have proof. And that's usually what the stadiums are going for. But now they're adding things like ordering from your seat, order concessions. And so that becomes more of a challenge.

6 gigahertz as much more people want to get used to 6 gigahertz. And now there's other wireless technologies as well that could help with that. Because we haven't even talked about some things like private 5G that has other use cases. Ultraband has other use cases. Those are all operate on different frequencies have different use cases. But Wi Fi is generally the most widely used one.

Capacity is just the hardware's ability to handle It sounds like bandwidth to me because you said like yeah, like you said 30 It's mostly physics right just how much stuff you can jam into those air signals at the same time There is a capacity for access points So you'll see things like channel utilization that channel how much is actually being used up by Whatever's being transmitted over the air

But then I find too that access points have their limits. Some access points do well with more clients on them, some do not. So there's no equality of vendor there. I'll hear vendors say, hey, we all use the same chipsets, but it also comes down to their developers and how well their chipsets interact with, I don't know.

Stuff software baby. I just knew yeah the software they have their own set of API is using with the chipset. So Software is part of it quality of the hardware quality of the radio that's on the access point matters as well So I do want to pivot a little bit. We've been talking a lot about these post deployment validation surveys and You as a wireless engineer you you have to know

the tech behind it. You have to know wireless, you have to know the physics to an extent, but you then also have to turn over a report to a customer at some point. So you, I think you know where I'm going with this. You have to have a skillset too, to be able to explain your findings to people like myself who don't know what the hell you're talking about and don't understand those things. So how have you done that in your career? How do you take?

that all of that data, all of that detail that you've gathered in your surveys and present that to somebody who doesn't really understand.

Yeah, so it comes. This is where in our careers where the soft skills really matter, right? I can talk technical all day, but you may not understand what I'm referring to. If I start putting out three letter acronyms and DBM values, you don't know what that means to you at the end of the day. So it comes down to still knowing what their requirements are. Like what, why do they need wifi? What are they trying to achieve over it? But

they have it deployed and they're not able to meet those business objectives. So I try to map the results of a survey to certain business objectives as well as technical objectives. A lot of times I see misconfigurations. So that's the majority of the things I see. So when I'm talking to technical people, they tend to understand what I'm referring to when I say, Hey, here are the different settings you can, I recommend to optimize this so you can get

better performance over your current deployment. And a lot of times it's referring to numbers, right? Maybe they got a quote to replace the vendor. I get this sometimes where they say, you know, we're just gonna rip and replace vendor A for vendor B, and I'm pretty sure that'll be much better. Okay, I mean, if my car wasn't working, would I just go buy another one just because, or would I try to figure out what's wrong first? So there's different ways to handle it based on who you're talking to.

And I think the soft skills are such a critical point where you want to be able to relate to to the end user, be able to address their main concerns rather than straight up talking technical jargon, confusing them. You may sound smart, but you're just confusing them even more. And they're just wondering why they paid you to come out and you don't know what you're supposed to do after this. Yeah, I think that's I think that's tough. And what something that a lot of us struggle with is.

As we try to become better versed in our craft, we learn those things. We learn the acronyms, we learn the tech behind it, and we get those so ingrained into our heads that I think it's nature for us to just go to that when we're trying to explain stuff to other people. And yeah, it's very important to be able to know your audience because at the end of the day, you're there to provide value. And if you're just saying things that

mean the world to you, but nothing to somebody else, your customer, then it does nobody any good. And like you said, they're wondering why they paid you to come out and do that. Yeah. I mean, knowing the technical stuff, don't get me wrong, knowing it really helps. It'll help you even further if you can translate that to something people can understand. And so I always tell people to at least get their CWNA, which is the foundational wifi.

non-vendor, it's a vendor neutral certification. It's the certified wireless network administrator. That'll get you so much knowledge and foundations into Wi-Fi that that alone will give you what you need to get started and become better. And then knowing and talking to other people, being able to translate that jargon will even, you know, it just makes it easier for you.

because you actually bring more value. And then for your end user, or even just your coworkers, maybe you're talking to some VP, he just wants the breakdown, right? And this is what I learned over time, is when you talk to with higher ups, they don't care about the technical stuff. They just wanna know the bullet points of what needs to be done, and have you done it already? And so, if you can break down the troubleshooting and the validation survey into three bullet points, five,

You're golden. Doesn't that sound great? I can't wait to be a VP and not have to deal with the technical crap. Just give me the five bullet points, Tim, and stop giving me all this damn... I've learned that with my reports. I've sent some out to... Because a lot of times I deal with the IT managers or network engineers, and when I do deal with VPs, the first thing they always say is, I just need the summary of what needs to be done. They don't even care for the results.

in the beginning of my reports have an executive summary that says, this is what you need to do. This is what happened. This is what I found. This is the issue. Here's how you fix it. I have a CWNA question. I actually thought that was a Cisco certification because of the C. So I'm happy to hear that's a vendor neutral one. Would you recommend that, do you need a baseline of networking knowledge before you go into that? Like should you have your CCNA first or can you just go in blind and will it teach you

Network fundamentals as well. Like, right, cause you can need network fundamentals in a wireless, right? Or maybe not, like, I don't know. Not necessarily. The CW&A is by a group called CW&P, certified wireless network professionals. And that certification covers just wifi generally. So you don't need to know things like submitting and stuff you don't need, you have calculators for anyways, right?

Same thing, I have my own calculators and Wi-Fi as well. And so it'll give you that knowledge, right? The different frequencies that are being used, what are the different radio frequency characteristics, how does antenna selection matter, what are the different types of antennas, all that will help. Even if you're a salesperson, be a better salesperson, because then you can sell the right wireless equipment.

I've come across lots of salespeople who just generally throw a lot of equipment in there, but I've gone into those scenarios where the customer just wants to rip and replace it because they just think it doesn't work. But really, they just didn't go in with a plan. So they didn't do a design. They didn't configure it properly. They didn't make sure it was installed properly afterwards. And so where the networking actually comes into play is troubleshooting.

because most of the issues, you guys know what most of those issues are, right? Internet's slow. DNS, DHCP, routing. I'm just kidding. Is that the biggest complaint you get? It's like, my wireless is slow. Yeah, wifi is slow. That's a tough one to crack. I keep, my wifi drops. Oh yeah, that's a big one. When it.

And then when I really dig into it, it's never dropped actually. And they just think it drops. So you, you, I want to ask this to him before we wrap. I know we're getting close. So. You know, you talked about, you were a help desk guy and I don't know if you went to network and then, and then, um, wireless, but you were in a role, like a technical role, networking adjacent and got into wireless. So for somebody listening who like loves wireless, has a passion for it, thinks it's amazing that.

would like to get in, maybe they're not a network engineer or help desk person who can fill a gap like you had said. Is there a recommendation you would make? Is it, you know, get your CW&A and do these two or three other things and then get a gig? What's the path? Yeah, if you had to say. Yeah. So I think it's always a common question, right? Even for people who are trying to get into network engineering in general.

I'm a little biased because I came from help desk and I understand the types of tickets that come through. And I've seen tickets just get thrown around like hot potato because people think it's they always point fingers right. It's always a firewall issue or routing issue kind of change that you make. For me if you if you've if you really like Wi Fi and want to get into it you can get into it right away because we all have Wi Fi at home right. It's

The Wi-Fi at home is not that much different from enterprise. You just have different equipment. You have a consumer equipment, whereas enterprise has enterprise equipment, but it's the same frequencies, same protocols that are being used. So you can pick up that CW and A-Book and be able to go through it and start using your own Wi-Fi network as a lab. So that's easy to get into. You don't need to purchase enterprise equipment.

The only time you need enterprise equipment is for enterprise features. So things like RRM, C in a consumer device, I won't be able to toggle that on my ear row. It just does it for me automatically. Now when it comes to being very, very useful in your job, and I'm talking general jobs like you walk into an organization and you're going to wear many hats, right? This is where

Knowing, having done help desk really helps. One, because it gets you closer to the user and you understand how the user does their work. You know what kind of things they're doing to make problems because they do cause problems. Two, you work on your communication skills because now you're gonna talk to end users. So you gotta learn how to talk to them in a way where you're not demeaning them or being disrespectful, communicate things properly to them.

Things like troubleshooting over email, this is the hardest one. Telling a user what to click on specifically, that's hard, right? So being very descriptive, like when a user says, well, I'm on a Mac, how do I do that? Well, I know how to do it because I use a Mac, so I can be very descriptive, but when was the last time I used Windows? Like I still know generally how to get there. Or even dealing with server guys, like I've had a server guys where they say, hey,

My server is not talking to another server. I think it's a network issue. And so you just have to know fundamentals of networking to kind of drill in and troubleshoot, right? It's the same thing with Wi-Fi. But knowing help desk kind of gets you actually in the mindset of knowing, all right, if a user has a Wi-Fi issue, what kind of questions can I ask them to try to get to a root cause without wasting a lot of time? And then.

getting into networking with a, I always tell people CCNA just because it covers such a a wide area of networking, they get into subnetting, which is important. I've seen a lot of weird subnets out there at different clients designs, like network designs that are kind of questionable. And then troubleshooting wifi, where networking comes in handy is when someone says there's a wifi issue and you've ruled out wifi being a problem.

Radio frequency not being a problem, the configuration of Wi-Fi not being a problem. How do you then tell someone where to go next? If I say Wi-Fi is not the problem, but the user is still sitting there going, well, I am not working over Wi-Fi. It sounds like a Wi-Fi problem to me. Then you're kind of useless, right? And so knowing how to troubleshoot a little bit further and understanding, okay, do they have an IP address? What subnet are they on? Can they reach the gateway? Can they reach us another subnet? Can they reach the internet?

Those kind of things. That's where networking does play a big role. Like, what's the difference between pinging an IP address and pinging a host name? Does that mean DNS works or not? I've run into different scenarios that way where they kick up an issue to me saying it's a WiFi issue, but when I start troubleshooting and go, well, you know, that person has an IP address on a subnet that doesn't have access to this resource because

It's a visitor SSID, which has no access to internal resources, that kind of thing. I love how you said that you can just, everybody has wifi at home pretty much. Yeah. Have a lab and learn that way. There's some free, I don't know if I'm using the right terms, but like heat map software out there, right? I've always wanted to do this in Haven, but I want to walk around with my laptop and look at the visual representation of my wifi. Is that what a heat map is? You can see your wifi. If it can.

Yeah, if it can display signal strength on a floor plan, that is a form of creating a heat map from that device's perspective, which is pretty good. Do you have any free software you recommend? Or like, I mean, just Google it. Like what could I put on my Mac and just walk around my house and see wifi? Like if I wanted to- Yeah, I mean, I can tell you some of the applications I use on a daily. I don't know any free heat mapping software. Oh, okay. You use all the- I know there's some that are out there. I just don't remember the name.

And there are some that are inexpensive compared to some other software. But I, on a Mac, I use wifi explorer a lot. There's also on a Mac tool called air tool and wifi signal all by the same guy. I think his company is called intuitive bits. If you just Google those names, you'll find it on

On Windows, I'm not so sure what's there now. I've tried to find reliable software, but they tend to either come or go or they don't work. But I know there are some PowerShell commands that you could run to give you some statistics over your Wi-Fi network, like your signal strength and what AP you're connected to, which would indicate my term BSSID, what your signal strength is.

There are different wire shark, I use that. And so if you can capture, same as you can do a PCAP on the wired network, you can do the same on a wifi network. Capture frames that fly through the air, you can capture those and really understand how an AP and a client communicate. I can see wifi, Tim. You're like a spy now, Andy.

I am a spy. You got anything else, Tim? I've learned a lot here. I don't think my brain can handle anything else. This has been great. There's a lot to dive into. Yeah, there is. Yeah. Yeah, I think that probably means we need to wait less than 110 episodes before we do another one on wireless. But we'll see. But Roy, thank you so much for joining us. Where can people find you out on the socials?

Yeah, you can find me on Twitter at Rowell D'Anecio. I tweet a lot. Or you can find me on LinkedIn. You can also find me and my co-host Francois on the Clear to Send podcast. It's, where it's strictly Wi-Fi. So we actually tell people if they want wired network engineering stuff to go to your podcast to go listen to that. We appreciate that. How long have you been running that now? Oh, since 2015.

Oh wow.

That's impressive. You still like it? I didn't think we'd come. You still enjoy it? You know, sometimes it's like a job. Yeah. I don't know if I can come into work today. Isn't it amazing how much it goes through, right? Like you're just, you know, running the show and topics and research and just a lot. That's the hard part. It's become, the research into coming up at the content has been a challenge. Like I'm, I have a topic in the Hopper for a long time now for a few weeks.

I just haven't had the time to lab it up. And it's strictly about, it kind of dives into wired a bit, but it's about iOS device discovering an Apple TV and how it can discover it, even though the Apple TV is not on a Wi-Fi network. But it's on a wired network and on a different subnet. And so I have a lab I'm setting up specifically with my iPhone, my Apple TV, and a Palo Alto firewall in the middle.

with one access point. Hey, have you got a Palo at home? I do. Big buddy. Yeah, that was without getting too deep into it. Yeah, that's definitely something I've come across, too, is you run into some of these technologies, like AirPlay, that leverages multicast DNS. I mean, it was designed for home networks, right? So it's not a routed protocol. And then you have everybody who wants to bring these into production environments.

We're much more segmented. We do this for usability and security. And no, I can't easily bridge those two networks together. And it just becomes a whole thing. I didn't say my favorite phrase yet. It works at home. Why do you never catch it in the office? And I'm like, wait, it works at home? Do you have like 10,000 clients and 9,000 ATEs at home? I don't have an IT staff at home, but I can get this to work. Why can't I do it here?

Yeah, I hear that a lot too. And it annoys me. Yeah, I'm looking forward to that. You'll have to let us know when you release that one. That's interesting. But yeah, thanks again. Thanks again for joining us, Roel. Andy, always a pleasure, my friend. Keep the scruff going. I don't care what your wife says. Nice to meet you too. You know what? The only reason I have it is she digs it.

I'm just trying to, you know, trying to keep it going over here with Tim. You know what I mean? The only reason I have mine is because mine doesn't like it. I'm very spiteful if you didn't know that about me. I can't really grow. I can't either. Mine's trashy as hell, but I've embraced it. It's my thing now. I'm trying. I'm slowly trying to become the creepiest looking dude on the planet and I think I'm doing a good job.

You know what? You got to stop with that. You look really good. I'm a thanks man. Like what you got going on. You both look good. I wanted to say it earlier, but well has the most like soothing voice. I feel like, like I'm just, I'm so Zen, but right. Like he just says, Hey man, what's going on? You know, he's got the Welcome to network.

Tell me better before it gets weirder. Yeah. Thanks everybody for joining. To find out more about us, you can check us out on our website, Find us on Twitter at Art of Net Inge, and you know, Google us. We're anywhere and everywhere. We tweet as a podcast, as us as individuals. So you'll find us out there. Thank you for joining us on the Art of Network Engineering. We'll see you next time.

Hey y'all, this is Lexi. If you vibe with what you heard us talking about today, we'd love for you to subscribe to our podcast in your favorite podcatcher. Also, go ahead and hit that bell icon to make sure you're notified of all our future episodes right when they come out. If you wanna hear what we're talking about when we're not on the podcast, you can totally follow us on Twitter and Instagram at Art of NetEng. That's Art of N-E-T-E-N-G.

You can also find a bunch more info about us and the podcast at art of network Thanks for listening.

Podcasts we love