It had this failure with Linux x64 and Windows10 x64 (dual boot), so I checked badip.txt again and found it on the Hub. Deleted it and added 10.0.* to the goodip.txt and whitelist.txt (so it won't happen again)
and then polling worked. So Invalid data frame can be the result of badup.txt or blacklist.txt, if your getting them have the hub feeding
you checked for your IP in badip.txt and blacklist.txt and have them put in goodip.txt and whitelist.txt and the problem shouldn't appear again.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 14:02:44 |
Calls: | 2,094 |
Calls today: | 1 |
Files: | 11,141 |
Messages: | 949,411 |