I have an GL-MV1000 and an AXT1800 with booth same issues.
The address range connected to the Lan ports or wlan of the MV1000 is 10.0.0.0/24
My home network is 192.168.10.0/24 with 192.168.10.1 as gateway
I also have a zerotier network running 172.26.0.0/24
All Clients (TV, SAT receiver, laptops etc) connected to my MV1000 should not use the “normal” gateway 192.168.10.1 instead of that I want them to 172.26.0.23 as the gateway to the www.
Any idea how i forward 10.0.0.x to 172.26.0.23?
I already tried ip route add … but this is not help because this descries the gateway to destination, what i would need is source to gateway
I can not use a VPN because on my home site i have ipv4 and the destination has ipv6
thanks a lot
root@GL-MV1000:/etc/config# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 wan
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan
10.10.10.0 172.26.0.23 255.255.255.0 UG 0 0 0 ztly56vpaa
172.26.0.0 0.0.0.0 255.255.0.0 U 0 0 0 ztly56vpaa
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 wan
10.10.10.0/24 is my 2nd home where it should be connected to
Zerotier is the ztly56vpaa interface
My problem is i do not know how to forward everything form the 10.0.0.0/24 and gateway via 172.26.0.23 into the 10.10.10.0/24 network - the reason for that is that all devices from 10.0.0.0/ and 10.10.10.0/24 should have the same address when they are in the internet
I can ping all 10.10.10.0/24 clients
root@GL-MV1000:~# traceroute 10.10.10.1
traceroute to 10.10.10.1 (10.10.10.1), 30 hops max, 46 byte packets
1 172.26.0.23 (172.26.0.23) 68.176 ms 71.820 ms 72.284 ms
2 10.10.10.1 (10.10.10.1) 71.392 ms 73.297 ms 75.303 ms
this configuration has no public IP address
I can ping the WG server address 10.10.10.172 from my WG client
After connecting them without any information that they are connected the ping does not work anymore
Is there a log file i can view to see why they are not connecting?
I saw on my AXT1800 is a log file:
Thu Nov 3 09:13:13 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Thu Nov 3 09:13:45 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Nov 3 09:13:51 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Nov 3 09:13:56 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
and I get the message time out in response please check network or reboot…
I rebooted a several times.
client is starting please wait… nothing happens