Connect EVE-NG to VOIP Phones and Wireless Access Points


throughout this evg playlist we’ve talked a lot about how to connect even g to a bunch of different types of devices maybe devices within even g maybe devices running from one topology to another topology or even how to connect even g nodes to other vms running on the same host but now we need to take it a step further because there are still some devices that no matter how hard you try you simply can’t emulate them i’m talking voice over iphones as well as wireless access points so by the end of this video you’ll understand how we can create a hosted esxi environment where even g nodes can communicate securely to other physical appliances within our network like voiceover iphones and wireless access points let’s get going all right y’all don’t make fun of me because of how messy this is i’m trying to set up the the twins new bedroom so this is where i just had to shove my lab for the time being so here we go i’ve got this wireless access point just sitting on the floor it actually goes into a poe injector right here and then from there the black cable goes right there into port 23.

You can see it’s amber right now on the switch and then right here this is even g so what i want to do is i’m going to take this this third nick right here i’m going to plug this in and i got to undo these twist ties hang on one second i got the twist ties undone so there we go you can see i’ve got the third nick now plugged in here and i’m going to plug it in to port 21 on the switch so i’ve got port 21 is going to be one of the even g clouds and port 23 is what leads into the poe injector which leads into this ap which is blinking at me right now trying to come to life so that’s what we’re going to do we’re going to try and get even g talking to this ap over one of the clouds that we talked about in a previous video this can be a bit of a complicated setup to understand fundamentally and logically so let’s kind of talk about what it is that we’re trying to do in this video here i have my physical server and again we’ve got my three nicks oop let me kind of stop doing there we go there’s my three nicks that we’ve got here then i had my physical switch sitting above it and all the way over here we had ports 23 i’m going to write it like this and we had ports 21.

Beyond that i also had my wireless access point i’m going to kind of draw it like this so it looks like this we connected the third port here into port 21 and we connected the wireless access point of course through a poe injector into port 23. beyond that we got to think about how vmware works vmware is going to create we need to create a new isolated way that way even g nodes can communicate into vmware out this nic and then into these two ports where they can communicate so here we’re going to need to create a vlan that isolates these two ports together let’s just call this something like i don’t know vlan 28 just to make something up and it’ll be the 172 28.0.

0 24 network beyond that on this switch i’m going to create an interface for vlan 28 so that we can run a dhcp pool for vlan 28.

Now recalling a previous video we have a default v-switch in vmware that binds itself to this nick and that’s how these devices communicate out to the outbound internet but now what i want to do is i want to create a new v-switch that binds itself to this nick right here the third nick and it will be able to serve a port group for vlan 28. so we’re going to have two v-switches one that’s going to be for our physical internet and one that’s going to be also for a physical network but it’s going to be isolated by vlan 28 and that’s how my nodes will be able to communicate into vlan 28 we’ll be able to use a cloud just like we’ve done in previous videos by attaching the evm into this physical v-switch so there is a lot going on here and that’s what we’re going to cover in this video let’s get going with it all right first things first i am on the physical switch here if i give it a show ip interface brief i should see that sure enough ports 23 is up that was going to be my ap and 21 is up and that’s going to be my server so let’s go into interface get let’s actually no let’s do this first let’s create vlan what did i say it’s going to be 28 there we go and i’ll give it the name wi-fi something like that now i’ll go into interface vlan 28 and i’ll create the ip address for 172 28.0.0. oh of course this does need to be an actual ip address and not a subnet right i’m already thinking about the dhcp pool let’s exit out and let’s create the dhcp pool for that subnet ip dhcp pool let’s call it wi-fi it’s going to be for network 172 28.0. let’s say default router is going to be this device 172 28.

0.1 and dns let’s just hand out 8888 something simple like that now of course we need to exclude the address with ipdhcp excluded address let’s remove 1201 so that way it doesn’t hand out the router’s address as part of the dhcp pool now we need to actually assign interfaces into vlan 28 and we know that’s going to be interface 21 and interface 23.

