I have a file server running debian 10 using iptables. Contected is 4 windows 10 desktops with microsoft access database front ends. The tables are stored on a map drive on windows 10 which points to a shared folder where the tables are stored on the file server.
All works how it should and no problems.
I have built a new testing server with debian 11 bullseye using nftables. It is the excact same setup but the only difference is nftables. I first tried it using iptables but it didnt work. Had the same problem that follows. The 4 desktops connect ok to the map drive and can read tables ok. If one desktop makes a change to a text field the changes show up on all other machines. If another machine makes a change to the same field same record it shows the change on the two other machines but the first machine that made the orginal change the new edit doesnt show. I can reload the records from the start and all changes are shown correctly. I know from past experience that this alone means the database is not working correctly. Every field is unbound to the database and only when you make a change to the field it writes back to tables and the change is made in the tables correctly.
I had this problem when I tried to update to bulleyes when first released. I re-installed buster debian 10 as it works there with no problems. I now have more time to investigate and to find out why this happens.
I have now created a table that logs any updates on any field in each record. this is timestamped and the user who made the change and logs old data. When I make a change all logs are correct and the database table shows correct data.
This now makes me think its a cache problem. I cant understand why it works with iptables and buster but not with nftables and bullseye.
Has anyone any views on this. I just seem to be going round and round in circles.