Firmware 6.3.4 build 3613 stops port forwarding

Product Discussion Peplink Balance
1

I upgraded my Balance 580 HW Rev 1 router from firmware version 6.1.2 build 3071 to 6.3.4 build 3613 this morning and all port forwarding stopped.

When I rolled back the firmware to version 6.1.2, all port forwarding started working again.

Does anyone know of any issues with this release or problems that would cause this?

Thanks,
Warren

2

I suspect this is not related to the Port Forwarding. Just take the example below. Can you share how you access the internal server from WAN side? Access using 192.168.1.10 or 10.1.1.10?

Server (192.168.1.10) —> (192.168.1.1, LAN) Balance 580 (WAN, 10.1.1.10) —> Internet

1 Like
3

Hi TK_Liew,

Thank you for the reply. My setup has been working flawlessly for years.

Inbound Access
Web server (192.168.1.208) —> (192.168.1.1, LAN) Balance 580 (WAN, 71.180.XXX.1XX) —> Internet
Web server (192.168.1.208) —> (192.168.1.1, LAN) Balance 580 (WAN, 97.76.XXX.1XX) —> Internet

DNS
A www.mydomain.com (WAN, 71.180.XXX.1XX)
A www.mydomain.com (WAN, 97.76.XXX.1XX)

ns1.mydomain.com (WAN, 71.180.XXX.2XX)
ns2.mydomain.com (WAN, 97.76.XXX.2XX)

4

Just to isolate the problem, if you using direct IP address 71.180.XXX.1XX & 97.76.XXX.1XX, do you able to access your server ?

Beside that, do you tested the DNS resolve for the domain still work after you upgrade ?

1 Like
5

Did you verify the inbound firewall is open for the port and LAN destination desired? What is your default firewall setting?

1 Like
6

Hi sitloongs,

I did an external test on my mail server with MX toolbox and was not able to access it.Yes, dns resolved.

7

Yes, i did. I have nothing blocking inbound access.

8

I just rebooted the router this morning into the upgraded firmware and all seems to be working. I wish I could find out why I had this issue. Thank you, everyone, for the help.

1 Like
9

Okay, I started doing some digging and figured out what is happening, I am reconfiguring my small network with vlans, under version 6.3.4 build 3613, the issue is when I add a tagged vlan to my lan port, forwarding stops on my untagged native vlan to my web servers and email servers. The behavior is different on the older firmware version 6.1.2 build 3071, where everything works correctly. The ports on my Cisco switches are untagged so it should still work. Do you know if any difference in the firmware that would cause this? Am I overlooking something?

10

Thank you for helping to isolate the problem. This can clear that the issue is not on the port forwarding nor the domain resolve issue.

Can you please share your device LAN settings here ? Why you created tagged VLAN for B580 LAN port seem Cisco is untagged ?

1 Like
11

Sorry for the late response. i didn’t see your reply.

What I was trying to say is. I still have my untagged traffic active until I move all of my devices to its proper tagged vlan.

I have servers on the untagged vlan using port forwarding. When I add vlans to the same lan interface, port forwarding stops under version 6.3.4 build 3613 for the untagged traffic. If I switch back to 6.1.2 build 3071, the untagged and vlans can coexist and i am not sure why this is happening.

12

@Warren_Cohn,

Please open a support case for support team to check. This need to check from the device.

1 Like