From 014d32cec1a8eadf96d1042df3fc75fdc51f35ff Mon Sep 17 00:00:00 2001
From: nick n <39005454+inphobia@users.noreply.github.com>
Date: Thu, 31 Jan 2019 02:14:37 +0100
Subject: [PATCH] device info would be handy too

for snmp::info device information always comes in handy. add it to the issue template.

basic info which helps: vendor, model & os plus an snmpwalk of the system leaf of snmpv2-mib.
---
 .github/issue_template.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.github/issue_template.md b/.github/issue_template.md
index f4f6675a..65ab66c0 100644
--- a/.github/issue_template.md
+++ b/.github/issue_template.md
@@ -25,6 +25,15 @@
 <!--- How has this issue affected you? What are you trying to accomplish? -->
 <!--- Providing context helps us come up with a solution that is most useful in the real world -->
 
+## Your Device
+<!--- Some basic info about your device will help out pinpointing the issue more easily -->
+<!--- also, snmpwalk output of the following oid helps out a lot: .1.3.6.1.2.1.1 -->
+* Vendor:
+* Device Model:
+* Operating System Version:
+* Snmpwalk output of .1.3.6.1.2.1.1:
+
+
 ## Your Environment
 <!--- Include as many relevant details about the environment you experienced the bug in -->
 * SNMP::Info version used: