https://netmaker.org logo
Powered by
Anyone else experienced issues with MacOS clients ...
# netmaker
r
Anyone else experienced issues with MacOS clients with two networks? On netclient daemon start I get only one net up and I need to manually wg-quick it to get the other one up.
m
Can you provide configs via PM/DM?
r
Sorry I missed you reply. Which files do you need?
my setup seems to be confusing utun8 and utun9 for example between the two networks. now its jumped to utun10 for one network and left utun8 free...
m
well, first what steps did you follow to join both networks?
Also which version(s) (client and server)?
(I just confirmed am able to join 2 networks on mac, ping another node on both networks (the other node is on both networks too), have the node ping the mac on both networks; then left and rejoined both networks on mac and repeated, still worked). this is with 0.16.1 clients talking with the upcoming prerelease on the server.
r
ok ill check and redo the steps you did next time Im physically next to the system. One think I remember not working for me as ping both IPs of the macos system (one per network). So maybe I need to remove the nets and start over.
@totoro ~> ping 10.200.200.120 (base) PING 10.200.200.120 (10.200.200.120): 56 data bytes 64 bytes from 10.200.200.120: icmp_seq=0 ttl=62 time=21.091 ms 64 bytes from 10.200.200.120: icmp_seq=1 ttl=62 time=22.563 ms ^C --- 10.200.200.120 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 21.091/21.827/22.563/0.736 ms @totoro ~> ping 10.210.210.120 (base) PING 10.210.210.120 (10.210.210.120): 56 data bytes Request timeout for icmp_seq 0 ^C --- 10.210.210.120 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss
yeap didnt work
10 Views
PreviousNext
Powered by