Hello, I have a device in a remote location connected to a Pepwave Peplink MAX BR1 Mini Core’s LAN port, however the device does not have a gateway IP set. The static local IP of the device I’m trying to reach through a port forward is 192.168.50.201 and the Pepwave LAN IP is 192.168.50.1. The Pepwave is connected to the internet and I have remote access through the WAN of the Pepwave.
Ultimately I need to get to a web server hosted on the device at TCP port 80 which will let me adjust network settings. Is there a way in the BR1 Mini to do a source NAT for the port forward instead of maintaining the original source IP so it appears to the device at 192.168.50.201 that the traffic is coming from the modem’s LAN IP at 192.168.50.1? Or maybe there is some other solution without port forwarding? Thanks!
Thanks Laurynas,
It looks like that InTouch should do what I’m looking for. It does seem like it requires a per modem subscription, however. I’m currently looking to see if my company would be okay to purchase that for this. Are there any alternatives that would not need a subscription?
Michael, if you don’t have a public IP on the wan/cellular interface, not really.
Here are your options in order of best to worst:
- InTouch
- SpeedFusion tunnel to a device/VM local to you that you can use to access the remote subnet via TCP/SSH/etc.
- Public WAN IP on WAN or cellular, exposing port 80 to the internet. THIS IS VERY BAD DO NOT DO THIS.
If you need a PrimeCare license to get this done, shoot me a DM and we can sort this out pretty quickly for you.
Hi Christopher,
I actually do have a public IP in a manner of speaking for the WAN side of the modem. It’s behind a VPN, but I have access to that VPN, so a port forward shouldn’t be a security concern like it normally would be with a fully public IP.
My main issue is that the device I am trying to access does not have a gateway IP set, and so when I try to port forward to the device, the device does not know how to respond to me with the port forward. It sees an IP outside of its own subnet, but it doesn’t have a route back to me. However, I can ping the device from the LAN of modem itself since the modem has an IP in the same subnet as my device.
Ah, thanks. That makes sense. One of the unique features of Peplink is the ability to do layer 2 tunnels. This will drop you onto the same L2 environment as your remote device.
Still, for incidental remote access, InTouch is the way to go.