https://netmaker.org logo
Join Discord
Powered by
hm is netclient able to join 2 different netmaker ...
# client
g
hm is netclient able to join 2 different netmaker networks? I have no matching address on this node and it still fails to add address to a new NIC (I already have a wg nic peered on netmaker)
j
remember to keep convos in threads
g
sorry
weird as it's not a server w/ an overlapping range 🤔
Copy code
# ip r|rg 10.215.97
# ip a|rg 10.215.97
#
i'm using netclient w/ 0.14.0 (both client & server side)
j
What error do you get while joining?
g
I have no overlapping network on this node
j
did you join previously and it failed?
it might have failed to clean up an existing interface
check "wg show"
g
hm
j
to see if it already exists
g
no nm-mesh here
I see my other network, w/ its peers
b
what is output of 
ip a
j
do "ip a"
the addres 10.227.44.1 must be present on one of your existing interfaces
g
Copy code
root@rasp4:~] 1 # ip a show nm-netmaker
22: nm-netmaker: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none 
    inet 192.168.15.2/32 scope global nm-netmaker
       valid_lft forever preferred_lft forever
[root@rasp4:~] # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:9f:ac:09 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.43/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::dea6:32ff:fe9f:ac09/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether dc:a6:32:9f:ac:0a brd ff:ff:ff:ff:ff:ff
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/none 
    inet 192.168.10.6 peer 192.168.10.5/32 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::b965:9323:69bf:165f/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
22: nm-netmaker: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none 
    inet 192.168.15.2/32 scope global nm-netmaker
       valid_lft forever preferred_lft forever
nope
this is why I found this error quite awkward
j
what OS?
g
raspbian
j
hmmmm, maybe wireguard acts weird on raspbian...I haven't done any testing on that OS
g
😬
that's weird as it's supposed to be a debian with some decorators
but indeed, maybe a "more than a decorator" feature as been added on the networking stack
j
is nm-skynet.conf still present under /etc/netclient/config?
if so, try running "wg-quick up" manually, to see what happens
g
nope no skynet
b
pi3 or pi4?
g
pi4 !
I have a 192.168.1.0/24 range for my lan, a 192.168.10.0/24 for my tun0 (openvpn) and a 192.168.15.0/24 for my first netmaker network. I tried w/ both 192.168.16.0/24 & 10.215.97.0/24 resulting in the same outcome
b
ok, just joined two networks on pi4 --- no issues
j
i would create an "ext client", download the config to the pi, and run "wg-quick up" to see if you experience the same issue
this sounds like a system issue with wireguard rather than netmaker. The logs shown are linux commands being executed on the host
actually you could try to execute the following without a config file:
Copy code
ip link add nm-skynet type wireguard
ip -4 address add 10.222.44.1 dev nm-skynet
ip link set mtu 1280 up dev nm-skynet
and see if you get the same error
@glamorous-crowd-4515 I replicated your issue and have the solution
We will have a fix in the next release, but for now, you need to just set the port while joining
the error is because you have the same default port on both networks (im guessing 51821), and the node is attempting to use that port in the second network, but it is unavailable
A bit of code is supposed to change that port if it's blocked but it got messed up in a release. So for now just do "netclient join -t --port=51822"
g
oh neato thanks @jolly-london-20127 !
c
It appears that 
netclient daemon
is only checking for updates to one of the two clients. Use the dashboard of one of the servers to modify the 
Listen Port
of the corresponding client; 
netclient daemon
will make that change on the client. Then use the dashboard of the other server to modify the 
Listen Port
of the other client; 
netclient daemon
will not be make that change on the client but 
netclient pull
will.
j
have not encountered this yet, but there is a known issue where if you attach to 2 different servers, and one breaks, the daemon will stop working for both. Are the two networks on the same server or different servers?
c
That is Issue #862 which I posted and was trying to retest with v0.14.0. I encountered this new behavior with two networks, each on a different server that is hosted on a different node.
j
ok, to confirm, this issue is when you have two separate servers for each network? I haven't encountered this with a single server + multiple networks for a single client
c
My test configuration has three machines and two networks: network TEST1 served by VPS1, network TEST2 served by VPS2, and a client node on VPS3 that has joined networks TEST1 and TEST2.
j
Can netclient join 2 different networks?
PreviousNext
Powered by