Getting an odd error tonight

[Corey Koval]

Last year I used the software pretty flawlessly. This year my club is using the same version as last year (since there is not newer official release). It started off petty well, however I stopped receiving updates  from other machines and my terminal outputs the same error over and over endlessly.

error, send_udp failed 150628.053209 (22, 'Invalid argument') [172.16.0.207]

req fill ('172.16.0.207', 'kb3zvn', 39)

Any idea why this is happening? What can I do to resolve it?

73,

Corey, K3CPK

[Alan Biocca]

Restart fdlog, it is having a network problem

--
You received this message because you are subscribed to the Google Groups "HS-FDLog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fdlog+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Corey Koval]

Unfortunately restarting on all machines did not solve this problem. I may just have to sync them up on a different network later on this evening.

I did notice the two windows machines are happy talking to each other. I am running linux. Earlier in the event all the machines were talking to mine just fine, but mine would not talk to them. Now I am just seeing that error, and I can see what bands people are on, however the logs are not propagating across to my box. 

[Alan Biocca]

Ok. Fdlog is not being allowed to send to the network on your box for some reason. It is receiving however. Os reboot, reconnect to net, etc may be needed

[Alan Biocca]

Probably is a network security setting, python needs sending privelige.

[Scott Hibbs]

I got a similar error today '22, invalid argument'... Mine was because Linux Mint was assigning a loopback. Your's is assigning a Class B private address (172.16.0.0 to 172.31.255.255).

I think I got a fix. It could be the netmask. The program automatically assigns the netmask as 255.255.255.0 (which is for class c 192.168) then looks to see if your on a Class A private address (10.x.x.x) and if so it assigns the standard netmask for class A which is 255.0.0.0. The standard netmask for Class B (172.16-31.x.x) is 255.255.0.0, but the program uses 255.255.255.0. This would explain why you could see some of your network traffic and not all. 

I'll make this change in FDLog_Enhanced but I have no way of testing it. 

Scott

[Alan Biocca]

We always ran FDLOG in the field on a local wifi net, so no problems with an 8 bit netmask.

To unsubscribe from this group and stop receiving emails from it, send an email to fdlog+unsubscribe@googlegroups.com.

[Scott Hibbs]

The correct netmask for 172 private networks is 255.240.0.0. I have made the correction in a beta copy of the Enhanced_FDLog project. It will be in it's next release before FD 2019. 

[Alan Biocca]

Good work.