development
- s
straight-lock-3524
08/28/2021, 10:55 PManything above that well error out but not tell you that your name is too long - s
straight-lock-3524
08/28/2021, 10:56 PMsame with your node name, anything with a - will give you an error, even while every default name is based on a name with a - 🙂 - q
quiet-continent-24852
08/29/2021, 11:53 AMHaha, yeah I think after our large refactor for 0.7 we over simplified some of the valid character checks with naming, we should probably address that soon though - q
quiet-continent-24852
08/29/2021, 11:55 AMI think 16 was the max for some OS we saw, hence why we tried to keep it shorter - q
quiet-continent-24852
08/29/2021, 11:56 AMBut we should probably allow dashes and/or have better error messages in a future release - s
straight-lock-3524
08/29/2021, 1:38 PMindeed, because the naming is driving me nuts a little bit 😛 - v
victorious-optician-32228
08/29/2021, 6:54 PMYes error handling could be better i guess. For example: i know that Nodes must be empty before deleting a network. Otherwise it will throw a regular error. But many don't know the cause. I think this happens on many error-messages. - s
straight-lock-3524
08/29/2021, 7:13 PMindeed - s
straight-lock-3524
08/29/2021, 7:13 PManyone tested it on a aws lightsail yet? - j
jolly-london-20127
08/29/2021, 8:51 PM@straight-lock-3524 the name limit is because of the max characters allowed for network interfaces on Linux - s
straight-lock-3524
08/29/2021, 8:51 PMah - s
straight-lock-3524
08/29/2021, 8:51 PMI already thought it was something like that 😉 - j
jolly-london-20127
09/01/2021, 6:57 PM@everyone anyone got Windows development / golang experience and would be down to check out an issue we're facing with development? - s
straight-lock-3524
09/01/2021, 8:27 PMI think hole punching needs a lot of work still, I needed to disable it now as well, with it enabled I had 2 hosts not being able to reach each other - b
bored-island-21407
09/01/2021, 8:51 PMCheck my avatar 🤣 - j
jolly-london-20127
09/01/2021, 8:55 PMAny info on the 2 hosts where it’s not working? - j
jolly-london-20127
09/01/2021, 8:56 PMIn general I would expect it to have problems on super restrictive firewalls - j
jolly-london-20127
09/01/2021, 8:57 PMAnd apparently Oracle VPS’s - s
straight-lock-3524
09/01/2021, 9:16 PMthis wasn't an oracle vps haha since I'm not giving them anything of me 😛 - s
straight-lock-3524
09/01/2021, 9:16 PMHetzner vps and a host behind a 4G machine - s
straight-lock-3524
09/01/2021, 9:16 PMwhat info you need? - j
jolly-london-20127
09/01/2021, 9:31 PMAhhhhh we had another user with issues on Hetzner a while back as well. 4G routers can also cause issues due to double nats. But those both worked for you without UDP hole punching? - s
straight-lock-3524
09/01/2021, 10:34 PMyep - s
straight-lock-3524
09/01/2021, 10:34 PMfirst try - s
straight-lock-3524
09/01/2021, 10:35 PMI actually have a public ip on my 4g haha - j
jolly-london-20127
09/01/2021, 11:20 PMHmmm that’s interesting. The problems I saw on those machines before were without UDP hole punching - j
jolly-london-20127
09/01/2021, 11:20 PMDid you happen to check firewall configuration? - s
straight-lock-3524
09/01/2021, 11:56 PMthe server has only a docker firewall, the 4G one I need to check if I can see that (router is 4g one with custom firmware from the isp) - p
purple-restaurant-77209
09/02/2021, 7:30 AMLittle info about my experience with UDP whole punching. Oracle cloud VM behind oracle firewall(single firewall) doesn't connect other nodes if that behind a firewall too. My raspberry pi behind router+ISP firewall doesn't work without UDP whole punching. The summary is, UDP whole punching needed for double firewall & no UDP whole punching for single firewall. - s
straight-lock-3524
09/02/2021, 8:32 AMSo you have double nat on your raspberry?