[SecuReporter] Upload fail going out wrong interface?
Best Answers
-
What is the device wan trunk mode?
Is vlan443 created based on OPT interface or different interface?
What is metric value of vlan443 interface?
5 -
Hi @PeterUK
For device local traffic(From ZyWall to Any), you can create a policy route from ZyWall to Any, next Hop is auto.
Device local service will go straight to main route table and refer to metric value.
Policy route: Incoming = ZyWall, Destination = any, next-Hop = auto
Packet flow: Bypass wan trunk table, go straight to main route table, and refer to metric value.
5
All Replies
-
What is the device wan trunk mode?
Is vlan443 created based on OPT interface or different interface?
What is metric value of vlan443 interface?
5 -
VLAN443 is based on LAN1 and has internet by USG40, the Licensing > Registered refresh works and goes out vlan443 just fine.
0 -
Setting the metric to 1 for VLAN443 now makes Upload succeed but really shouldn't need to with the order of the trunk to just make it work?
Thanks
0 -
Now its gone back to:
[SecuReporter] Upload fail.
[SecuReporter] A connection timeout
trys to go out OPT port even if VLAN443 metric set to 1 now
Can see a traffic capture on OPT to 34.243.175.172 and nothing going out VLAN443 except for the Registration refresh.
0 -
Hi @PeterUK
For device local traffic(From ZyWall to Any), you can create a policy route from ZyWall to Any, next Hop is auto.
Device local service will go straight to main route table and refer to metric value.
Policy route: Incoming = ZyWall, Destination = any, next-Hop = auto
Packet flow: Bypass wan trunk table, go straight to main route table, and refer to metric value.
5 -
Good rule didn't think you can select ZyWall in routing.
So if next hop is VLAN443 with metric set to 0 would that work?edit seems to be working edit2 nope causes problems with ping to OPT so has to be auto.edit3
Seem to be causing more problems
in Logs Category myZyXEL.com now shows
Connection error has occurred.
[SecuReporter] Parameter required. arg_cnt=8
and Registration status refresh shows
Unable to connect to myZyxel.Try again later. < or maybe its down? < Registration status refresh is up on my USG40 but something odd has happened to my Zywall 110...
0 -
With the routing rule from ZyWall to any it causes Registered refresh to fail so it causes problems with that showing.
Unable to connect to myZyxel.Try again later.
This makes no sense the service license refresh works but not Registration refresh with this routing rule. So the service license refresh is not making an outgoing connection when clicked.
Edit disbaled the rule Registered refresh with VLAN443 metric set to 1 works again so something really bad with routing rule from ZyWall to any.
0 -
So this is still a ongoing issue but just to update I have set both OPT and VLAN443 to metric 0 and when the upload fails or even a Registration refresh what seems to make it work again is to inactivate and activate VLAN443 then it works for some hours then trys going out OPT.
I have another setup with USG40 based on the same setup and that shows fine but have not activate SecuReporter but the Registration refresh works fine and going out VLAN443 with a uptime of over 24 days with V4.33(AALA.0)ITS-WK08-2019-03-14-190200778
0
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 102 Nebula Status and Incidents
- 5.8K Security
- 302 USG FLEX H Series
- 283 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 255 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.7K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 76 Security Highlight