Wi-Fi 101: Origins and History Networking |
- Wi-Fi 101: Origins and History
- Moving VMs from one data center to another while keeping the same IP addresses
- Question about monitoring fan inlet temperature on Cisco 3850.
- KISS Small Business Network
- Dell S-Series Stacking
- ASN Naming / Nomenclature?
- Optimum Wireless Configuration in a MDU
- Question about DHCPOFFER through a Relay
- Issues pinging from VM to VM
- IOS-XR Show Commands with Regex?
- Watchguard IPSec VPN default parameter
- Adtran VRRP
- Pulse Secure
- Best Practice for Deploying a Wireguard Server on Network
- Using dual NIC's on server and workstations to create dual networks for a seamless switchover to backup WAN/ISP
- Documentation template?
- Is there a better way to move a large file (image) from one network share to another?
- How does ARP work over wireless if broadcast traffic is trimmed?
- IOS-XE RESTCONF Interface Call Question
- VPN with Digital certificate enrollment question
- Is there a wifi vendor who supports multiple VLANS per SSID using WPA2 authentication and different preshared keys?
- Recommendations...
- Advice for my future
- Does ARP suppression without SVI on Spine-Leaf
| Wi-Fi 101: Origins and History Posted: 30 Sep 2020 09:07 AM PDT Wi-Fi as we know it today is a series of standards, voted on by a worldwide engineering body, the IEEE. The IEEE is an open membership organization with more than 423,000 engineers in 160 countries. It took years of work and dozens of proposals to form the original Wi-Fi standard in 1997. It took even more effort over the last 23 years to get to where we are now. The story of the invention of Wi-Fi depends on who you ask. There is a complicated history leading up to that original 1997 standard, and the truth is hard to decipher. I'm not capable of litigating who invented what, but there are some key players to know about. Where possible, I will point out the people and the organizations behind the technology. Wired and Wireless Precursors: Say ALOHA to Wireless NetworkingIn 1968, researchers at the University of Hawaii began to investigate if radio waves could be used for communication between computers. The project was led by professor Norman Abramson, Dr. Franklin Kuo, and a team of faculty and students. It would go on to become known as ALOHAnet. During this time, wired computer networking was in its infancy, and evolving rapidly. Packet switching was conceived of by Paul Baran in 1964, and first demonstrated by Donald Davies in August 1968. In October 1969, the first ARPANET link was established between UCLA and the Stanford. By June 1971, ALOHAnet was the world's first wireless packet switched data network.(1) During the development of ALOHAnet, Abramson and his team had to solve many foundational issues with wireless networking, including collisions and failed transmissions. They decided that a random access protocol would be the best way to accomplish this. The ALOHA protocol allowed terminals to send data whenever they had it, and listen to their transmissions to make sure they were received, and acknowledged. If a transmission failed, terminals would resend after a random delay. This was simple and effective, but had problems scaling up to more users. The ALOHA protocol was improved and expanded, and was the inspiration for CSMA/CA. ALOHAnet was a pioneering technological marvel, but it was experimental and not fit for commercial use. Most critically, unlicensed spectrum for computer communications was not available to the public yet. Since the University of Hawaii didn't have a way to sell the technology, it was put into the public domain. ALOHAnet was decommissioned in 1976, but it inspired others to continue what it started. Most notably, Robert "Bob" Metcalfe studied it for his PhD dissertation. Through the 1970s, many wired local area network technologies were developed. Some were proprietary, and some were open standards. Most of this early work has gone on to become ANSI or IEEE standards, and formed the basis of the computer communication and the Internet. A standards-based approach wasn't destiny, and we all benefit from the pioneers who pushed for standards over proprietary solutions. All of this groundbreaking work on wired standards helped lay the foundation for wireless. Key Dates In Wired Networking History
The Wright Brothers of Wi-FiBy 1985, all the pieces were in place for the development of a universal wireless networking standard. These were the Wild West days of wireless networking. Dozens of companies were competing to be the first to produce a successful product. Many companies came and went, so I'm only going to focus on the biggest and most important ones. NCR and WaveLANIn the 1980s, NCR Corporation was a big international company selling computers, ATMs, and cash registers. They wanted to develop a way to have their cash registers work wirelessly. This would give them a competitive advantage, and allow retail stores to avoid the costs and logistics of running cabling to every register. At the same time, cash registers were becoming more computer-like, so NCR sought to develop an International wireless standard that any computer could use. Two of the key engineers assigned to this project were Cees Links and Vic Hayes. Through 1986 and 1987, Vic and the other engineers at NCR developed a product which became known as WaveLAN. NCR introduced WaveLAN to the world in 1990.(2) While WaveLAN was intended for use in cash registers, it was also positioned as a wireless alternative to Ethernet and Token Ring for PCs. In the 1990s, wireless products were expensive, and hard to use. The early drivers were buggy, and documentation was hard to find. WaveLAN network adapters cost hundreds of dollars, and access points could cost thousands. The high cost and limited usability kept WaveLAN as a niche product, mainly found in the big businesses that could afford them. WaveLAN operated at 900MHz or 2.4 GHz, and offered speeds of 1 to 2 Mbps. It competed with Aironet's ARLAN and others which offered similar speeds, frequency ranges and hardware. Several companies also marketed wireless bridges and routers based on WaveLAN technology. Wireless networking products became a mess of competing companies and different implementations. The need for an International standard was clear. NCR wanted to have Vic Hayes make the technical proposals to the IEEE on the companies behalf. Vic disagreed, and fought to stay independent and not do any of the proposals on behalf of NCR. The company agreed, and this actually worked to their benefit. Since Vic wasn't pushing NCR's proprietary solution, he gained the trust of others. Vic ended up becoming the first chairman of the IEEE 802.11 working group, giving him the nickname "Father of Wi-Fi" IEEE and the 802.11 working groupIn 1988, Vic Hayes approached the IEEE to contribute to the 802.4L, an existing committee creating a wireless standard based on Token Ring. As it turned out, that committee had become inactive, and the chairman had quit. This let to Vic becoming the chairman of 802.4L, and the forming of a new working group, 802.11. Ethernet and WaveLAN technology formed part of the technical base of the 802.11 committee, which was officially started in 1990. WaveLAN and the knowledge of Vic Hayes' group at NCR helped form the basis, but countless others contributed as well. Many other companies submitted proposals for various aspects of the standard, and the group compromised and voted on the best ideas along the way. Most of their documents are still publicly available. The 802.11 group continued to work throughout the 1990s to develop the standard, which was a long and complicated process. It took 7 years and input from countless engineers to form the first Wi-Fi standard, known as 802.11-1997. The first Wi-Fi standard was in some ways a messy compromise. It allowed for transmissions over Infrared or 2.4 GHz radio waves. It also allowed for two different frequency selection methods, which prevented guaranteed compatibility. In the end, both Frequency Hopping Spread Spectrum (FHSS) and Direct-Sequence Spread Spectrum (DSSS) were added to the standard. The group allowed these options as a way to please the entities involved in the creation, but it made the standard weak. 802.11-1997 never gained much traction. Despite that, the group got to work on its next set of standards, 802.11a and 802.11b, which were developed in parallel. The main difference between them was the frequencies and the modulation schemes they used.
802.11b hit the market first. Despite the slower speeds, people preferred the availability, lower cost, and longer range of the 2.4 GHz equipment. The success of 802.11b snowballed into the development of 802.11g, and made 2.4 GHz the defacto International wireless spectrum range for years to come. In the late 1990s, Wi-Fi's success wasn't guaranteed. Early Wi-Fi devices were expensive, slow, and often incompatible with other devices. According to Vic Hayes, he approached many computers makers to persuade them to add Wi-Fi to their computers, but most of them said no. Steve Jobs and Apple wanted to add Wi-Fi to an upcoming laptop, but they wanted it to cost $100, not $500. They argued that the lower cost would make it more marketable to consumers. Apple eventually got the $100 Wi-Fi card they wanted. The iBook and AirPort launched on July 21, 1999, a few months before the 802.11a and 802.11b standard were finalized. It was the first mainstream computer designed and sold with integrated wireless networking. OFDM, CSIRO, and Dr. John O'SullivanThis is where our story get murky. CSIRO is the Australian federal agency with a long history of scientific research. They have developed many advanced technologies, such as atomic absorption spectroscopy. According to CSIRO, Wi-Fi is an Australian invention. The truth isn't that simple, and it isn't that clear. CSIRO's key insight came out of their work in radioastronomy. In 1977, CSIRO researcher Dr. John O'sullivan was searching for small exploding black holes. He wrote a paper about how fast Fourier transformations could be used to sharpen images from optical telescopes. As the waves traveled towards the telescope they became scrambled, and CSIRO developed a custom processor to use fast Fourier transformations to unscramble the image. While this technique didn't help him discover the black holes he was looking for, it helped to solve a different problem. Starting in 1990, John O'Sullivan led a team of CSIRO scientists to develop a high-speed wireless network. Their goal was 100 Mbps, to compete with the best wired networks of the time. This caused them to look past the techniques used by ALOHAnet and WaveLAN, because they wouldn't be fast enough. One technical challenge they faced was how radio waves tend to bounce off surfaces indoors, causing an echo that distorts the signal. Using fast Fourier transformations, they found a way to transmit a signal while reducing that echo. Rather than using one fast wireless channel, they used lots of slower channels. This is known as multicarrier modulation. Single-carrier modulation systems exploit only one signal frequency to transmit data. Multi-carrier modulation systems divide the whole frequency channel into subcarriers, and the data stream is divided into many low-rate streams transmitted in parallel. Single-carrier modulation has advantages, but multi-carrier modulation is better suited for high-bandwidth, short-range communication like Wi-Fi. In modern Wi-Fi standards, we use multi-carrier modulation in the form of orthogonal frequency division multiplexing, or OFDM. According to their lawyer in a 2009 patent dispute, CSIRO did not invent Wi-Fi, but it did invent the best way of doing it. CSIRO scientists tested hundreds of techniques until it found a unique combination that worked at high speeds. That combination involved multi-carrier modulation, forward error-correcting, and frequency interleaving to send multiple copies of the data. This specific combination of techniques is the secret sauce the CSIRO applied for a patent for in 1992, and was granted in 1996. CSIRO didn't invent the underlying techniques, since they were already known. Frequency division multiplexing dates back to the late 1870s, when telegraph companies were trying to increase their capacity. Multi-carrier modulation was described in the 1950s. OFDM is attributed to Bell Labs employee Robert W. Chang back in 1966. Interleaving also dates back to the 1960s. Forward error correction was used when NASA sent the Mariner mission to Mars in 1968. CSIRO also wasn't the first to combine these techniques and apply them to computer communication. Harris Semiconductor sold modems to the US military using these techniques in the 1980s. Critically, the Harris modem was never patented since interleaving, modulation, and coding had been around for decades by the time Harris came along. According to testimony, Intel official Stephen Saltzman said that outside CSIRO, engineers didn't take the idea of a Wi-Fi patent using these techniques seriously. Experts at Intel had already shipped products based on OFDM with previous employers, and thought that a new patent with OFDM didn't seem credible. Regardless of the merits and the origin of the ideas, US patent #5,487,069 was granted in 1996. During the development of the 802.11a standard, CSIRO made the IEEE aware of its patent and offered to license it. Beyond that offer, CSIRO never got involved in the creation of the 802.11 standards. Dozens of companies made proposals to the various 802.11 committees, offering to submit their ideas or license their patents. CSIRO never submitted a proposal for the original 1997 standard, or any of the revisions. Despite their lack of involvement in the process and lack of licensing agreement, 802.11a, 802.11g, and later IEEE standards would go on to use OFDM and multi-carrier modulation. Years later, CSIRO used this as the basis for lawsuits against major networking and technology companies. CSIRO won settlements worth $205 million in 2009, and another $229 million in 2012. If you want more detail on the CSIRO patent fight, Joe Mullin wrote a good piece for ArsTechnica back in 2012. Mark Summerfield wrote a counter-point to Joe's article for Patentology, looking at what the CSIRO patent did and didn't cover. The truth is a messy thing. In Wi-Fi's case, success truly did have many fathers. 802.11 Timeline
Footnotes:1 - ALOHAnet used 100 KHz channels, operating at 9600 baud on the 407 and 413 MHz UHF frequencies. It originally connected seven computers across four islands, which communicated wirelessly with a central computer in a star network topology. 2 - AT&T would go on to buy NCR in 1991, only to spin off the remnants of the division as NCR and Lucent by 1996. Sources and Further Reading
[link] [comments]  |
| Moving VMs from one data center to another while keeping the same IP addresses Posted: 30 Sep 2020 08:16 AM PDT Hello, we are reducing our data center footprint and have the following wish list. The reason we want to keep the same IPs (if possible) is that it will reduce the risk of application errors because IP addresses are hardcoded. I'm starting to gather information on whether the steps below will be possible, and the best approach given what's in play. We plan to do the following (if we can make it work):
Facts about our network
[link] [comments]  |
| Question about monitoring fan inlet temperature on Cisco 3850. Posted: 30 Sep 2020 05:20 AM PDT My goal is to monitor the inlet temperature of a Cisco 3850 fan and have the switch notify me if the temperature goes over X degrees. I have many remote locations (50+) would like to take advantage of the temperature monitoring already inside my Cisco gear. It doesn't appear that I can adjust the temperature thresholds for GREEN, YELLOW, and RED from the "show environment temp status" command. If I could then temperature alerts would show up in Solarwinds. Correct me if I am wrong, but I believe these values are hard set. I think that there might be a way to do this with Cisco EEM (Embedded Event Manager). But I pretty new to this feature and I am not sure how to implement this. The fan inlet temperature seems to be what I should be watching. Has anyone solved the problem of monitoring room temperature using the existing Cisco gear? [link] [comments]  |
| Posted: 30 Sep 2020 10:43 AM PDT Hello, I am tasked with helping retrofit/modernize/upgrade a small business network and need some help with hardware recommendations and/or resources for best practices, keeping in mind that the needs of this organization are pretty minimal and I'd love to keep it as simple as possible. Right now, there are about 18 workstations, and a handful of printers, all wired. They are running a modem/router combo from the ISP and dumb 48 port switch. There is a single fileserver running Windows 2000 Server (!) and all of the Workstations are running Windows versions XP through 10. I'd like to get a proper security device, replace all pre-Windows 10 Workstations and replace the server. They do have a Windows 2016 Essentials server (Dell PowerEdge T630) that is sitting unopened in a box. I'd like to do this as efficiently as possible. I do not have a set budget, but would love to keep it under, say $10K while also keeping in mind that the needs of this organization will, in all likelihood never need to grow much in number of users or current needs. Thanks for your suggestions. [link] [comments]  |
| Posted: 30 Sep 2020 12:26 PM PDT So far, I mostly worked with Aruba switches, but now I need to configure two Dell S4112-ON Switches for the first time. The Dell switches are supposed to be the core switches in the network, and should do some routing in the future. Therefore, my plan was to stack those two switches using the QSFP interfaces. However, as I went through some config guides, I found out that those switches are running on OS10 operating system, and according to a Dell forum, OS10 doesn't support stacking (which is absolutely ridiculous for an enterprise switch in my opinion). Now, my question is: what's the best practice for a setup with two switches that are supposed to work as router without stacking? [link] [comments]  |
| Posted: 30 Sep 2020 01:00 PM PDT Preemptive apologies for such a (potentially) novice or silly question. I'm requesting my first ASN from ARIN and curious how others have chosen the NAME for their ASN. Is there any sort of nomenclature you follow? I'm assuming it's something I can't change later, so I'd rather not pick something silly I regret later. Does the naming really matter? [link] [comments]  |
| Optimum Wireless Configuration in a MDU Posted: 30 Sep 2020 10:35 AM PDT Curious of everyone's thoughts on optimum wireless configuration in a MDU type environment. We are beginning to run into some issues (of our own creation). I got to reading this Cambium application document and it actually highlights our current configuration and some of the pitfalls of that. Currently we have a unique SSIDs for every unit (actually two) very much like a typical residential ISP CPE device (only we are strictly using them as APs). In some cases the APs are powered locally which can lead to an issue where Layer 1 fails and clients are connecting to an AP that is still powered up but has zero network connectivity. Or the AP goes down they can't see "their' unit any longer (even though the access passphrase is standard across the network it's just the annoyance of generating the support ticket and telling them to connect to their neighbor using the same passphrase). The other bigger issue, over 10,000 APs in production and less than 25 are centrally managed. So there's that. Now I'm trying to push to go to common SSID, centrally managed with the ability to ad hoc custom SSIDs on the fly but I was looking at how Cambium suggested using dynamic VLANs and thought that's another way. Anyone else have any clever design ideas? For the record, our current wireless vendors are Mikrotik and Cambium (we've tried Ruckus Unleashed and UniFi and didn't like the price versus performance) and I have a bit of a love hate relationship with Cambium dating back to the Motorola Canopy days since they were the defacto leader in many industries I've worked in (public saftey communicaitons, oil/gas, WISP). [link] [comments]  |
| Question about DHCPOFFER through a Relay Posted: 30 Sep 2020 01:50 AM PDT Question for you... Is the source IP address (in the IP header) of a relayed DHCPOFFER specified in any standard/RFC? I have seen platforms where:
FZ [link] [comments]  |
| Posted: 30 Sep 2020 07:40 AM PDT Im a student and very early in my education, so bear with me if i sound like a newbie. I have 2 clients on 2 different LAN's connected through a WAN, i've configured my cisco 1941 routers and switches, and everything seems to be working as expected, im able to ping and tracert without any issues. On each of my clients i have installed 2 VM's in Hyper V, im using virtual switches, installed as external. I can ping from the LAN-1 VM to the physical LAN-2 client and vice versa just fine, but for some odd reason i cant ping from VM to VM, it tells me "destination host can't be reached" etc. I've been trying to fix the issue by myself today for many hours, trying to reinstall hyper-v, the virtual switches, upgradig one of the clients to a more recent windows version etc, no fix so far. Could anyone give me a few tips? Thanks Edit: i have disabled the firewall and enabled file and printer sharing (IMCPv4) as well, so ping should be possible. [link] [comments]  |
| IOS-XR Show Commands with Regex? Posted: 30 Sep 2020 07:39 AM PDT Hey all. I have tried googling this and can't find an answer. And I refuse to believe you cannot do this with IOS-XR. So, if I wanted to pipe out any show command using the formal argument, and if the last number is a 0, 1 or a 2, it will output EVERYTHING that has that number within the include portion. It's best if i show an example as it's harder to explain. If I did the following: sh run formal | i TenGigE0/5/0/1 ...and I JUST wanted to see everything configured for that interface (IGMP, multicast, etc), it will spit out 0/5/0/1, 0/5/0/11, 0/5/0/12, 0/5/0/13..etc I've tried using a $ at the end of it. I tried wrapping it in quotes. I tried combining both of them. I CANNOT figure out how to output just the one interface without the OS spitting out all of the other ones that match that include statement. This has to exist, right? Can someone let me know how to do this? Thanks [link] [comments]  |
| Watchguard IPSec VPN default parameter Posted: 30 Sep 2020 06:18 AM PDT Hi there, I have half functional IPSec VPN between a Checkpoint (our side) and a Watchguard FW (customer). Tunnels are up and traffic flows for one of two customer side subnets. However nothing going through the tunnel from the other customer subnet. I suspect that the watchguard might be set on one tunnel per gateway while it's on one tunnel per subnet on our side. Unfortunately I can't get any info from the customer. Does anyone here know if the default for a Watchguard is one tunnel per gateway? [link] [comments]  |
| Posted: 30 Sep 2020 03:58 PM PDT Im still learning networking and im wondering how to setup a vrrp between two adtran routers on gig eths? [link] [comments]  |
| Posted: 30 Sep 2020 07:30 AM PDT After the update, the client defaults to putting the domain prefix before the username, which isn't how we have it setup to authenticate. Does anyone know what to edit after the fact so that the domainprefix\username is trimmed off? [link] [comments]  |
| Best Practice for Deploying a Wireguard Server on Network Posted: 30 Sep 2020 12:59 PM PDT I've got a cloud server that I'm connected to that all the clients on my LAN need to be able to access. I'm curious what the best practices would be for the network design (not the Wireguard stuff, I've got that covered). The Wireguard server is sitting inside my LAN (behind NAT):
I'm using a Unifi USG for the router on my LAN and the Cloud Server is just a single public IP address. Looking forward to hearing from you guys! [link] [comments]  |
| Posted: 30 Sep 2020 12:49 PM PDT I have a client that wants to set up dual networks in his home office of 10 users. It includes a windows server (non-domain) solely as a file share and QB database host. The purpose is to implement a backup for when the primary ISP has an outage (Spectrum). Previously there was a router that was capable of dual WAN with automatic switchover, but it never really worked properly and they were left to physically moving the switch cable from the WAN port designated for Spectrum to the WAN port designated for DLS/PPPoE. Well now that we upgraded the router to eEro Pro, it turns out that eEro will not support DSL. He's very happy with the eEro performance, but of course, we are looking for solutions for the backup DSL service, right now next time there is a Spectrum outage they have no options but to wait until Spectrum addresses the issue. I've looked at the Google Mesh, which does support DSL but does not support ethernet as a backbone. He theorizes that if we have machines with dual NIC's and a separate WiFi system altogether dedicated to DSL we will have a seamless switchover of ISP's. While my gut tells me there are easier ways to do this, he is very much married to his idea. He is very technical as he comes from a computer science background, so at the same time, I want to make this work for him. We are on the verge of replacing all the machines, so I would like to have a strong grasp on whether or not this will work before we order new machines with the dual NIC's. Has anyone else seen or implemented this use case in the real world? If so, is there any special configuration or software requirements, or additional hardware besides the extra NIC? How about once the primary WAN is restored, how do we automate the switchback? Should we be concerned about file corruption on the packet level during any switchover? Does anyone have any other ideas that I can represent that would work just as well that he may consider? I'm sure there are other questions I don't know to ask. If there are more appropriates subs I should be posting this to, please send me a pm. Thank you all for your expertise. [link] [comments]  |
| Posted: 30 Sep 2020 12:36 PM PDT Hi guys, I'm at a new position(Network Engineer) at a new job, for starting I'll be doing documentation to fill the gaps in the department. I would like to ask if you have a template to documentation for the networking stuff that work for you guys. I have in mind something like this is service "x" that have this "normal behavior" if different from "normal behavior" try step A, if still failing try step B if still failing try step C if still failing call to this escalation list Thanks in advance! [link] [comments]  |
| Is there a better way to move a large file (image) from one network share to another? Posted: 30 Sep 2020 08:17 AM PDT I am trying to move a large image 30gb atm (with more on the way) from one share to another. Both are at our companies network maybe different servers. I don't recall if me copy/pasting from one to the other adds a middle man to the time? Its going like 1.5MBs max atm and was wondering if there was a way to remove myself from the middle (if its even effecting anything). I dont have any control over the network but if its caching or generally slowing down due to my methods like like to know, I am working from home and VPNing in so I know stuff sent from my machine to the network is this slow, but dont think network to network should be this slow imo. Thanks [link] [comments]  |
| How does ARP work over wireless if broadcast traffic is trimmed? Posted: 30 Sep 2020 11:58 AM PDT Hi everyone, So my current understanding is that building very large wireless subnets in the modern world (20/21-bit netmasks) is ok because wireless systems can trim broadcast traffic. So my question is: how does ARP work over wireless? Or any other piece of networking that still relies on broadcast data? How these systems decide which broadcast traffic can so easily be dropped? Thanks! [link] [comments]  |
| IOS-XE RESTCONF Interface Call Question Posted: 30 Sep 2020 11:05 AM PDT Hey all, I'm having this issue with making REST GET calls. I asked this question on the Cisco forums but go not reply. Thought I'd try here before firing up a question to TAC. When I make a call in Postman or Python to this device, it works fine: https://host/restconf/data/ietf-interfaces:interfaces/ { "name": "FiveGigabitEthernet1/0/1", "type": "iana-if-type:ethernetCsmacd", "enabled": true, "ietf-ip:ipv4": {}, "ietf-ip:ipv6": {} }, { "name": "FiveGigabitEthernet1/0/10", "type": "iana-if-type:ethernetCsmacd", "enabled": true, "ietf-ip:ipv4": {}, "ietf-ip:ipv6": {} }, ... ... { "name": "Vlan219", "type": "iana-if-type:l3ipvlan", "enabled": true, "ietf-ip:ipv4": { "address": [ { "ip": "10.46.219.60", "netmask": "255.255.255.128" } ] }, When I modify the REST URI to focus on a specific VLAN interface, it works fine too: https://host/restconf/data/ietf-interfaces:interfaces/interface=Vlan219 { "ietf-interfaces:interface": { "name": "Vlan219", "type": "iana-if-type:l3ipvlan", "enabled": true, "ietf-ip:ipv4": { "address": [ { "ip": "10.46.219.60", "netmask": "255.255.255.128" } ] }, "ietf-ip:ipv6": {} } } However, if I want to make a GET call to a specific physical interface, it doesn't work for some reason: https://host/restconf/data/ietf-interfaces:interfaces/interface=FiveGigabitEthernet1/0/1 { "errors": { "error": [ { "error-message": "uri keypath not found", "error-tag": "invalid-value", "error-type": "application" } ] } } The URI is calling the very first Fi1/0/1 interface that you saw in the very top output. Am I calling the interface incorrectly trying to get its output? What am I doing wrong here? [link] [comments]  |
| VPN with Digital certificate enrollment question Posted: 30 Sep 2020 03:49 AM PDT Greetings everyone, I am learning Digital certificates on the ASA. My question would be whats the difference between "enrollment self" and "enrollment terminal" Now obviously with "enrollment self" the ASA is generating its own self signed Certificate I tought that if I give out the "enrollment terminal" i would be able to import an existing certificate via pasting its "crypto ca certificate chain" into the console. But asap I give out: conf t crypto ca trustpoint Our_New_CA what happens is that the ASA does not promts me to give a copy-paste input of an existing key chain, it just gives me the following text: Certificate Request follows: -----BEGIN CERTIFICATE REQUEST----- MIICljCCAX4CAQAwGjEYMBYGCSqGSIb3DQEJAhYJUHJpbWFyeUZXMIIBIjANBgkq hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjJgmV3GYrP21UJoQ2u0gOdD4H/fC0Q/Y Q7vjg/8HT9CiVw9m0SN9RTVga8gnuqf1JjCQZIPRwtwowq1WImIFN6NMJPjlTNRM jkMI0lrG31/iR5koBBx9m/+3a9tQRFThETpkTrIzYAJGLQ5zZHS1x6r37+EbC+ui UoVH7SxETOj+0MYT4WjwpvNRlttcdXUin1sCJUKUrZIVCL3rYAaogoXhOPAb99is ZNIa2566137OzLvEuqZu/G0EXtVtdWjyrcGpEnbfosU2EVA4ZJkHdHyTbFnsAuvI jARmVzIkhCwreH47lIT1Q7Cw7ckVoOeBjf6d8u2pzwE8H6vUfT++jQIDAQABoDcw NQYJKoZIhvcNAQkOMSgwJjAOBgNVHQ8BAf8EBAMCBaAwFAYDVR0RBA0wC4IJUHJp bWFyeUZXMA0GCSqGSIb3DQEBBQUAA4IBAQA2RM2UlU2wyfC3dhPYmcUfiYLMHqYu MKT05T12PzXNwxyt/yQ0XguOTA3x8bEBQnTQMJVgacUXMKkTjG5Wt9dSWabq2E/C F8oKSAYYOh3+a/24SN+/DorLoqXwNz+Gfp48AKLJAOaouA1XG9wX5gczltnhA7eI nHcCa0Ob4UPY8GVNQDodq3/uZvQA9beh1fFC2lyM3dXCNZhmgijJk49koQL9mW+6 X5utUAKV1xWIWoZmbMCxOJ1u0wtvJI31d/hSMF2nYYWuaR2EtkQFF++/n6L6s356 1s3cGL/KTzSjPUM6MkRL1vOR16ufCSkP7lddm4Rh8z4uTNCE5hTOkqtV -----END CERTIFICATE REQUEST----- Redisplay enrollment request? [yes/no]: no What did I do wrong here? Is it how this intended how this is supposed to be working? [link] [comments]  |
| Posted: 30 Sep 2020 09:38 AM PDT Is there a wifi vendor who can handle having multiple VLANs per SSID where the VLAN is assigned based on which PSK is used? Some Cisco WLCs can apparently handle this, but only ones that allow more than 16 WLAN profiles. Yes, I know that I can do that on pretty much anybody's wifi if I can use Radius for dynamic VLAN assignment, but in this case that is not an option. [link] [comments]  |
| Posted: 30 Sep 2020 04:39 AM PDT I'm looking to replace my remote site Sonicwalls with something that offers central management and reporting, I really like Ubiquity as I use their wifi and switches, but many tell me to stay away as they're not enterprise gear. I know about Meraki, but it's too pricey, does pfsense offer something like Unifi perhaps? I really just need a vpn tunnel to my data center, qos for phone and seperate lan port for public guest network that would use PBR to send the vpn traffic back to the data center for the lan1 port, and everything else like phones and public access over the local wan port. Suggestions? [link] [comments]  |
| Posted: 30 Sep 2020 07:35 AM PDT Hi all. I've been working with Networking (professionally) for 7 years now. I have a college degree in the field of Networking and IT-Security. However, I feel just during these 7 years, that things have changed so drastically. From going from CLI to GUI. From going from MPLS to SD-WAN. From going from WiFi to 4G/5G. Work is being outsourced to India. Things are just so much more automated now. Every day just feels like there is less and less need for a network engineer. I really can't see so much of a future in this. In the meantime I really love what I do, but its hard, when you feel its not worth it. I make quite good money. I cant see myself to buying an apartment etc. just cause I feel my job is so... worthless in a sense, even though I support 100+ locations, wireless network for 2000+ users etc. I've been responsible for migrations from on-prem solutions of Wi-Fi to Cloud, from MPLS to SD-WAN etc. What do you guys feel is for us in the future? Should I try to go to a ISP and get a management role? Am I just in the wrong field? I can take changes, but when they change so quick and fast, its just quite depressing to be honest. Does anyone agree? [link] [comments]  |
| Does ARP suppression without SVI on Spine-Leaf Posted: 29 Sep 2020 08:07 PM PDT Does ARP suppression works on cisco nexus switches if we don't have any SVI or anycast gateway on leaf ? [link] [comments]  |
| You are subscribed to email updates from Enterprise Networking Design, Support, and Discussion.. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment