Schneider Electric support forum about Protection Relays, Substation Controllers & RTUs, Arc Flash Devices & Systems in Medium Voltage and Low Voltage. A place to get support on product selection, installation, commissioning and troubleshooting.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2021-08-2708:35 AM
Easergy T300 Firewall
Hi,
I have a T300 configuration that configures a T300 to be a Modbus master to a series of P3 relays over TCP. The T300 is turn is a DNP3 slave to a PSO 2020 system over TCP.
I am trying to decide how to configure a white list for the T300 firewall for the WAN interface. Does the white list only control incoming connections to the T300 (in which case I guess I only need to include the IP addresses for the PSO servers) or does it filter all incoming packets (in which case I guess I need to include the P3 relay IP addresses in the white list as well)?
As you said it is a WAN interface configuration, which means the rules will be applied to every packet arriving at the WAN physical interface.
The option you have is to connect the P3 into the LAN interface as following:
However, I cannot answer it without giving you this advice: Please avoid using Modbus as much as possible. the T300 and the P· have better protocols (Protocols with time-stamp as a minimum) to do this integration.
You could use DNP3.0 or IEC61850-MMS for the downstream communication with P3.