Orbi WiFi 7 RBE973
Reply

FVS336Gv2 impossible to enable PPTP on same subnet !

Amoniks
Aspirant

FVS336Gv2 impossible to enable PPTP on same subnet !

Hello,

 

We installed a FVS336Gv2 in a company, yesterday we did the firmware upgrade from 3.0.9-2 to 4.3.3-6, and here is our problem :

 

Our FW ip is 192.168.1.1 with mask 255.255.255.0 , our subnet is 192.168.1.0... and here is our big problem :

 

We have a dedicated server in France, and we use it to print some Datas on the servers (we print the datas to a printer located in our Subnet in Switzerland), we had the PPTP server enabled before the firmware update with these configurations : 

 

/vpn/pptpServer/configure "0x4a0002=\"1\"" "0x4a0003=\"192.168.1.200\"" "0x4a0004=\"192.168.1.205\"" "0x4a0005=\"0\"" "0x4a0007=\"0\"" "0x4a0008=\"0\"" "0x4a0009=\"1\"" "0x4a000a=\"0\"" "0x4a000c=\"1\"" "0x4a000d=\"0\"" "0x4a000e=\"300\""

 

But now on the new firmware i can't enable the PPTP server with the address range of 192.168.1.200 to 192.168.1.205, i have this error message now :

 

The subnet specified is same as LAN/VLAN subnet, Please specify a different subnet.

 

if community can help me to get my external server able to print again on our local printers would be very nice !

thank you in advance for your help.

 

 

Message 1 of 6
Retired_Member
Not applicable

Re: FVS336Gv2 impossible to enable PPTP on same subnet !

Hi Amoniks,

 

Welcome to the community!

 

This is expected behaviour in firmware 4.3.3-6, I have tested other ProSafe models (SRX5308 and FVS336Gv3) running firmware 4.3.3-6 and the same message is observed.

 

You will need to specify a different subnet in the PPTP IP settings in order to use it.  Using a different subnet on the FVS336Gv2 PPTP settings will mean the PPTP client will pickup a new IP address when connecting to the PPTP VPN so you may just need to re-map to the new IP address picked up by the PPTP client.

 

As this change in the firmware is intended, it is not seen as a bug and will not be changed.

 

Hope this helps.

 

Thanks. 

Message 2 of 6
Amoniks
Aspirant

Re: FVS336Gv2 impossible to enable PPTP on same subnet !

Hello,

 

thank you for your reply.

 

But i just setup the subnet 192.168.4.1 in the PPTP Server, i can connect my French Server through PPTP to my FVS336Gv2, but i can not ping my FVS336Gv2 or any device inside the subnet 192.168.1.0, can you please explain me how can i re-map my 192.168.4.1 ip address (French Server) to my LAN subnet (192.168.1.0) ???

 

i need to print some important files...

 

Thank you.

Message 3 of 6
Retired_Member
Not applicable

Re: FVS336Gv2 impossible to enable PPTP on same subnet !

when the French Server connects the vpn and receive IP address 192.168.4.1, the fvs336gv2 should update it's routing table to include the 192.168.4.x network so the local lan clients and the VPN client (French server) can communicate.

 

Can you go to Monitoring - Diagnostics. From the Ping section see if it is possible to get a reply from the ip address 192.168.4.1 

 

In relation to mapping, what i was referring to is if you had mapping on your LAN client to the IP address the french server used to receive when the PPTP function work in the 192.168.1.200-205 range.

 

The mapping from local LAN 192.168.1.x to the PPTP VPN range 192.168.4.1 should happen automatically by the fvs336gv2

Message 4 of 6
Amoniks
Aspirant

Re: FVS336Gv2 impossible to enable PPTP on same subnet !

it's just impossible...

 

i could now setup the ip of my client on the same subnet (french server = 192.168.1.201) but i can't reach the printer (192.168.1.25)....

I never had so issue to make a little VPN working....

 

We think to change from Netgear to Fortinet... it's really bad how this firewall is working....

From the Firmware update now our firewall don't give the internet to the LAN...

and i need to close all 3 VPN tunnels to make LAN TO WAN work again...

 

