the point is even some clients they only want to allow http traffic and only on 443

thats the reason why we need websockets 😦

I know it breaks all the magic of wireguard

but is the only way to bypass this super restrictive FW

interesting issue

have in mind I talking about pharma industry

some stupid burocracy and policians

I would talk to @User if this is something a lot of companies need/is feasible, we may roadmap it

Can anybody install netclient on OpenWRT?

Thanks. I tried another way that pulled the source code of netmaker and build it. It runs properly but OpenWRT does not have wg-quick, which is required by netmaker. Did you meet the same problem?

I did a testsetup today, so the quick-start-script on a public-ip server and then a node on linux in my home network that I made an egress-node and made the netmaker-server an ingress-gw. Then put in the ext-clients dns an IP of an DNS-server in my home network. Then made an external client, put that config on my ios-device and tried. So far all working well. I can ping the DNS-server in my homenet from the iphone. The WG-config states the DNS-server. However looking at the logs of the coredns-docker all dns-requests go there and not to the specified dns-server. I tried to read about that and here in the discord was somewhere sth. mentioned it's because the ext. clients are NATed. But I don't know if that's really the problem. I don't get exactly why the requests go to the coredns-container even if an other dns-server is specified.

because we are not using wg-quick to set the DNS for peers as it is works differently on different distributions. The dns in netmaker is there to enable finding the wg ip address of a peer using node.network . this is so you can do

ping node.network

vice

ping <wireguard ip address of peer>

but the ext client dns-setting goes into the ext. clients config. And if wireguard on IOS shows the DNS-ip, how are the requests from IOS going to the coredns-container? I would've thought they a) go elsewhere and IOS ignores the setting or b) I won't get answers if IOS couldn't reach the specified DNS. But not finding the requests in the coredns-container.

is maybe on the netmaker-node some iptables-magic going on that the dns-requests go to the coredns-container if it's the ingress point?

yes, that's how we're doing it

the netmaker server does iptables forwarding from 53 on the wireguard interface to 53 on the coredns container

that explains it then, thanks!

Ok, I'll do more testing then and try out, now that I know where I can look for.

Hello guys, sorry can't find anything on the topic in the GitHub Repository. Is there an possibility so sign in via SSO (e.g. Keycloak etc?)

not yet, only oauth

ok thx. But if Oauth is supported then Keycloak should work right?

currently oauth is only for azure, github, and google

just saw it in the docs, thanks for clarifying though

hopefully it will be integrated in the future 🙂 just love the local hosting of an auth provider

Can older version like 0.8.5 of netclient connect to the server running 0.10.0 netmaker?

No, data structures are not compatible

OK, thanks. I found that netclient which version over 0.8.5 will use wg-quick instead of wg command to configure network. But OpenWRT doesn't have wg-quick command. So I need to use older version.

If wq-quick is not available a v0.10 client will still work

OK, I will try v0.10 again.