ESP8266-Sensor
/
SBNetwork
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
SBNetwork/src/SBNetwork_config.h

25 lines
539 B
C
Raw Normal View History

Added sources, library properties and example code.
2017-11-20 16:54:06 +01:00
#ifndef _SB_NETWORK_CONFIG_
#define _SB_NETWORK_CONFIG_
Changed the library to not use AutoAcknowledge so that an analysis of the network can not be done by a simple trying to ping a device/master. The master must be paired to a device before he sends any ACK package or must enable new slaves to answer to a MASTER_SEARCH Request. The AutoAcknowledge feature would automatically send an ACK package which makes the master and any other device directly visible. Be aware that this feature does not prevent a devices for being detected by sniffing the radio traffic, because the normal data traffic is still there and not encrypted in any way. An Encryption would hide the sender address. This would make it again more difficult to copy a sender address and simulate a paired device. (This is stikk possible now). But again, this will come later, maybe! The best solution is to implement an encryption feature at a higher communication layer.
2017-12-15 13:55:09 +01:00
// Generates details debug messages about sending and receiving data packages
Removed self made ack handling. Now it seems to work very stable.
2018-02-11 14:14:40 +01:00
changed on pairing stuff
2019-04-17 21:41:37 +02:00
#define _DEBUG
Added sources, library properties and example code.
2017-11-20 16:54:06 +01:00
Changed the library to not use AutoAcknowledge so that an analysis of the network can not be done by a simple trying to ping a device/master. The master must be paired to a device before he sends any ACK package or must enable new slaves to answer to a MASTER_SEARCH Request. The AutoAcknowledge feature would automatically send an ACK package which makes the master and any other device directly visible. Be aware that this feature does not prevent a devices for being detected by sniffing the radio traffic, because the normal data traffic is still there and not encrypted in any way. An Encryption would hide the sender address. This would make it again more difficult to copy a sender address and simulate a paired device. (This is stikk possible now). But again, this will come later, maybe! The best solution is to implement an encryption feature at a higher communication layer.
2017-12-15 13:55:09 +01:00
// All slaves will ping the master every xxx milliseconds. if set to 0, they will not ping the master
#define MASTER_CHECK_INTERVAL 0
Added sources, library properties and example code.
2017-11-20 16:54:06 +01:00
#define MAX_CLIENTS 10
Changed the library to not use AutoAcknowledge so that an analysis of the network can not be done by a simple trying to ping a device/master. The master must be paired to a device before he sends any ACK package or must enable new slaves to answer to a MASTER_SEARCH Request. The AutoAcknowledge feature would automatically send an ACK package which makes the master and any other device directly visible. Be aware that this feature does not prevent a devices for being detected by sniffing the radio traffic, because the normal data traffic is still there and not encrypted in any way. An Encryption would hide the sender address. This would make it again more difficult to copy a sender address and simulate a paired device. (This is stikk possible now). But again, this will come later, maybe! The best solution is to implement an encryption feature at a higher communication layer.
2017-12-15 13:55:09 +01:00
#define CLIENT_TIMEOUT 60000
changed on pairing stuff
2019-04-17 21:41:37 +02:00
#define CONNECT_TIMEOUT 10000
Removed self made ack handling. Now it seems to work very stable.
2018-02-11 14:14:40 +01:00
// Milliseconds to wait for fragmented packages
changed on pairing stuff
2019-04-17 21:41:37 +02:00
#define FRAGMENT_TIMEOUT 150
Added sources, library properties and example code.
2017-11-20 16:54:06 +01:00
Removed self made ack handling. Now it seems to work very stable.
2018-02-11 14:14:40 +01:00
// Milliseconds to wait between two fragment sendings
changed on pairing stuff
2019-04-17 21:41:37 +02:00
#define FRAGMENT_DELAY 20
Did some changes in ping process. A ping now must get an answer from the destination device, otherwise the ping returns false. The master device now must be available and must know the device as a slave before it answers with a return ping. This prevents a slave to send data to master but the master doesn't know the slave (maybe because of a reset). This makes finding errors much easier than before.
2017-12-14 23:38:46 +01:00
Added sources, library properties and example code.
2017-11-20 16:54:06 +01:00
#endif