«jool_siit --eamt» failing with «Error code: 3»; entries missing from output

toreanderson commented 7 years ago

I know for a fact that there is an EAMT entry for 87.238.60.1/32 2a02:c0:400:17::2/128 installed on this Jool node. It is working fine too, I can ping 87.238.60.1 through the Jool node without issues and so on.

However it doesn't show up in output from jool_siit --eamt. Plenty of other EAMs does show up in its output though. So either it is only 87.238.60.1/32 2a02:c0:400:17::2/128 that is missing, or if there are others, it's not many.

root@sdbr1-osl2:~# jool_siit --eamt | egrep '(87.238.60.1|2a02:c0:400:17::2)/'
Jool Error: 
(Error code: 3)

This trips up our provisioning systems since it compares the output from jool_siit --eamt with its database, trying to add/remove EAMs to make the former match the latter. Essentially it ends up trying to do this, which fails:

root@sdbr1-osl2:~# jool_siit --eamt --add 87.238.60.1 2a02:c0:400:17::2
Jool Error: The requested entry already exists.

(Error code: 17)

I see this on two Jool nodes running 21b97b1e4fd29676ae3dd6800dc3286c70dd0690 as well as one running v3.5.2. Identical config on all three.

ydahhrk commented 7 years ago

~~Is this two bugs in one? You said that some entries are showing up, but the output you posted is a flat error.~~

~~I managed to reproduce the "flat error" part by trying to print a very large EAMT, but I'm still trying to reproduce the entry skipping-part.~~

Edit: Never mind; found it.

ydahhrk commented 7 years ago

Fix ready, I believe. Please test.

e6afbda patches the version you're using. e9a3991 patches Jool 3.5.4.

toreanderson commented 7 years ago

Confirmed; e9a3991 doesn't exhibit the problem. Thank you!

ydahhrk commented 6 years ago

3.5.5 released; closing.

NICMx / Jool

«jool_siit --eamt» failing with «Error code: 3»; entries missing from output #249