So i’ll say interface gig one slash zero actually you know let’s just do this in one field interface range gig one slash zero slash twenty one comma one slash oop one slash zero slash twenty three oh it’s gotta be gig doesn’t it there we go and we’ll say switchboard access vlan 28 and make sure it’s on switchboard mode access as well but as i’m typing this i realize wait a minute that’s not how vmware works these v-switches when they attach to a nic they’re sending a trunk out outbound even if there’s only one port group attached to it so what we need to do is we need to actually tag this traffic as it’s coming in through the nic and into the switch now we plug the server into port 21 so port 21 actually needs to be a trunk let’s change interface gig one slash zero slash 21 and we’ll change this to switch port mode trunk and just for fun i’ll say no switchboard access vlan 28 so if i say do show run interface gig one zero 21 we see it’s just switch port mode trunk and if i check out 23 we’ve got it set to vlan 28.

So as traffic comes out of the v switch and out of the server into the physical switch it’s going to be tagged with vlan 28 then of course as it arrives on the switch that tag will be removed and it’ll be sent out to the rest of vlan 28 in this case it’ll be our wireless access point so now let’s exit out of this switch that we’ve been configuring and we’ll start setting up the esxi server to handle vlan 28 and attach to the correct nic so here we go i’ve got esxi brought up here and if i jump into the networking section i see that i’ve got a bunch of different port groups but if i look at my virtual switches i’ve really only got two virtual switches here one that’s for my main network and one that i specifically created for my dna center now this one is attached to my first physical nic and this one is attached to my second physical nic but if i look under physical nics i see that i’ve actually got a bunch of physical nicks here i’ve got four and those are these b and x threes that we see here and in fact one of these b and x threes this v-neck two we see that it’s actually showing an up status that’s because we did plug it in beyond that i can even take a look at the mac address seeing that it ends with e48c so if i need to use this mac address for any troubleshooting later i can see oh this is the mac address that i’m specifically looking for this one that ends with e48c so let’s start creating our physical vert let’s start creating our virtual switch that’s going to bind itself to that physical nick and then we’ll create the vlan on that virtual switch so i’m going to choose add a standard virtual switch we’ll call this wi-fi v switch something simple like that i’ll leave the basic settings here the same i am going to accept promiscuous mode because that’s how this traffic is going to work in fact i’m just going to accept all of these things here because that’s kind of the entire point when it comes to even g and virtualization we’re going to be sending in multiple mac addresses on the same nic coming into this virtual switch so my uplink here is bound to that vm nick 2.

If i had plugged in the other vm nic i could add a second uplink here and do some load balancing but this is fine this is binding vmnic2 is the third physical nic on my particular server so i’ll click add and now i have my wi-fi v-switch now i have to do is create vlan 28 which is a port group on that v-switch so i’ll say add port group i’ll call this wi-fi one more time the vlan id is 28 and the virtual switch that this needs to be in is my wi-fi v switch if i expand security here we can see it’s going to inherit the settings from my v-switch doesn’t hurt to go ahead and just set these explicitly to accept as well so i’ll click add and now my esxi host is now bridged out to that physical server which is now going out up a trunk port into that particular physical switch all i have to do now is add a physical nic into even g that connects itself to that port group so on my eve ng vm i’m going to choose edit here add a network adapter and if i scroll down i see it’s added the third network adapter right here and i’m going to choose to connect this to the wi-fi port group so at this point consider this is how it’s going to work here’s my eve vm it’s got a nick here that goes out to the internet it’s got a nick here that i used in my previous video where i connected eve vms to other vms on the es6i host now i’ve just added this third nic here which goes into my new v-switch it belongs to the port group which has vlan 28 on it that v-switch is connected to the third physical nic on my server so i’ll just draw two others here so you can see that it’s clearly the third this third physical nic on my server is a dot one q trunk that goes into port 21 on my physical switch and now because the traffic was tagged with vlan 28 up here this can communicate to vlan 28 traffic anywhere in my physical network which is where my wi-fi adapter is so now within eve i could spin up things like a virtual wireless lan controller that can communicate all the way down to my wireless devices i’ll click save here and just for good measure i am rebooting my e-virtual machine so let me get signed in here we can even say it tells me to keep using the same ip address that we’ve been using that’s a good sign too all right after the machine has rebooted i am getting signed into my eve in g lab and as we can see here i’ve got some devices with some networks that i’m playing with in the background here’s what i’m going to do i’m going to add a new network into the mix here this is going to go back to those cloud networks that we talked about in a previous video and understanding how they bind to different networks now before we add cloud zero which goes out to my management network by default that’s the default nic then we had cloud one that was the second nick in esxi that even g is bound to so here is cloud zero here is cloud one so this will be cloud two so if i jump back to my evg topology i’m gonna choose cloud two i’m gonna call this the wi-fi cloud and i’m going to change the symbol here to actually be a cloud and i’ll click save and now just for good measure i’m going to add a node something like a cisco wireless lan controller so i’ll click save here to add the wireless lan controller onto the topology i’ll drag it onto the wi-fi cloud and click save and then i’ll give it a start let me bring up the console of the wireless lan controller here and we’ll watch it come to life in fact while this is coming to life a good idea would also be to grab a new little docker container so that we could manage our wireless lan controller from a front end so let’s use the gui server or we could use firefox doesn’t really matter i’m going to use the gui server just for good measure and i’m going to enable dhcp on ethernet 0 that way it grabs an ip address from that dhcp pool that we created on the actual switch itself i’ll click save to this and i’ll drag this onto the wi-fi network as well and click save i’ll also boot that container up so we’ll continue to wait as these devices come to life here let’s actually terminate auto install we’ll say yes terminate auto install interestingly something i forgot about these wireless lan controllers look at this they run a dhcp pool by default so that’s something that is an issue that you might run into when you start your wireless lan controller for the first time if you want to use a different subnet other than 192 1681 and you’ve already created a dhcp pool somewhere else now you have two dhcp servers on the same subnet that’s something we’ll have to fix so here i’ve brought the gui server to life let’s bring up these system tools and the terminal real quick and i’ll give it an ipaddr and i see right here it did in fact get an ip address on the correct pool so at this point if i jump back onto my physical router and do a show mac address table let’s see what we got going on here under vlan 28 look at this now i see a bunch of different hosts and in fact i see two hosts coming in over the trunk port for vlan 28 this is going to be my wireless lan controller as well as the physical gui server let’s check out show ipr one second and interestingly i see 172 2816 which i assume is going to be one of my virtual devices because the mac address right here lines up right here on gig one zero 21.