Look at the LOGS....   :

 

Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] HTB: quantum of class 11024 is big. Consider r2q change.
tHashTblDelete+0x100/0x1f8 [vipsec]
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] HTB: quantum of class 10001 is big. Consider r2q change.
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] p->perfect 0000000000000000 p->h a80000000533ae00
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_dump(tp a80000000343a680,fh 0x0,skb a800000006fb9080,t a800000006fab010),p a800000006b7a500,r 0000000000000000,b a800000006fab038
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_change(tp a80000000343a680,handle 0x00000000,tca a800000007c0b500,arg a80000000483b920),opt a80000000533aa30,p a800000006b7a500,r 0000000000000000,*arg 0x0
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_get(tp a80000000343a680,handle 0x00000000)
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_init(tp a80000000343a680)
Mon Jan 18 16:33:31 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] HTB init, kernel part version 3.17
Mon Jan 18 16:32:36 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] IPsec: device unregistering: ppp1
<7
Mon Jan 18 16:30:06 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_delete(tp a80000000343a800,arg 0xa80000000343a388),p a800000004bf6280,f 0000000000000000
0x0/0x560 [vipsec]
Mon Jan 18 16:30:06 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_walk(tp a80000000343a800,walker ffffffff80443ce0),p a800000004bf6280
Mon Jan 18 16:30:06 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] tcindex_destroy(tp a80000000343a800),p a800000004bf6280
Mon Jan 18 16:30:06 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] IPsec: device unregistering: ppp1
Mon Jan 18 16:30:00 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] IPsec: device down: ppp1
e at kernel/softirq.c:140
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]
ffffffff80139928>] tasklet_action+0xa0/0xf8
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8011bb80>] elf_core_dump+0x1b8/0xbd8
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80119c54>] handle_sysn32+0x54/0xa4
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802cad80>] compat_sys_setsockopt+0x200/0x400
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802ae838>] sys_setsockopt+0xc0/0xc8
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802aea14>] sys_sendto+0xbc/0x110
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff801201d0>] do_page_fault+0x40/0x430
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802b0c1c>] lock_sock+0xbc/0xd0
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8016ccec>] __handle_mm_fault+0xb1c/0xdb8
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8014bdb8>] autoremove_wake_function+0x0/0x48
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802adb70>] sock_sendmsg+0xb0/0x100
Mon Jan 18 16:29:50 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8017f608>] kfree+0x68/0xe0

Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025e130>] addrRepositoryDelete+0x3d0/0x620 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025e130>] addrRepositoryDelete+0x3d0/0x620 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025cd98>] ulpRepositoryDelete+0x128/0x1e0 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025ac00>] ulpNodeFree+0x0/0x90 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000259918>] ulpNodeUnlink+0x0/0x48 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80133aa8>] printk+0x0/0x88
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260458>] portHashTblDelete+0x100/0x1f8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8017f608>] kfree+0x68/0xe0
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000002601d4>] deletePort+0xac/0x230 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260000>] portHashTblDump+0x130/0x258 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260458>] portHashTblDelete+0x100/0x1f8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8017f608>] kfree+0x68/0xe0
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000002601d4>] deletePort+0xac/0x230 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025d750>] deletePolicy+0x88/0xc0 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260000>] portHashTblDump+0x130/0x258 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000024dde8>] key_freesp+0x238/0x3a8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000028b3d8>] dstBufFree+0x0/0x260 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000024c9e0>] key_freesav+0x0/0x560 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80180000>] cache_alloc_refill+0x2d8/0x628
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000000a29f0>] xlr8NatCtxFlush+0x138/0x1b0 [xlr8Nat]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000000a2a30>] xlr8NatCtxFlush+0x178/0x1b0 [xlr8Nat]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] Call Trace:
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] Badness in local_bh_enable at kernel/softirq.c:140
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8011bb80>] elf_core_dump+0x1b8/0xbd8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80119c54>] handle_sysn32+0x54/0xa4
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802cad80>] compat_sys_setsockopt+0x200/0x400
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80139928>] tasklet_action+0xa0/0xf8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802ae838>] sys_setsockopt+0xc0/0xc8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802aea14>] sys_sendto+0xbc/0x110
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff801201d0>] do_page_fault+0x40/0x430
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802b0c1c>] lock_sock+0xbc/0xd0
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8016ccec>] __handle_mm_fault+0xb1c/0xdb8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8014bdb8>] autoremove_wake_function+0x0/0x48
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff802adb70>] sock_sendmsg+0xb0/0x100
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff801203d8>] do_page_fault+0x248/0x430
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000292a94>] key_output+0x29c/0x3b8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8010d0d4>] timer_interrupt+0x19c/0x360
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000002490c0>] key_parse+0xca8/0xdb8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260000>] portHashTblDump+0x130/0x258 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8014f108>] ktime_get_ts+0x58/0xb0
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025a6d8>] keySpdDeleteWrap+0x488/0x4a8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8025df00>] memcpy+0x0/0x8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000259888>] keySpdDelete+0x80/0xc8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025e130>] addrRepositoryDelete+0x3d0/0x620 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025e130>] addrRepositoryDelete+0x3d0/0x620 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025cd98>] ulpRepositoryDelete+0x128/0x1e0 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025ac00>] ulpNodeFree+0x0/0x90 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000259918>] ulpNodeUnlink+0x0/0x48 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80133aa8>] printk+0x0/0x88
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260458>] portHashTblDelete+0x100/0x1f8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000002601d4>] deletePort+0xac/0x230 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260000>] portHashTblDump+0x130/0x258 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260458>] portHashTblDelete+0x100/0x1f8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000002601d4>] deletePort+0xac/0x230 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000025d750>] deletePolicy+0x88/0xc0 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c000000000260000>] portHashTblDump+0x130/0x258 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000024dde8>] key_freesp+0x238/0x3a8 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000028b3d8>] dstBufFree+0x0/0x260 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c00000000024c9e0>] key_freesav+0x0/0x560 [vipsec]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff80180000>] cache_alloc_refill+0x2d8/0x628
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000000a29f0>] xlr8NatCtxFlush+0x138/0x1b0 [xlr8Nat]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<c0000000000a2a30>] xlr8NatCtxFlush+0x178/0x1b0 [xlr8Nat]
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL]  [<ffffffff8013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] Call Trace:
Mon Jan 18 16:29:39 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] Badness in local_bh_enable at kernel/softirq.c:140
Mon Jan 18 16:27:14 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] device eth0.1 left promiscuous mode
e
013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:27:14 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] eth0.1: dev_set_promiscuity(master, -1)
Mon Jan 18 16:26:54 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] device eth0.1 entered promiscuous mode
013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:26:54 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] eth0.1: dev_set_promiscuity(master, 1)
Mon Jan 18 16:26:09 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] device eth0.1 left promiscuous mode
e
013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:26:09 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] eth0.1: dev_set_promiscuity(master, -1)
Mon Jan 18 16:25:54 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] device eth0.1 entered promiscuous mode
013975c>] local_bh_enable+0xa4/0xd8
Mon Jan 18 16:25:54 2016((GMT+0100)) [FVS336Gv2][Kernel][KERNEL] eth0.1: dev_set_promiscuity(master, 1)

 

Message 5 of 6
Retired_Member
Not applicable

Re: FVS336Gv2 impossible to enable PPTP on same subnet !

Amoniks,

 

Sorry to hear the issue is not resolved and now you see other issues also. How was it possible that you could now setup the ip of the client on the same subnet (french server = 192.168.1.201)?

What steps did you take on the FVS to make this possible?

 

The IP address used in the PPTP VPN configuration is now intentionally different so as to eradicate possible strange routing behaviour when the LAN subnet and the subnet of the PPTP VPN client are the same. This could explain why you see strange LAN to WAN behaviour when the PVN is active.

 

At this stage I recommend you also log a support ticket through the contact us page as your issue may need to be diagnosed further via the support team. Contact us page is available here http://support.netgear.com/general/contact/default.aspx

 

Thanks.

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 3618 views
  • 0 kudos
  • 2 in conversation
Announcements