Beta 2 feedback

Hi,

Thank you for the feedback. We need some more details

1. IPv6 no longer obtains address by DHCP over PPPoE.

- We do not support IPv6 with PPPoE. Please clarify the configuration.

3. mail report set to generate at 1100 AEDT has not been generated current time is 1106.

This is the behavior is persist from first release of XG.

The notification mail would be generated after set time to max +1 hour, as we have every hour thread to check the mail notification queue.We have already JIRA Id for improvement and tracking it under NC-10222.

5. . mail testing and reporting still broken, no sender, no receiver and passed as safe.

Please provide the setup/network details and firewall rule/smtp profile details

Hi,

item 1. under v17b1. I Was assigned an IPv6 addressing DHCP over PPPoE

item 2. the previous report was that issue was being addressed and fixed in this beta (2)

Let me try and explain. this is an extract from the report that was generated today. "Server Time : Fri Oct 06 12:14:51 GMT+10:00 2017", the trouble is I am in AEDT which is 11 hours.

Item 5. 

I am using the mail template and the default mail settings. I am using the same configuration in mr8 as well as beta2.

I can send you my backup if you would like.

Ian

Hi,

Item 1: Please share the screenshot of that Interface UI

Item 2 and 5 sending you PM

Hi,

I have sent you lots of details as requested and screen shots of the IPv6 assignments. I have since found while running the tests for you that I am assigned a IPv6 /64 on the external interface with a gateway using DHCP over PPPoE in both beta 1 and beta 2. I have restarted the XG a number of times and edited the interface.

Happy hunting.

Ian

Hi,

there is some slightly better news on reports. Since upgrading my main XG to v17b2 the daily reports are being generated at reasonable hours, not the correct time, but within 2 hours instead of 11.

Ian

Hi,

there is some slightly better news on reports. Since upgrading my main XG to v17b2 the daily reports are being generated at reasonable hours, not the correct time, but within 2 hours instead of 11.

Ian

Hi rfcat_vk,

Thank you for the update, this due to we have resolved the timezone/time issue in Beta-2(NC-21762, already shared). The +1 hour time difference would be there as it is in product backlog NC-10222.

Hi Deepti,

the time zone issue does not appear to be fixed, my reports still show a 2 hour difference not the up to one hour expected.

Ian