In fact i verify that right here yep here it is on my gui server 172 2816. let’s see if the wireless shows up and shows cdp neighbors sure enough it does right there there’s my wireless device on gig 1023 let’s say show cdp neighbors details and i see its ip address right here 172 28 0 21. so if all works that means my nodes that are running in even g can ping my nodes that are physically existing like my wireless access devices there we go we have round trip traffic from my even g nodes all the way out to my physical network where my wireless access points are so this node which is running an even g has the ip address 172 0 16 it communicates out the third nick of my eve vm into the new v switch that we just created bound to the third nic of my physical server trunked into the physical switch and then from there out to the wireless access point quite a journey right but this is how we can get even g now communicating to devices like our wireless access points or like our phone devices which is really cool stuff if you need to start labbing things like how wireless works or how telecommunications work so that’s been how to get evg talking to your physical network where you can have an isolated vlan just for devices like wireless access points or for communication devices like voice over iphones.

banner 27aug13




Free VOIP (Skype) for iPhone

VoIP (Voice Over Net Method) is incredibly well-known these days. With this system, a lot of people have the ability to connect at no charge. Although there are small charges in some circumstances, the last is so little that many still intend to connect this way. In addition, VoIP can be quickly made use of as soon as you have developed a Web connection.

The Issue of VoIP Latency

From the earliest days, among the complaints versus VoIP was that it presented an unacceptable quantity of lag right into telephone conversations. Using the appropriate configuration however, we can alleviate the majority of that downside.

Evolution of Cloud PBX VOIP

We are residing in the age of the computer systems and also we no more do points the standard methods. Organizations – no matter of their size and scale of operations – are coming to be progressively reliant on the web for its day-to-day procedures. As most of us are aware, PBX (Personal Branch Exchange) makes links among the interior telephones of a private company as well as also connects them to the PSTN (Public Switched Telephone Network) using trunk lines.

International Conference Call Service – What Are Its Contribution To Business World?

International seminar call solution is commonly utilized nowadays by small to large time company owner for reaching clients, associates and financiers across the globe. It has actually made cross country calls more affordable and faster in actual time.

Experience More Rewarding Interactions With Cutting Edge Audio Conferencing Services

Audio conferencing has actually gained tremendous significance in today’s day and age of seamless connection. The requirement to connect, connect and engage with crucial sources at numerous degrees has raised for many years. Top teleconference company are helping companies stay connected with the people who matter.

You May Also Like