I have a Balance 580 running 5.4.9 build 2573 and having trouble getting a service to forward TCP 80 to a device on the LAN.
Operating mode is NAT, no firewall rules involved, all inbound is allowed.
System is configured for HTTPS mgmt only, not HTTP.
Service is set up on both of two WAN interfaces, for any IP and TCP port 80 to forward to a server 192.168.10.10 on the LAN.
I have other services working fine with similar configuration, such as a print service running on TCP 515 forwarding to a printer.
For now, there are no real users of the network, just trying to tshoot this issue with no production traffic
I am trying to determine if the Peplink itself is responding to the port 80 requesting incoming from the WAN instead of forwarding to the LAN. I disabled HTTP for management, so it seems it should not be listening on port 80 on the WAN interfaces.
While troubleshooting, I found the hidden support page that allows packet capture, and I kicked off a capture and started investigating. However, the packet captures only worked a few short times and after I let the capture run longer I found I could no longer access the admin GUI, like the mgmt plane was hosed. It still seemed to forward traffic.
The device will get powered down this evening as the vehicle it is in is stowed, so I intend to pick back up tomorrow when hopefully the Peplink recovers after reboot.
Is anyone aware of an issue forwarding TCP port 80 (HTTP) from a WAN link to the LAN using a service, where maybe the Peplink is intercepting and redirecting to the GUI rather than forwarding the request?
Is anyone aware of packet capture limitations in either duration or size of capture that would result in instability or nonresponsiveness of the device?
Thanks for any help