Please add DHCP reservation feature to switch M4300
As the core of LAN, L3 switch really needs DHCP reservation, which is indispensable. It's well-known that switch is the most stable hardware in network. It's more likely for a bare-metal server goes down than a switch does. If M4300 has DHCP reservation feature, we can transfer the DHCP server from a PC to the switch, which could enhance the stability and convenience for management of the network significantly. At present, in "System-Services-DHCP Pool Configuration", I have to create ONE "manual_pool" for EACH MAC-IP mapping. It's REALLY tedious and boring. I think you can add at least two features to improve the situation. 1. Re-design "System-Services-DHCP Pool Configuration-Type of binding-manual" in the web-gui, and allow people to add multiple MAC-IP-GATEWAY-DNS-NETBIOS mappings to one 'manual_pool'. For example: https://i.loli.net/2020/04/03/lotb2NgSHzwpqIL.png In this way, users can easily add or remove records by clicking the '+' or '-' button ahead of each line. 2. Add a new command to load an external text-based datebase which contains all the information stated above from a USB flash drive or tftp server. In this way, users can create and modify the text-based database using their favorite text-editor and then upload it to the switch. It would be great if the developers can add the features I stated above to M4300. Thanks a lot.Letter of Volatility
Please ensure NTGR does publish the Letter of Volatility (LOV) along with the product support download pages. We see that requests for LOV are taking reasonable bandwidth in the community support, temporary file downloads will be enabled with valid for a few days only. This makes the replies virtually useless, because the download is no longer available. So we see requests for the same product LOV again, or we get new posts. All this can be avoided... Thank you for consideration! Regards, -KurtM4100: scheduled config save via encrypted connection (needs telnet up to now..)
Hello everybody, we would like to use NMS300 to save the config of our 40 Netgear Switches (M4100 series, different models) automatically every night, but this requires telnet to be enabled on all switches (confirmed by Netgear Expert Bruce_G: https://community.netgear.com/t5/Managed-Switches/NMS300-config-backup-with-telnet-disabled/m-p/1161992/thread-id/2682#M2753) I think that transmitting a password for administrative access in cleartext over the network isn't best practice, especially for a product which claims to be enterprise ready. Would you please implement an option for a scheduled config saving and other mass actions like firmware update for all switches via an encrypted conection? It should be possible to disable telnet on the switches without disabling any funcionality (apart from logging in via telnet of course..) ;-) Thanks in advance! Kind Regards Christoph PeusFeature Request: Disable/remove automatic port descriptions
Request: Either create a way to stop network profiles from overriding manual switch port descriptions or remove the feature. Reason for request: We use the netgear switch plugin for our control system (Q-Sys). Using the plugin and port descriptions we are able to quickly bounce devices and/or power cycle POE devices when needed. Without reliable port descriptions, this becomes a much longer and involved process. We have over 30 40 port switches in our environment plus even more of a mix smaller M4260's. Not all of our admins have detailed information on switch configs. Background: This feature was added to the firmware in version 13.0.5.20. Expected behavior: Option 1: If a manual port description is applied to a port, reapplying a network profile will not overwrite the description. Option 2: Add an option in the network profiles that turns that feature off for the profile. Option 3: Remove the automatic generation of port descriptions altogether.Management VLAN Support on Plus Series
I have an issue where if I create a tagged VLAN on a JGS516PE, GS108PE, & JGS524PE switch on the uplink port then it will pull an IP from that tagged VLAN as its management VLAN. e.g. I have VLAN1 - 192.168.1.0/24 - untagged and VLAN100 - 192.168.100.0/24 - tagged then the switch will grab 192.168.100.25 as a management VLAN. I created a ticket with Netgear support on this issue and I was told that the switch was sending out DHCP requests for each VLAN and which ever it recieved back first it would take and ignore the rest. The solution was to assign a static IP since the Plus series doesn't support management VLAN changes. I believe assigning a static is a patch to an issue that shouldn't exist. I know a change in the way that we do the initial setup will allow us to know which static we need to use before we deploy the switch with tagging but it has been an issue before and we had to create inter-VLAN routing to be able to get back to the switch and manage it.
Limit bandwidth on port - confused
Hi I have a guest house and I've created a vlan for the guests there, using only port number 24. I'd like to limit the bandwidth from that port to 100 Mbps but get confused by instructions in the manual and in the web interface. At one place it says I should define the "Interface Shaping Rate" to a number between 16–16384 (manual) and at the other is says between 1-100 (the web interface). I'm doing something wrong. Can you help me out here?
