NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
bug
24 TopicsNeed instructions to update FVS318Gv2 firmware beyond 4.3.3.6
Hi. I'm looking for clear ("for laymen") instructions to upgrade my FVS318Gv2 firmware past the v4.3.3-6 update which blocks subsequent upgrades through the GUI. A firewall without bug fixes is like a door without lock - pointless. For those who don't know, the v4.3.3-6 update of the FVS318Gv2 had apparently a bug which somehow disabled further firmware upgrading through the GUI: Once this firmware installed, the firewall errors out after a couple seconds on any subsequent upgrade attempt. Meaning that we need to somehow force-feed the next version (4.3.3.8 or later) into the firewall so upgrades resume working. How can we do this? It's a problem Netgear created, and I expect Netgear to help us solve it. So, what are my options? I definitely don't have the time to go through the "have you tried to switch it off and back on again" routine with some helpdesk drone in Pakistan, and apparently that's the only support option offered. For $50, too... Is there another support option I missed? E-mail would be great. What other means are there to fix this problem? Yes, I did find a thread mentioning using telnet and TFTP servers, but I also read there is a danger of bricking my firewall, and that Netgear doesn't condone accessing the firewall using telnet. So, besides the technical difficulty, it's also dangerous... Can somebody please tell me how high are the chances of bricking our firewall, and if it happens, what would be my options (besides rushing out to buy a new one - of a different brand)? Anyway, I would need more explicit instructions please. Specifically, where do I find a "TFTP server" software (which won't wreck my business computers!)? I can manage a telnet session, but that's about all. Thanks for your time.Solved15KViews1like14CommentsBUG: Cannot edit "Internet" VLAN settings (e.g. Priority, VLAN ID)
Router Firmware Version V2.0.0.74 Steps to reproduce: 1) Sign in to orbilogin.com (or whatever method) 2) Click the "Advanced" tab 3) Expand the "Advanced Setup" section in the left list, then scroll down within the list until you see "VLAN/Bridge Settings". Click "VLAN/Bridge Settings". 4) Click "Enable VLAN/Bridge group" and then "By VLAN tag group". 5) Highlight the existing/default "Internet" VLAN tag group and click "EDIT" 6) Change the VLAN ID (e.g. to 201, as I need to do for CenturyLink Fiber internet). 7) Click "APPLY" Expected results: VLAN tag group page is shown with the new settings specified above. Actual results: VLAN tag group page is shown with old settings; any changes are not respected/retained/saved. Using the exact steps above, the entire VLAN settings are disabled / not enabled. If you already have VLAN settings enabled, then the "Internet" group will simply remain in VLAN ID 10 -either way, it is uneditable. Looking for Netgear help here, as this seems to be a bug in their firmware or router settings. Also very interested if others can reproduce, or whether this is just my device.SolvedTraffic Meter Units Displayed & By Device?
TWC is saying that I have used 693+ GB this month (9/1 to 9/20) compaired to 308 for the previous month. How the heck do I convert the data reported in the traffic meter and is there a report with more detail by device available? Do you think that this is inclusive of LAN traffic? Firmware Version - V1.01.15Solved9.9KViews0likes11CommentsWLAN config changes not possible
Hi Guys, I got a problem with my R8000. At the moment its broadcasting the default configured SSID, but for security purpose I want to configure my own SSID / PSK. But this doesn't seems to be possible. When I try to save a change on the SSID / PSK Menu, it gets cancelled: This DFS-Channel cant be used because a radar gets detected. (Error message in german, I translated it, so therefore it could be, that it isnt the exact error message on a english ui) BUT: The error appears even if the second 5G-Radio isn't even turned on, so therefore this shouldnt bother. Further, the first 5G-Radio is sending on a non-DFS-Channel, so this couldnt be the problem either. For me this seems to be a bug. I'm using V1.0.3.4_1.1.2 which seems to be the latest version. kind regards, AndreasSolved8.3KViews0likes12CommentsFVS318G Telnet LAN<>WAN firewall settings not working
Hello, when logging into the router via telnet and accessing the fw / lan-wan settings, I cannot use the show function nor can I disable or enable any rules. I need this to work for an automated task that should change these parameters. It tells me that I provided too few parameters, however the show functions in the other routing virtual folders seem to work just fine without any additional arguments. Am I missing something, or is there a way to contact Netgear so that they can finally fix this and some other issues in the firmware. Or do I really have to build and flash OpenWrt and do my own, less buggy firmware? Sincerely, Benedikt7.9KViews0likes17CommentsLLDP "Operational MAU type" (802.3 TLV) is zero for GS724Tv3
Versions Model Name Boot Version Software Version B5.1.1.1 5.4.2.19 I've enabled the optional LLDP TLVs on all my ports. When I receive the 802.3 organizationally specific TLV subtype 1, the oerational MAU type is zero. What the operational MAU type should be is 30. The RFC for this is: dot3MauType1000BaseTFD OBJECT-IDENTITY STATUS current DESCRIPTION "Four-pair Category 5 UTP, full duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 40" ::= { dot3MauType 30 } When I check on the web interface, it shows 1000mbit, full duplex. The switch can only do 1000-base-t on 4 pair of unshielded twisted pair. It would be handy to be able to get this information and verify that everything was as it should be. But the latest firmware (just downloaded it) gives a zero. This is the wrong answer ;-) Here's what the dump of the TLV shows: ORG SPECIFIC DUMP: 00120f: DUMP (9 bytes): 00 12 0f 01 03 00 01 00 00 You can read about this in Annex G of the 802.1AB (LLDP) spec. On my copy this spans pages 132 and 133. An OUI of 00-12-0F means it's the 802.3 TLV (as I expect). The last two bytes (octets) are the "operational MAU type". As you can see they are both zero. The only reason for them to be zero is if the type of MAU isn't listed in RFC 3636. But it is. So, it's an error for it to be zero.6.5KViews0likes11CommentsNetgear Nighthawk M1 drops LTe connection every day and requires multiple reboots
Hi there, Purchased a Nighthawk M1 (MR1100) from Telstra recently. Seems to work well in terms of speed. But a few problems including severe lack of configuration for DHCP (the only item you can configure is DHCP range - there's no fixed host mappings, or any even basic features present in almost every other device on the market. I really hope this is addressed in a future patch or Netgear advise a secret menu to access these basic features as it's really disappointing and lets the router down at the present time). However, it's by far the fastest I've ever tested. Anyway to the main problem. Every day when I come home the device is no longer providing Internet over the connected ethernet cable. I can connect to the modem admin screen fine, and it reports it's connected to the internet (reports LTE connection is fine and has been connected for over a day); however, no devices on the network can use the internet and the only way to solve it is by restarting the MR1100 multiple times eventually it starts routing traffic again. This problem does not occur on any of the other modems I've tested using the same SIM/Service so it's definitely an issue with the MR1100. Something is wrong with the software - need someone from Netgear to sort this out. Also Netgear you need to add the Nighthawk M1 to your model list as I had to assign this ticket against a random unrelated modem as your product list isn't up to date.Orbi Access Control Firmware 1.3.0.12
I just updated my Orbi Router and Satellite to the latest firmware, 1.3.0.12. I'm using Access Control to limit access to the network. I have a Tivo Mini hooked up to the ethernet port of the satellite, and it was connected and allowed to network access before the firmware update. Now when I enter access control, the Tivo Mini shows as "blocked", and even if I select the device and click "allow", it stays blocked. That's the first issue. The second issue is that it's not actually blocked (nor do I want it to be). It's able to connect to the network and access the internet just fine. I tried to block and unblock it and it didn't work. Not sure what the issue could be except a firmware bug.AirPrint and ReadyNASOS6
Hey, I've been trying to get my ReadyNAS to operate as a 'print server' for my local network, including with AirPrint functionallity. I have a Brother wifi printer (so it's not connected via USB) and have sucessfully installed the required CUPS and foomatic filter packages, and have the printer shared with my network without issue. The next issue was AirPrint. I've read all the posts in this forun where people have sucessfully got it working with pre-iOS6 clients; but have had no success with the post-6 devices. I believe I have figured out why.... The issue is Avahi, and the advertising of the printer as an AirPrint printer. Previous to iOS6, the Avahi .service file did not make use of the <subtype> directive; but since iOS6, a specific <subtype> setting is required in order for iOS to 'see' the printer. Unforunately, it is the use of the <subtype> directive in the .service file which is causing Avahi to crash on the ReadyNAS - and thus prevent the NAS from advertising the AirPrint printers to the local network. The Avahi .service file for my Brother wifi printer was created with this script: https://raw.github.com/tjfontaine/airprint-generate/master/airprint-generate.py The script spits out a valid .service file which contains everything which SHOULD be required in order to advertise the printer via mDNS/Bonjour for the iOS devices to pick up. The problem is that Avahi crashes while it is parsing any .service file which contains a <subtype> option. This can easily be reproduced if you upload a .service file created using the above script (or any other example you find with google) and run Avahi from a terminal as root. The .service file for my Brother wifi printer is: <?xml version="1.0" ?><!DOCTYPE service-group SYSTEM 'avahi-service.dtd'> <service-group> <name replace-wildcards="yes">AirPrint Brother_DCP-1610W @ %h</name> <service> <type>_ipp._tcp</type> <subtype>_universal._sub._ipp._tcp</subtype> <port>631</port> <txt-record>txtvers=1</txt-record> <txt-record>qtotal=1</txt-record> <txt-record>Transparent=T</txt-record> <txt-record>URF=none</txt-record> <txt-record>rp=printers/Brother_DCP-1610W</txt-record> <txt-record>note=Brother DCP-1610W</txt-record> <txt-record>product=(GPL Ghostscript)</txt-record> <txt-record>printer-state=3</txt-record> <txt-record>printer-type=0x80b004</txt-record> <txt-record>pdl=application/octet-stream,application/pdf,application/postscript,image/gif,image/jpeg,image/png,image/tiff,image/urf,text/html,text/plain,application/vnd.adobe-reader-postscript,application/vnd.cups-command,application/vnd.cups-pdf</txt-record> </service> </service-group> (different printers will obviously have different output from the script... but the key point of note here is the inclusion of the <subtype> directive) If the <subtype> directive is commented out, Avahi on the ReadyNAS will parse and load the file without issue (but the printer is not picked up by iOS due to the missing directive): Found user 'avahi' (UID 84) and group 'avahi' (GID 84). Successfully dropped root privileges. avahi-daemon 0.6.31 starting up. Successfully called chroot(). Successfully dropped remaining capabilities. Loading service file /services/AirPrint-Brother_DCP-1610W.service. Loading service file /services/frontview.service. Loading service file /services/nut.service. Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for mDNS. Joining LLMNR multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for LLMNR. Network interface enumeration completed. Registering new mDNS address record for 192.168.67.248 on bond0.IPv4. Registering new LLMNR address record for 192.168.67.248 on bond0.IPv4. Server startup complete. Host name is NAS.local. Local service cookie is 2760298420. All host RR's have been announced/verified : SERVER RUNNING Service "NAS" (/services/nut.service) successfully established. Service "ReadyNAS Administration on NAS" (/services/frontview.service) successfully established. Service "AirPrint Brother_DCP-1610W @ NAS" (/services/AirPrint-Brother_DCP-1610W.service) successfully established. However, with the <subtype> option present, Avahi crashed out at startup: Found user 'avahi' (UID 84) and group 'avahi' (GID 84). Successfully dropped root privileges. avahi-daemon 0.6.31 starting up. Successfully called chroot(). Successfully dropped remaining capabilities. Loading service file /services/AirPrint-Brother_DCP-1610W.service. Loading service file /services/frontview.service. Loading service file /services/nut.service. Joining mDNS multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for mDNS. Joining LLMNR multicast group on interface bond0.IPv4 with address 192.168.67.248. New relevant interface bond0.IPv4 for LLMNR. Network interface enumeration completed. Registering new mDNS address record for 192.168.67.248 on bond0.IPv4. Registering new LLMNR address record for 192.168.67.248 on bond0.IPv4. Server startup complete. Host name is NAS.local. Local service cookie is 1803852026. avahi-daemon: running [NAS.local]: entry.c:1080: avahi_server_add_service_subtype: Assertion `flags & AVAHI_PUBLISH_USE_MULTICAST || flags & AVAHI_PUBLISH_USE_WIDE_AREA' failed. I believe this is an issue related to the version of Avahi present on the ReadyNAS. Is there any chance of Netgear upgrading the version to one which doesn't contain this bug, or at the very least patch something which will cause Avahi to crash at start? I'd appreciate if anyone else can test their system to see if they get a similar problem with Avahi - just to make sure i'm not doing something completely brain-dead :) If we can get this crashing issue resolved, i'm pretty sure we can get AirPrint working again in ReadyNASOS6. Cheers.5.9KViews0likes6CommentsWN3000RPv3 Urgent Firmware Update Bug
Was already using firmware V1.0.2.50, says V1.0.2.52 is available, downloaded V1.0.2.52 img, hardwired update, and your V1.0.2.52 is bugged and thinks that it’s V1.0.2.50 still... Around in catch 22 circles the update procedure goes... Who knows what version I’m even on now, because both V1.0.2.50 and V1.0.2.52 come back as V1.0.2.50? This needs urgent attention, roll on V1.0.2.54 lol.Solved5.9KViews0likes10Comments