v1.7.2stable

This release is focusing on Ethernet fixes and additions, but is adding also functionality for servers and bridges:

for ETH.h based Ethernet boards (like the WT32-ETH01) now a separate ModbusServerETH.h was created that is to be used instead of ModbusServerEthernet.h for these boards.
The older special Ethernet library by @maxgerhardt was removed. eModbus now uses the standard Ethernet library instead
The ModbusServers now are supporting ANY_SERVER as a server ID to register a worker to. There are clients in the wild that seem to be using the server ID to signal stuff to servers. WARNING: servers registering ANY_SERVER workers will get all requests, especially on RTU, that not necessarily are meant for them. Note that workers explicitly registered to a certain server ID/function code combination always will have precedence before the ANY_SERVER workers.
Bridges now can have filtering functions for all requests and/or responses coming through the bridge. Hence you may manipulate both requests and responses to cope with different capabilities of the requesting clients or the servers responding.
Note to all users of Platformio: please be sure to add lib_ldf_mode = deep+ to your platformio.ini to avoid building problems with the Ethernet modules.

This release is focusing on Ethernet fixes and additions, but is adding also functionality for servers and bridges:

for ETH.h based Ethernet boards (like the WT32-ETH01) now a separate ModbusServerETH.h was created that is to be used instead of ModbusServerEthernet.h for these boards.
The older special Ethernet library by @maxgerhardt was removed. eModbus now uses the standard Ethernet library instead
The ModbusServers now are supporting ANY_SERVER as a server ID to register a worker to. There are clients in the wild that seem to be using the server ID to signal stuff to servers. WARNING: servers registering ANY_SERVER workers will get all requests, especially on RTU, that not necessarily are meant for them. Note that workers explicitly registered to a certain server ID/function code combination always will have precedence before the ANY_SERVER workers.
Bridges now can have filtering functions for all requests and/or responses coming through the bridge. Hence you may manipulate both requests and responses to cope with different capabilities of the requesting clients or the servers responding.
Note to all users of Platformio: please be sure to add lib_ldf_mode = deep+ to your platformio.ini to avoid building problems with the Ethernet modules.

eModbus