NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
M4300 (GSM4352PS V1) : can't get kernel image
Hi Netgear Users and Administrators, I have a little problem with my M4300 GSM4352PS V1. There's possibility that image2 is broken. Device is actually booting from image2. On the console I see that can't boot from image and i see "ERROR: can't get kernel image". I supose that the image1 is a good conditional. Best Redgards PawelNetgear GS316EP reports as GS108EV3 after factory reset
We have an unused Netgear GS316EP 16 port switch. During troubleshooting we were asked to factory reset the switch. After factory reset it reverted to it's default IP address. When you connect via web to the switch via it's default IP address, the switch now says it is a GS108Ev3 8 port switch. The configuration utility is completely different from before. I downloaded the newest firmware but have not yet tried to install. The installation of firmware is even very different between the different models and I was concerned that the incorrect firmware (wrong model) might brick the switch. How can we get our 16 port GS316EP back? (We need all 16 ports not just 8)GS110TP hardware version?
Hello, I have the GS110TP V1H1 switch (I'm assuming I have the V1 hardware?). I am trying to find the correct firmware to use. When I check the support page for the GS110TP, it lists firmware as 5.0.1.10 (Located here GS110TP Page) I noticed something weird.. On the back of the switch, there is a sticker that shows the firmware being newer than what's on the GS110TP page?: HW: GS110TP SW: 5.0.3.5 Does anyone know how I can confirm which firmware I should be using, and where I can find the most current firmware? Thanks.Auto Voice VLAN setup
We are looking to isolate our VoIP traffic to its own VLAN. For a number of reasons, we'd like this to happen without needing to configure each phone. It looks like Netgear switches support this. Unfortunately, the documentation is scattered and in many cases outdated. I'm hoping some folks here can show me where we're going wrong. Goals: Voice VLAN = 88. Ports 1-44 set to untagged VLAN 1 and VLAN 88. Default to 1 unless MAC address prefix matches a VoIP device. Ports 45-46 are for router for Voice-VLAN and has no access to VLAN 1. Ports 47-48 are for router normal VLAN (1) and has no access to VLAN 88. Ports 49-52 are uplinks and should carry traffic for both VLANs. The phone should be able to operate in pass-through mode, and devices behind them should default to VLAN 1 as they normally would. Currently I am facing two issues: When I plug in a phone with matching MAC prefix, it is not being pushed to VLAN 88. I'm unable to outright disable Voice-VLAN (88) on ports 47-48. I'll add some screenshots of the current config in a follow-up post. Hopefully some kind network admin will take a look and be able to spot where I'm going wrong.Confusing typos in HTTPS certificate upload page
The MS510TXUP Smart Switch has some confusing typos on the page used to upload HTTPS certificates whilst on the latest firmware version 1.1.0.9 (and all versions before it). The user is presented with the following options: "SSL Trusted Root Certificate PEM File" should be used for the X.509 Public Certificate PEM File, and "SSL Server Certificate PEM File" should be used for the X.509 Certificate Private Key PEM File. As my device is out of warranty, I could not find any way to make Netgear aware of this issue. If anyone from Netgear sees this, please the typo be resolved? Also, TFTP is insecure and should not be used to transfer private key files. Please could a secure alternative be implemented?M4300 Stack (GSM4253PB) - Firmware upgrade causing PABX failure ?
Hi. We have a stack of 4 GSM4253PB switches with firmware version 12.0.11.15 and yesterday we planned an upgrade to version 12.0.19.4, going through the versions : 12.0.11.15 -> 12.0.13.8 12.0.13.8 -> 12.0.15.7 12.0.15.7 -> 12.0.17.6 12.0.17.6 -> 12.0.19.4 At each version upgrade, we carried out a complete stack update (simultaneous restart of the stack). The firmware was copied to the stack via the web console (http upgrade) on the inactive image with Stack Firmware Auto Upgrade enabled. On two occasions, the firmware copy had to be restarted because it was frozen. After the last reboot of the stack, the master changed and the LAG of 2 cables uplinking toward the core stack was unstable (one member had been changed from 1/0/51 to 3/0/51, a port on which there was no cable...). After correcting these two incidents, I realised that the VLAN configurations of switches 1 (master) and 4 (member) had been lost, causing a network loop. This was quickly corrected. Subsequently, the OmniPCX PBX connected directly to this stack failed: the CPU card was blinking orange and the LAN ports were unreachable. According to Alcatel-Lucent technical support, a ‘network anomaly’ caused the CPU card to flash its firmware (!!!) and rendered the PBX inoperable. This card controls power-up and the other ports are no longer powered => no diag possible. Do you think this can really happen ? Is this a plausible cause of the failure ? Can you imagine what had possibily went so wrong that this PABX stopped functionning because of a switching stack firmware upgrade ? Any help or insight would be appreciated. I hope this case is clear enough. Regards.
