Book Image

Python Network Programming

By : Abhishek Ratan, Eric Chou, Pradeeban Kathiravelu, Dr. M. O. Faruque Sarker
Book Image

Python Network Programming

By: Abhishek Ratan, Eric Chou, Pradeeban Kathiravelu, Dr. M. O. Faruque Sarker

Overview of this book

This Learning Path highlights major aspects of Python network programming such as writing simple networking clients, creating and deploying SDN and NFV systems, and extending your network with Mininet. You’ll also learn how to automate legacy and the latest network devices. As you progress through the chapters, you’ll use Python for DevOps and open source tools to test, secure, and analyze your network. Toward the end, you'll develop client-side applications, such as web API clients, email clients, SSH, and FTP, using socket programming. By the end of this Learning Path, you will have learned how to analyze a network's security vulnerabilities using advanced network packet capture and analysis techniques. This Learning Path includes content from the following Packt products: • Practical Network Automation by Abhishek Ratan • Mastering Python Networking by Eric Chou • Python Network Programming Cookbook, Second Edition by Pradeeban Kathiravelu, Dr. M. O. Faruque Sarker
Table of Contents (30 chapters)
Title Page
Copyright
About Packt
Contributors
Preface
Index

Vendor-neutral libraries


There are several excellent efforts of vendor-neutral libraries such as Netmiko (https://github.com/ktbyers/netmiko) and NAPALM (https://github.com/napalm-automation/napalm). Because these libraries do not come natively from the device vendor, they are sometimes a step slower to support the latest platform or features. However, because the libraries are vendor-neutral, if you do not like vendor lock-in for your tools, then these libraries are a good choice. Another benefit of using these libraries is the fact that they are normally open source, so you can contribute back upstream for new features and bug fixes. 

 

 

On the other hand, because these libraries are community supported, they are not necessarily the ideal fit if you need to rely on somebody else to fix bugs or implement new features. If you have a relatively small team that still needs to comply with certain service-level assurances for your tools, you might be better off using a vendor-backed library.