I have a lab setup with a MAX-BR1. Behind the PepWave is a Cisco router connected to the lab network - only one of these networks needs internet access. All routing is working. DNS proxy is working and the hosts in the lab can resolve. However I cannot get out to the internet on anything and I’m pretty sure it has to do with NAT. I have tried a Many-to-One config on the PepWave with no luck. Is there any guidance on how to actually set this up? The network behind the PepWave is a 172 network. Thanks for any help - I’m sure someone else has done this but I can’t find anything in the community that matches this simple situation.
Hello @howlingthunder,
Welcome Michael to the Peplink Community Forum.
Have you contacted your local Peplink Partner through which you purchased the router? Their in-house PCE (Peplink Certified Engineers) can best help resolve this.
Here is a quick test and solution: backup your configuration, then factory reset the device. Put a laptop on the LAN and see that you get internet through the router; if not, then something is misconfigured on the WAN setting(s) (such as seen occasionally with a static IP on a WAN). Once you get the internet working, make other changes to your connection to the device(s) on the LAN.
Out of interest, are you using the Peplink InControl2 platform? This is one of the best ways to manage and monitor Peplink devices remotely.
Happy to Help,
Marcus 
Thanks for the above. I do manage with IC2. My issue is not with any of the defaults. If I connect a LAN and just allow DHCP from the PepWave, or connect to the PepWave WiFi, everything works fine.
My issue is if I connect an existing network to it, I can configure routing and everything pings OK, but because NAT doesn’t seem to function properly no hosts can get out. DNS works proxy’ ing through the PepWave, but not access to internet.
I’ve tried doing IP Passthrough as well. Cisco router picks up WAN IP. NAT trans on Cisco router shows everything still translated to 192.168.X.1 - even though I am doing IP Passthrough. I changed NAT on PepWave to Passthrough as well. I don’t get it.
I don’t have these PepWave’s to create whole new networks with. I need to make them the WAN GW for existing networks, and that has never seemed to work (multiple PepWave’s, multiple networks).
The test is to plug your laptop into the LAN of the BR1. If you can access the internet from there the BR1 is working.
You’re not clear in your OP if there is NAT on the CISCO WAN<>LAN? If not, then you’ll need a static route (or dynamic routing protocol) configured so the BR1 knows to use the CISCO 172. address when it needs to forward traffic back.
1 Like
I get what you are asking, and am trying to find an answer to the same problem. I wish people would read before they respond…
Yeah it’s kind of unexpected. If I simplify what I’m asking above: From the PepWave down, everything pings, everything can talk, no issues whatsoever. It’s when I try to go through the PepWave - either using PepWave NAT, NAT on my router, or just Passthrough - it doesn’t work. I have to use the built-in PepWave LAN or I get nothing. Doesn’t make sense that I cannot connect this to an existing network and use PepWave as a gateway. That’s part of the core functionality of the product that doesn’t seem to work.
Can you put together a network diagram for us? Your description isn’t clear enough for me to understand the setup.
Revisiting this.
From where to where?
This is expected behavior. Your CISCO is not doing IP passthrough it’s in NAT mode, so only the CISCO wan gets a WAN IP.
To clarify:
- You plug a laptop into the LAN of the Peplink and you get DHCP, DNS and internet works fine?
- You plug your CISCO router into the Peplink and nothing behind the route can access the internet?
- Can you login to your CISCO and ping 8.8.8.8?
- Does DNS resolve for the LAN clients as well as the CISCO router?
- Can you post your CISCO config here?
- Is CISCO LAN subnet different to Peplink LAN subnet?