https://netmaker.org logo
Join Discord
Powered by
Client issues
# client
a
@jolly-london-20127 Hello men, in the new release 0.18.5, each client need is own key ? I ask that because, when i join new client (and force sync all node with UI) i can ping other node but after less than 2 minutes > ping stop working. wg command still show me all the other node, what could i do to help you to understand this weird bug ?
j
You are likely experiencing the same issue as other users with our new “endpoint detection”, which may change the address after a couple of minutes. In the wg command, can you see the endpoint change, and does it display private addresses , rather than public ones?
a
i am gonna verify now let me few second :)
@jolly-london-20127 Issue found : ip change for private ip from no where i know, looking close to docker internal ip :) Fresh push :
Good ip

https://cdn.discordapp.com/attachments/1092776808044314634/1092780257230200962/Capture_decran_2023-04-04_a_13.55.41.png▾

can be ping
and good public key (same in wg and in web UI)
After few minute : endpoint change for 172.20.0.1

https://cdn.discordapp.com/attachments/1092776808044314634/1092780532594643004/Capture_decran_2023-04-04_a_13.54.40.png▾

https://cdn.discordapp.com/attachments/1092776808044314634/1092780532884062258/Capture_decran_2023-04-04_a_13.52.45.png▾

https://cdn.discordapp.com/attachments/1092776808044314634/1092780533131513916/Capture_decran_2023-04-04_a_13.53.31.png▾

this is the problem ;)
at least my problem :D
j
I assume that is the docker interface, am I correct?
Can you show me the “ip a” at least for docker?
a
Yep this ip come from docker, no problem wait 1 second ;)

https://cdn.discordapp.com/attachments/1092776808044314634/1092782176581460088/Capture_decran_2023-04-04_a_14.04.22.png▾

172.20.X.X is 5 in the list in the screenshot :)
I am going out of my home, send me message and request for all the thing you need to found the bug :) Stange things : it's append only for one specific node, not other i think
I am trying to force delete manually/etc/netclient and restall the client now, maybe it's gonna help 😅
Ok I am waiting 5 minutes to verify if the problem was that ✌🏻 Very excited to see the new ui in action 😄 I pray for better UX, less click 😄 In futur netmaker gonna have lts release or only latest is supported ?
Nooo :( problems is not solved 🥲 The node continue to get this stupid IP 🥲
j
Can you confirm that 172.20.0.1 goes through docker0?
I believe you can do “ip route 172.20.0.1”
a
What do you mean by docker0 ? Ok I type the command wait
j
docker0 is the name of the interface
a
ip route not working, I am gonna send the you all docker network I have

https://cdn.discordapp.com/attachments/1092776808044314634/1092786179029610656/rn_image_picker_lib_temp_7e77b043-1603-4160-b246-0d85b7b1cc8e.jpg▾

https://cdn.discordapp.com/attachments/1092776808044314634/1092786338849378415/rn_image_picker_lib_temp_19287b44-1913-4c42-939f-a4b166a2bd70.jpg▾

Strange

https://cdn.discordapp.com/attachments/1092776808044314634/1092786732010831942/rn_image_picker_lib_temp_14e8572c-0849-496b-9045-e981c19a5efe.jpg▾

I go out, ask me anything I am here to help the project and testing all the things for you ✌🏻
j
Is this happening with all clients?
And apologies the command is “ip route get 172.20.0.1”
This is the client running in the server I am guessing? If so, this is a known issue, which should have been hotfixed yesterday. When did you install?
a
Ok men I try in few minutes 😄
I am happy to say to you, the patch seems to work fine 😄
@quiet-continent-24852 @jolly-london-20127 Great job 😁😁
PreviousNext
Powered by