Thermomix Cookidoo Connection can lo longer be established after Upgrading to v18 EAP

I do use my Sophos XG at Home.
There I do have a Thermomix which is connected with Cookidoo through a Cook Key (WiFi)

Before Upgrading to v18 EAP i was able to connect to Cookidoo (their Portal) without Problems an could sync it there.
After upgrading this in no longer possible an it tells me that it has no internet connection.

I checked Firewall Logs. There I can see packets on Port 80 and 443 that are allowed.
After that (a few minutes later) there a packets that are Invalid Traffic (I guess a Stateful Inspection Timeout)

IPS logs don't show anything that is blocked.
SSL Inspection is not showing any handled traffic for the source IP.

Any idea? ;)

0 LuCar Toni over 4 years ago

Can you show us your SSLx Rule (if created) and your firewall Rule for this host?

__________________________________________________________________________________________________________________
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Björn Ebner over 4 years ago in reply to LuCar Toni

There is no specific SSLx Rule defined in the system.

Also there is only a LAN -> WAN Any Rule with a Linked NAT Rule ans IPS activated that all other devices within the LAN Zone also use that work fine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 LuCar Toni over 4 years ago in reply to Björn Ebner

Do you have anything enabled beside IPS in this firewall rule?

Thats the reason for asking.

Maybe try a new "Host based" firewall rule on top.

__________________________________________________________________________________________________________________
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Björn Ebner over 4 years ago in reply to LuCar Toni

No, only IPS is activated and there are no Log Entries for this IP in the IPS Log.

It is also possible that there is an issue with the portal itself but it is strange that it is no longer working after installing v18 EAP.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Björn Ebner over 4 years ago in reply to Björn Ebner

It is still not working.

So i guess it is no issue with the portal but due to a change from 17.5 to 18.

But I don't have any clue what could cause this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rana Sharma over 4 years ago in reply to Björn Ebner

Hi Bjoern Ebner,

Thanks for the feedback.

Sending you PM for more detailing and also some recommendation to try.

Thanks,

Rana Sharma
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Björn Ebner over 4 years ago in reply to Rana Sharma

Are there any updates to this issue?

It is still not working with v18 EAP1 refresh 1.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rfcat_vk over 4 years ago in reply to Björn Ebner

Hi,

you will meed to create an exception in the GUI -> web -> exception page for the moment.

Ian

XG115W - v20 GA - Home

XG on VM 8 - v20 GA

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Björn Ebner over 4 years ago in reply to rfcat_vk

Unfortunatelly even after creating a web exception rule for all my Subnets as source, it doesn't work.

Only after completely disabling TLS/SSL Inspection it starts working.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rfcat_vk over 4 years ago in reply to Björn Ebner

Hi,

have you added an exception to the SSL/TLS groups?

Ian

XG115W - v20 GA - Home

XG on VM 8 - v20 GA

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel