This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / Re: WAN Failover and Multigateway rules fail if more than two WANs enabled
« on: July 11, 2014, 07:54:51 pm »
I tried several times to make a bug report. I registered with on the site, (https://tracker.zentyal.org) but get the following error when I try to submit it:
Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.
Who can I contact about this?
Internal error
An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.
Who can I contact about this?
2
French / Re: Objet réseau
« on: July 09, 2014, 10:56:57 pm »
Ils sont dans le menu "Réseau" (network) sous, "Objects". Pour visualer les listes, il faut faire click sur l'icon, "Membres" (Members).
3
Installation and Upgrades / WAN Failover and Multigateway rules fail if more than two WANs enabled
« on: July 09, 2014, 05:37:28 pm »
We've been using Zentyal since version 2.2. We run the system with three WAN ports and one of the reasons we chose Zentyal is for its ability to aggregate our three WANs into one user network. However, since Ver 3.2, we haven't been able to make WAN Failover or Multigateway rules work correctly. Both seem to work if there are only two WANs enabled, but as soon as the third WAN port is turned on, all WAN Failover and Multigateway rules are deleted by the system, and the functions seem to disappear.
Both functions seem to work as expected in Version 3.2, but versions 3.3, 3.4 and now 3.5 all share this (these) bug(s)(?). Is this a bug, or a change in the definition of how these functions are defined?
I notice that there is very little space devoted to these topics in the documentation. In fact, there is no mention at all of WAN Failover or Multigateway rules until Appendix B. Even this short description uses images from Version 3.0.
For our deployment, the Multi WAN capability is one of the most attractive features of Zentyal. Is there anyway we can help troubleshoot it? Please let me know if there is any way to support the effort as part of the community.
Thank you.
Both functions seem to work as expected in Version 3.2, but versions 3.3, 3.4 and now 3.5 all share this (these) bug(s)(?). Is this a bug, or a change in the definition of how these functions are defined?
I notice that there is very little space devoted to these topics in the documentation. In fact, there is no mention at all of WAN Failover or Multigateway rules until Appendix B. Even this short description uses images from Version 3.0.
For our deployment, the Multi WAN capability is one of the most attractive features of Zentyal. Is there anyway we can help troubleshoot it? Please let me know if there is any way to support the effort as part of the community.
Thank you.
4
Installation and Upgrades / Zentyal 3.3 Multigateway woes (WAN Failover & Interface weights)
« on: March 14, 2014, 06:31:54 pm »
We run a small campus which is served by three DSL modems. We've been using Zentyal with its multigateway feature since ver 2.0. We had very good success with Zentyal 3.2, but recently upgraded to 3.3. At first I used an upgrade to get the 3.3, but was unable to get WAN Failover rules and Interface weights to store. They seemed settable, but returning to the page showed them clear again.
So, I did a scratch install and at first these rules seemed to work. However after entering filtering rules and doing other configurations for our network, they have now reverted to failing to "stick".
"Balance Traffic" and WAN Failover Event are both enabled, and the interface rates are specified correctly in "Traffic Shaping". Ultimately, WAN Failover fails to operate and users see the admin entry page for the modem instead of whatever they were surfing for when the lines go down. The Balance Traffic feature doesn't seem to work either, effectively wasting the extra bandwidth of our one faster link.
Has anyone heard of a solution for this?
Here are some details:
~$ dpkg -l | grep "zentyal-"
ii zentyal-bwmonitor 3.3.1 Zentyal - Bandwidth Monitor
ii zentyal-ca 3.3 Zentyal - Certification Authority
ii zentyal-common 3.3.2 Zentyal - Common Library
ii zentyal-core 3.3.5 Zentyal - Core
ii zentyal-dhcp 3.3 Zentyal - DHCP Service
ii zentyal-dns 3.3.1 Zentyal - DNS Service
ii zentyal-firewall 3.3.2 Zentyal - Firewall
ii zentyal-ftp 3.3 Zentyal - FTP
ii zentyal-gateway 3.3 Zentyal - Gateway Suite
ii zentyal-infrastructure 3.3 Zentyal - Network Infrastructure Suite
ii zentyal-ips 3.3 Zentyal - Intrusion Prevention System
ii zentyal-l7-protocols 3.3 Zentyal - Layer-7 Filter
ii zentyal-monitor 3.3.1 Zentyal - Monitor
ii zentyal-network 3.3.2 Zentyal - Network Configuration
ii zentyal-ntp 3.3 Zentyal - NTP Service
ii zentyal-nut 3.3 Zentyal - UPS Management
ii zentyal-objects 3.3.1 Zentyal - Network Objects
ii zentyal-openvpn 3.3 Zentyal - VPN Service
ii zentyal-remoteservices 3.3.2 Zentyal - Cloud Client
ii zentyal-services 3.3 Zentyal - Network Services
ii zentyal-software 3.3.2 Zentyal - Software Management
ii zentyal-squid 3.3.3 Zentyal - HTTP Proxy (Cache and Filter)
ii zentyal-trafficshaping 3.3 Zentyal - Traffic Shaping
ii zentyal-users 3.3.3 Zentyal - Users and Computers
ii zentyal-webserver 3.3 Zentyal - Web Server
So, I did a scratch install and at first these rules seemed to work. However after entering filtering rules and doing other configurations for our network, they have now reverted to failing to "stick".
"Balance Traffic" and WAN Failover Event are both enabled, and the interface rates are specified correctly in "Traffic Shaping". Ultimately, WAN Failover fails to operate and users see the admin entry page for the modem instead of whatever they were surfing for when the lines go down. The Balance Traffic feature doesn't seem to work either, effectively wasting the extra bandwidth of our one faster link.
Has anyone heard of a solution for this?
Here are some details:
~$ dpkg -l | grep "zentyal-"
ii zentyal-bwmonitor 3.3.1 Zentyal - Bandwidth Monitor
ii zentyal-ca 3.3 Zentyal - Certification Authority
ii zentyal-common 3.3.2 Zentyal - Common Library
ii zentyal-core 3.3.5 Zentyal - Core
ii zentyal-dhcp 3.3 Zentyal - DHCP Service
ii zentyal-dns 3.3.1 Zentyal - DNS Service
ii zentyal-firewall 3.3.2 Zentyal - Firewall
ii zentyal-ftp 3.3 Zentyal - FTP
ii zentyal-gateway 3.3 Zentyal - Gateway Suite
ii zentyal-infrastructure 3.3 Zentyal - Network Infrastructure Suite
ii zentyal-ips 3.3 Zentyal - Intrusion Prevention System
ii zentyal-l7-protocols 3.3 Zentyal - Layer-7 Filter
ii zentyal-monitor 3.3.1 Zentyal - Monitor
ii zentyal-network 3.3.2 Zentyal - Network Configuration
ii zentyal-ntp 3.3 Zentyal - NTP Service
ii zentyal-nut 3.3 Zentyal - UPS Management
ii zentyal-objects 3.3.1 Zentyal - Network Objects
ii zentyal-openvpn 3.3 Zentyal - VPN Service
ii zentyal-remoteservices 3.3.2 Zentyal - Cloud Client
ii zentyal-services 3.3 Zentyal - Network Services
ii zentyal-software 3.3.2 Zentyal - Software Management
ii zentyal-squid 3.3.3 Zentyal - HTTP Proxy (Cache and Filter)
ii zentyal-trafficshaping 3.3 Zentyal - Traffic Shaping
ii zentyal-users 3.3.3 Zentyal - Users and Computers
ii zentyal-webserver 3.3 Zentyal - Web Server
Pages: [1]