This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BUGs and other issues new and old in V18 MR1

Hi folks,

V18.0.1 MR-1 existing bugs, new BUGs and things that weren't reported as bugs.

1/. Existing bugs that didn't get fixed

a) multiple entries in the logviewer for DDNS registrations.

b} diagnostic traffic reporting - way under actual

c) IPv6 static addresses not appearing in the DHCP leased list

d) IPv6 RA assigned addresses not appearing in logviewer or in assigned address list

e) use of FQDNs in IPv6 firewall rules

f) daily reports will have to wait until tomorrow to see they haven fixed

g) pattern updates for authentication client, Sophos connect client and SSLVPN clients have not updated since Dec 2019

 

A previous bug though not reported.

XG fails to stop adult/sexually explicit sites even though they are correctly categorised. Blocks video and ads associated with the sites, but not the sites. Now according to the firewall logviewer -> web page one site is blocked, but the actual block message come from Sophos Home Premium. The appears to be a bug in Sophos Home Premium with regard to blocking some of these sites on Apple devices, currently inland with Sophos Home Premium.

 

New Bugs.

So far I have not found any.

 

Maybe BUG

a) normally when I run speedtest I see entries in the IPS GUI but no values in the table when I click on an item, today no entries after 4 speedtests.

 

A question about a BUG in V18 GA

Did the default drop rules get fixed eg can I remove my default rule?

 

Ian



This thread was automatically locked due to age.
  • This is interesting because since I upgraded to v18 MR1, I got some issues regarding Google Play Store. 

    I didn't changed anything in my configuration and rules, btw. So maybe there is something wrong in MR1...

  • TheBalmasque said:

    This is interesting because since I upgraded to v18 MR1, I got some issues regarding Google Play Store. 

    I didn't changed anything in my configuration and rules, btw. So maybe there is something wrong in MR1...

     
    Yep, Google is affected as well. 
     
    I think what's going on here is that MR1 no longer respects the "old" (pre-v18) web exception list. I had Google on there forever and after the upgrade to MR1 I had to put Google on the "new" (URL-Group based) exceptions to get it to work. v18 releases prior to MR1 respected the old list.
     
     
     
  • What's even more weird (as I just found out) is that play.google.com is even included on the managed exclusion list, as seen here:

    Yet I had to add it to my local exclusion list for it to work. Something is really broken here. 

  • cryptochrome said:

     

     
    TheBalmasque

    This is interesting because since I upgraded to v18 MR1, I got some issues regarding Google Play Store. 

    I didn't changed anything in my configuration and rules, btw. So maybe there is something wrong in MR1...

     

     

     
    Yep, Google is affected as well. 
     
    I think what's going on here is that MR1 no longer respects the "old" (pre-v18) web exception list. I had Google on there forever and after the upgrade to MR1 I had to put Google on the "new" (URL-Group based) exceptions to get it to work. v18 releases prior to MR1 respected the old list.
     
     
     
     

    I'm seeing the same behavior on MR1.  

  • Will this issue be addressed in a new firmware version?

    Any news when this will be corrected?

  • I've identified the Dropped due to TLS engine error: FLOW_TIMEOUT[5] error with poor performance on some sites.  I've reverted back to using the web proxy for now.