I'm running into a little trouble with the Port Forwarding page in the web GUI. I am port forwarding WAN ports 80 and 443 to a webserver inside my LAN, and this (with the auto firewall feature and hairpin NAT) are working great. I ran into some trouble with PPTP VPN clients, as they would get redirected to the router's GUI instead of following the hairpin NAT to the webserver. This was fixed by adding interface "pptp+" to the list of LAN interfaces (as mentioned in this thread), but here's where things got interesting.
To do so from the GUI, I selected "other" from the list and entered "pptp+" into the adjacent field. Unfortunately, the GUI insists that this is an "Invalid interface name" and will not allow me to apply the config. The workaround was to use the Config Tree to add pptp+ to the list, and now it appears correctly in the Port Forwarding page.
This isn't quite the end of the story, however, as now I still can't use the Port Forwarding page to make any additional changes (say, adding or removing any port forward rules) -- it complains once again that "pptp+" is an invalid interface name. I can continue to go back to the Config Tree for any future changes (I'm not quite up to speed on the CLI yet), but at this point the Port Forward page is informational only.
Is this a bug, or am I missing something?
Alternatively, I could add a list of pptp interfaces (pptp0, pptp1, pptp2, etc) using the Port Forwarding page, and that presumably would work just fine, but I'm afraid I'll forget to go back and add one more the next time I inherit a new VPN user. The pptp+ wildcard interface is definitely preferable.
I'm running EdgeOS v1.9.0 on an EdgeRouter Lite.