Dual WAN Seperate NAT Paths Not Working
Dual WAN Seperate NAT Paths Not Working
I have set up dual WAN, fed from two different Modems. WAN1 is the fastest connection, and is marked as primary WAN. WAN2 is deemed backup. The internet load balancing and link backup is working as expected and is great.
Now comes the issue.
app1 DNS is the IP of WAN1. It has a NAT on a few different ports that translate to some servers internally.
app2 DNS is the IP of WAN2. It has a NAT on a few different ports that translate to some servers internally.
Only one of these will work at a time. If app1 is working, externally, then app2 is not, and vice versa. I'm not positive what makes them swap, but it's incredibly annoying. If I make all apps go to one of the WAN IPs, and NAT from that, all works fine.
I've tried disabling Application Optimized Routing:, didn't fix it. I've tried without Link Backup, no go. I've tried with Link Backup - no go.
I've tried creating policy routing to make the one server always go out the WAN IP that it's NATed from, and the other to the other WAN, still no go.
There MUST be something obvious I'm missing. Can I not have different WANs NATing to different local addresses?
I appreciate any help anyone can offer. As to the well, why are you doing this? My primary is the strongest speeds. I'm having all my gaming servers/apps like teamspeak run through this. I want all my generic external web hosting and camera software to go through the weaker link. I have priorities - haha.
I'm using the default attack prevention settings.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
+3 Feature Request! ACTIVE / ACTIVE MULTI-WAN NAT (Virtual Servers)!
- Copy Link
- Report Inappropriate Content
This works on the old firmware version 2.0.1 Build 20223 Rel.68551. I just checked. This does not work on the latest firmware version.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Hank21 It looks like it's come to light that I'm not the only one, and on top of that, there's a strong possibility this is a bug introduced by a later version of firmware. Is there any way to escalate up? I tried with tech support, but they kept telling me they could not replicate the issue.
I never did think it made sense we could do load-balancing, and connection-level routing, but not be able to have different WANs NAT to different internal addresses. It being a bug makes a whole lot more sense.
- Copy Link
- Report Inappropriate Content
BTW: Policy-Routes LAN -> WAN will route traffic over the wan iface u specify, without any problems.. Analysing their WONDERFULL shell codes -with nearly no comments in it- atm. with openwrt sources and unknown copied sources in it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 1966
Replies: 16
Voters 0
No one has voted for it yet.