Ahhh I see what you're saying, it's for return traffic

correct

did you do any testing adding the rule to your own gateways?

my network now works because I manually added this iptable rule on my egress gateway

I however did not build the code of netmaker

I'm not a go developer :D

adding the rule manually is a sufficient test for this, I think it looks good

fresh Install v0.12.0: Added Egress-Gateway to a node: 192.168.11.0/24 docker exec -it netmaker route on the Server does not show it:

@User bug?

Hmmm not sure. It did not cause any server logs? Also, can you test with a non-server node to see if it picks up the route?

How to check on the server logs? How to test with non-server node? Sadly don't have that much nodes connected right now. Only the one that is in the same 11.0/24 Network. Edit: Egress Gateway is not pushed to Windows Client either. Allowed IPs stays the same. ACL (blocking) did work so a communication is there. but it is added to: docker exec -it netmaker wg show peer: +D+5ilSNWJEFe1qh2kakc6Di1bSaL2jlX+8ty3cHdRM= endpoint: 94.100.XX.XXX:57009 allowed ips: 10.9.1.1/32, 192.168.11.0/24 latest handshake: 1 minute, 28 seconds ago transfer: 222.45 KiB received, 75.00 KiB sent persistent keepalive: every 20 seconds But still not to docker exec -it netmaker route

Thanks for all the info @User , we're aware of the issue and should have it fixed in the next patch

hey all, does anybody have a HOW TO BUILD guide? im trying to help test the fix for server slow interface up but cant work out how to build? - https://github.com/gravitl/netmaker/tree/issue-954-attempted-hotfix

are you familiar with docker builds?

to a degree, i use compose alot

although i am just realising i think i need linux env not my windows env haha

if you have the repo locally, you can run "docker build -t ." from the root of the directory to build the server image

then docker-compose down, change the tag in the compose file, and docker-compose up -d

its the client app im testing for the devs

ooooh

in that case you need to install golang

and then just run "go build" from the netclient directory

and away the build goes haha, thanks!

and its finished building, haha, thanks!

np, make sure you're building on the same OS you intend to run on. If not, there are some flags you must add to build for a target environment/cpu