 | 1 | initial version |
https://developers.google.com/web/ilt/pwa/introduction-to-push-notifications
Chrome currently uses Firebase Cloud Messaging (FCM) as its push service. FCM recently adopted the Web Push protocol. FCM is the successor to Google Cloud Messaging (GCM) and supports the same functionality and more.
https://firebase.google.com/docs/cloud-messaging/concept-options
If your organization has a firewall to restrict traffic to or from the Internet, you need to configure it to allow mobile devices to connect with FCM in order for devices on your network to receive messages. FCM typically uses port 5228, but it sometimes uses 5229 and 5230.
The traffic is probably encrypted so not what you will get if setting decode to TLS for port 5228
You can map the port number to "google" by setting up a personal "services" files:
https://www.wireshark.org/docs/man-pages/wireshark.html
Name Resolution (services)
The services file is used to translate port numbers into names. Both the global services file and personal services files are used if they exist.
The file has the standard services file syntax; each line contains one (service) name and one transport identifier separated by white space. The transport identifier includes one port number and one transport protocol name (typically tcp, udp, or sctp) separated by a /.
An example is:
mydns 5045/udp # My own Domain Name Server mydns 5045/tcp # My own Domain Name Server
Put your custom "services" file in the folder pointed to by Help->About->Folders: Personal Configuration
| | 2 | No.2 Revision |
https://developers.google.com/web/ilt/pwa/introduction-to-push-notifications
Chrome currently uses Firebase Cloud Messaging (FCM) as its push service. FCM recently adopted the Web Push protocol. FCM is the successor to Google Cloud Messaging (GCM) and supports the same functionality and more.
https://firebase.google.com/docs/cloud-messaging/concept-options
If your organization has a firewall to restrict traffic to or from the Internet, you need to configure it to allow mobile devices to connect with FCM in order for devices on your network to receive messages. FCM typically uses port 5228, but it sometimes uses 5229 and 5230.
The traffic is probably encrypted so not what you will get if setting decode to TLS for port 5228
You can map the port number to "google" by setting up a personal "services" files:
https://www.wireshark.org/docs/man-pages/wireshark.html
Name Resolution (services)
The services file is used to translate port numbers into names. Both the global services file and personal services files are used if they exist.
The file has the standard services file syntax; each line contains one (service) name and one transport identifier separated by white space. The transport identifier includes one port number and one transport protocol name (typically tcp, udp, or sctp) separated by a /.
An example is:
mydns 5045/udp # My own Domain Name Server mydns 5045/tcp # My own Domain Name Server
Put your custom "services" file in the folder pointed to by Help->About->Folders: Personal ConfigurationConfiguration
My services file for testing:
google 5228/tcp # Google Cloud/Firebase messaging