Bug/Feature and v6 update

As you all know, when you add a user to the G2 database, the local gateway selects an IP address that is unique for that base callsign and sends that to the Trust Server.

So, I have had some issues with adding users due to duplicate IP addresses, but this has been really exercising me as in my database the IP address was clear. What I've found is that deleting users from G2 is a two-step process - the user is flagged for deletion and then at some point in the future when all gateways are synced, the user is purged.

Big problem - in the current trust network, the gateways are never really in-sync. So where I'd been pulling callsigns out and re-using IP addresses immediately, I now flag them with a deleted flag instead.

v6 tests progress very well. The code looks very stable - running on Ubuntu 9.10 on an EEE 901 PC and a pair of Tait radio modemes quite happily.

I've been able to change the USB routines to deal in 12-bytes as high-speed USB supports longer data frames, and this means that I can now link the outgoing buffer to the incoming buffer much more accurately. The net effect is that I have been able to reduce the time-lag through the repeater and nearly eliminate the transmit overhang on local repeat.

David

v6 Beta

So I received my v6 Beta PIC from Satoshi (thank you !) two days ago, plugged it in and it worked as expected from day one.

I've now modified my code (releater 0.985) so that it recognises whether it is attached to a v4 or a v5/6 board - the main reason for this is that on v5 and v6 I use S/N rather than COS. I've also included a new value in the .cfg file that allows you to set the S/N trigger level.

The next stage will be to investigate having two v6 boards connected to the same gateway.