When I tried it again after adjusting the size of the IP pool and so on, IP reusing seems working as I expected.
However, I found that IP release was sometimes failed.
IP address which wasn’t released wouldn’t return to the pool even after the UE begin to use new one.
When this happens, following error log is seen in AMF logs.
[ERRO][AMF][GMM][AMF_UE_NGAP_ID:1] state mismatch: receieve gmm message[message type 0x45] at Deregistered state
Is there any way to release the IP address, and make it reusable?
I tried to find the cause of this error from message type, but I couldn’t find it.
If there are dynamic ip left in the ip pool, it will be .1, .2, .3 in order, and when it is used up, it will allocate the smallest of the released ip.
For example, there are only 60.60.0.1 and 60.60.0.2 in the ip pool. If 60.60.0.1 is released, the next time will be allocated 60.60.0.2 when it is connected , if 60.60.0.2 is released, and it will be allocated 60.60.0.1 when it is connected again.
Please give the entire log and pcap so that we can debug more easily , thanks.
From 60.60.0.1 to 60.60.0.6, IP address release was succeeded as I expected.
But 60.60.0.7 seems not released and it didn’t return to the IP Pool.
I guessed so since the pool information is diveded .