NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
GS1xxE and their PoE equivalents. Getting them an IP using DHCP on a specific vlan.
Hello to anyone taking the time to read this. I have close to a dozen netgear GS1xxE switches at my home and various family member's homes by now and swear by the things. Vlan tagging is a must for our various setups and these switches haven't disapointed yet. However , when it comes to configuring them, the fact one is incapable of selecting the vlan on which the things do their DHCP negotiating forces me to use fixed IP's. In essence this isn't all that bad. But adding this to the firmware isn't something unreasonable to ask I would think. http://i.imgur.com/JZEvBx4.png http://i.imgur.com/p9evrYY.png Thanks in advance for taking the time to reply. If you also think this slight oversight should be rectified please do reply.Feature Request: Display Port Description to other relivant pages displaying other port info
Under System -> Management -> Port Status you are able to add a port description. It would be very useful to see this descrioption displayed throughout the interface while looking at the ports such as while defining VLAN's, System -> Monitoring -> Port Statisitcs, and others.The IGMP Snooping Static Router Port setting on GS108PEv3
The IGMP Snooping Static Router Port setting on GS105PE was originally not available on that model, but it was later added after a request to add it and was provided by updating the firmware. Our engineers will now review if it will be possible to add it on the GS108PEv3 and we need to log it as a request however we will not be able provide you an estimated time of release. We will have to wait and see it on the future firmware update of the product.tcpdump does not decode Prism radio header (wireless interface)
Please update the version of tcpdump that's included in the WAC720 and WAC510 access point (and other WiFi routers/access points). The version currently installed relies on a buggy libpcap that incorrectly processes the Prism radio header. As a result, running a packet capture on the radio interface results on undecodable frames. Please note that the problem is in the pcap library, not tcpdump (the pcap library is static linked into tcpdump). This is the version of tcpdump currently installed: # tcpdump -V tcpdump version 3.9.8 libpcap version 1.1.1 This is what happens when the current version of tcpdump is run on a radio interface (notice the decodes are useless): # tcpdump -i mon0 -n tcpdump: WARNING: mon0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on mon0, link-type PRISM_HEADER (802.11 plus Prism header), capture size 96 bytes 16:25:39.368772 [|802.11] 16:25:39.395357 [|802.11] 16:25:39.396201 [|802.11] 16:25:39.408759 [|802.11] 16:25:39.415976 [|802.11] 16:25:39.416788 [|802.11] 16:25:39.448778 [|802.11] This is an updated version of tcpdump: # /tmp/tcpdump -V tcpdump version 4.7.4 libpcap version 1.7.3 This is what happens if I use an updated version of tcpdump (notice the decodes are sensible): # /tmp/tcpdump -i mon0 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on mon0, link-type PRISM_HEADER (802.11 plus Prism header), capture size 262144 bytes 16:26:44.309540 Probe Request (Carioca_5G) [6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 Mbit] 16:26:44.319537 Probe Request (Carioca_5G) [6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 Mbit] 16:26:49.047216 Probe Request () [6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 Mbit] 16:26:49.048028 Acknowledgment RA:9c:3d:cf:ea:67:69 16:26:49.087172 Probe Request () [6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 Mbit] 16:26:49.088047 Acknowledgment RA:9c:3d:cf:ea:67:69 16:26:49.127191 Probe Request () [6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0 Mbit] 16:26:49.127972 Acknowledgment RA:9c:3d:cf:ea:67:69 You can download the updated version of tcpdump using this command: curl -k -o /tmp/tcpdump https://raw.githubusercontent.com/andrew-d/static-binaries/master/binaries/linux/arm/tcpdumpProsafe M4100-26G TLS 1.2 Not Available and Weak Cipher Suites
Our vulnerability scanning shows that our switch's management over HTTPS only has TLS 1.0. In today's world, everything should be at TLS 1.2, so it is causing our vulnerability scanning to report it as a high vulnerability. We have the latest firmware (10.0.2.20), and have recently re-issued the certificates, so I'm not sure what to do. We have the ability to create self-signed certs externally to the switch, but it doesn't seem to allow us to use them. I can only see how to let the switch generate its own certificates. It is also reporting that it is using weak cipher suites. How can I ge these upgraded?
WN203 SNMP settings
I have several WN203 APs and I have been very happy with them. I recently started using NMS300 to monitor my network and noticed that there does not appear to be any way to configure SNMP location and contact information for the WN203 using the GUI or the command line. I would like to see this capability added in a future firmware release but given the limited number of previous updates for this device I don't think that will happen. If no firmware updates are forthcoming, I may just accelerate my plans to migrate to WAC720 or WAC730.