Zywall 310 why on other firewall as a source address is see my LAN address
on zywall 310 I've got 2 WAN ISP: main WAN1 with address i.e. 22.214.171.124 / 29, backup WAN2 126.96.36.199 / 29. LAN address 192.168.1.1 / 24
I configured second zywall (old Zywall5) in WAN2 network with address 188.8.131.52 and make firewall rule to mgmt access from Zywall 310. When I try connect from Zywall 310 to Zywall5 I can't. In Zywall5 logs as a source address I see... my LAN address i.e. 192.168.1.33 not 184.108.40.206, when I switch off WAN2 on Zywall 310 it's works good: I connect to Zywall5 via WAN1 and see as a source 220.127.116.11
I try second configuration: Zywall5 is set in WAN1 network with address 18.104.22.168. It's works good as a source address I see WAN1 Zywall 310 22.214.171.124
Is some wrong set in config Zywall 310?
As we talked in the private message, that is a misconfiguration will cause that kind of problem.
Also, you said that you want to set Policy rule for 2 WANs.
- If WAN1 working use only WAN1
- If WAN1 is not working use WAN2 but only until WAN1 works again.
Can you try adding a Trunk with Spillover algorithm?
You can test Trunk interface's behaviour as following;
1- Open 2 command line from Windows and ssh to gateway, type following command for 2 external interfaces;
Router# packet-trace interface wan1 ip-proto icmp
3- Plug in the removed interface, check which external interface is pinging.
Do you think that it will work for your environment?
HiI check it next week0
- 8.5K All Categories
- 1.6K Nebula
- 72 Nebula Ideas
- 57 Nebula Status and Incidents
- 4.5K Security
- 227 Security Ideas
- 985 Switch
- 46 Switch Ideas
- 882 WirelessLAN
- 24 WLAN Ideas
- 5.2K Consumer Product
- 158 Service & License
- 280 News and Release
- 99 Success Stories
- 61 Security Advisories
- 13 Education Center
- 581 FAQ
- 263 Nebula FAQ
- 160 Security FAQ
- 76 Switch FAQ
- 75 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 62 About Community
- 46 Security Highlight