NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
FVS336GV3 - Decriptage de logs
Bonsoir, Je cherche à comprendre les logs que m’envoie mon Firewall FVS 336 GV3 (sous firmware 4.3.4-2). Logs pour « Wan status » et paquets supprimés « WAN to LAN » : [T**/FVS336Gv3]Mon Oct 2 21:55:38 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restarting WAN1 for IPv4 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device down: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_destroy(tp a8000000045f7e80),p a8000000031dcb00 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_walk(tp a8000000045f7e80,walker a80000000315fd00),p a8000000031dcb00 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_delete(tp a8000000045f7e80,arg 0xa800000002e06d88),p a8000000031dcb00,f 0000000000000000 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:43 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:48 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:48 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:48 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:48 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] IPsec: device unregistering: ppp1 [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] unregister_netdevice: waiting for ppp1 to become free. Usage count = 1 [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: dev_set_allmulti(master, -1) [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: dev_set_allmulti(master, -1) [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: del 01:00:5e:00:00:02 mcast address from master interface [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: del 01:00:5e:00:00:02 mcast address from master interface [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: dev_set_allmulti(master, 1) [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: dev_set_allmulti(master, 1) [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: dev_set_allmulti(master, -1) [T**/FVS336Gv3]Mon Oct 2 21:55:53 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: dev_set_allmulti(master, -1) [T**/FVS336Gv3]Mon Oct 2 21:55:57 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restart on WAN1 returns OK [T**/FVS336Gv3]Mon Oct 2 21:55:57 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restarting WAN2 for IPv4 [T**/FVS336Gv3]Mon Oct 2 21:55:57 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restart on WAN2 returns OK [T**/FVS336Gv3]Mon Oct 2 21:56:01 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restarting WAN2 for IPv4 [T**/FVS336Gv3]Mon Oct 2 21:56:01 2017((GMT+0100)) [T**/FVS336Gv3][System][NIMF] Restart on WAN2 returns OK [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: dev_set_allmulti(master, 1) [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: dev_set_allmulti(master, 1) [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.1: add 01:00:5e:00:00:02 mcast address to master interface [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] eth0.2: add 01:00:5e:00:00:02 mcast address to master interface [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_init(tp a800000004b82c80) [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_get(tp a800000004b82c80,handle 0x00000000) [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_change(tp a800000004b82c80,handle 0x00000000,tca a800000007c05a80,arg a800000002dbf950),opt a800000002b20630,p a800000004fb6380,r 0000000000000000,* rg 0x0 [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] tcindex_dump(tp a800000004b82c80,fh 0x0,skb a800000002ae4380,t a8000000029dc010),p a800000004fb6380,r 0000000000000000,b a8000000029dc038 [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] p->perfect 0000000000000000 p->h a80000000423e200 [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] HTB: quantum of class 10001 is big. Consider r2q change. [T**/FVS336Gv3]Mon Oct 2 21:57:13 2017((GMT+0100)) [T**/FVS336Gv3][Kernel][KERNEL] HTB: quantum of class 11024 is big. Consider r2q change. Ma configuration coté WAN : WAN1 : vers un modem ADSL(D-Link) pour un service Orange. WAN2 : Libre pour le moment. Pouvez-vous m'aider à comprendre ce qui se passe. D'avance merci. ING91_P01
FVS336Gv3 PPTP VPN for macOS Sierra
Hi Netgear community, One of our sites has a NETGEAR ProSafe™ Gigabit Dual WAN SSL VPN Firewall FVS336Gv3 which has PPTP Server enabled and setup with working users for Windows OS, there is 1 user that uses MAC OS. Since that 1 user upgraded their macOS to Sierra the option for PPTP has been removed (Apple reports the reason is for security). I have tried enabling SSLVPN in the firewall but have struggled to get that working. As a fallback, we are looking at 3rd party clients that can create the VPN using PPTP again. I've looked at some suggested clients (FlowVPN, VPN Tracker, user is trying TunnelBlick) but not getting very far. Ideally, we want a freeware that can do PPTP (unless there is a free SSLVPN option). Any suggestions or if you have got around this issue with macOS Sierra. Many thanks in advance.ProSafe Firewall FVS336Gv3 firmware upgrade question
Hi all, I have a quick question regarding upgrading the firmware on a FVS336Gv3. It is currently running on 4.3.3-8 and I want to upgrade it to the latest 4.3.5-3, will the settings already in the device be retained or will they get wiped from the firmware upgrade? Thanks.
FVS336Gv3 - L2TP/IPsec on Windows 10
I have a Windows Server running RRAS with PPTP. The FVS forwards this with no problem. The problem is we now need to move to L2TP. I have created this on the Windows server, and from within the LAN, a client machine (my laptop) can connect directly to the server(using the internal server name). But as soon as I go outside the network it doesn't work (using external address). We do have a site to site IP SEC VPN running between this FVS and one in another site. I hope this isn't causing the problem?? I have forwarded UDP 500, 4500, 1701 and pretty much every other port in desperation. I have enabled L2TP Passthrough. I have made sure the external address is pingable. I have upgraded the firmware today to 4.3.4-1. Any suggestions greatfully welcome! thanks, Arron
FVS336Gv3 locks up and sometimes reboots
Hi i have 3 fvs336gv3 routers all running 4.3.4-2 firmware these units are running vpn's with each other in a star configeration. i have one that is locking up/rebooting several times a day all of a sudden it stopped doing this for a period of about 3 weeks now it has started again one thing i noticed is the unit dosn't keep time it seams to lose time and gain time for no apparent reason anyone got any idear'sFVS336G changes WAN MAC address based on connectivity - how to disable this?
There is a highly annoying feature of this router I would like to disable. When the router loses internet connectivity, it appears to change its WAN MAC address to a "dummy" address of "00:de:ad:xx:xx:xx" and "de:ad:de:ad:de:af". While I'm sure the designers of the device got a real kick out of that, it is causing problems with our cable modem service. See, our business cable internet connection allows up to 5 devices to be connected to the modem, and it determines the total number of connected devices by reading their ARPs. Unfortunately, the Netgear sends multiple ARPs with these dummy MAC addresses, causing those addresses to be reserved as 2 of 5 devices. Shown below is a screenshot of the modem page, showing all of the MAC addresses. Two of them come from the Netgear: I need a way to disable this; the device is taking up a MAC, and we need it for another device. I have tried setting a static MAC address on the WAN interface, but that does not disable this behvaior. Please advise.
FVS336GV3 adding multiple IP addresses on WAN
Make/Model: Netgear Prosafe FVS336GV3 4.3.3-6 - applies to any version Having wasted time reading multiple posts but successfully adding multiple IP addresses to a single WAN port, I thought I would post the simple solution myself, so that Netgear employees don;t have to stretch themselves too much.... Make sure you create and add SECONDARY ADDRESSES to the WAN (1 or 2) BEFORE you create your inbound NAT rules. Only then will they appear in the drop-down list where you can bind them to internal addresses (see above screen-shot)
