Hi !
I have search the forum and I couldn't find my answer... so here is my current situation.
There will be a lots of questions ... and it will get complex. Brace yourself ;) But I need help !
We currently have 7 nodes on our current network.
Two nodes are remote ( 16 km away ) but they can reach my QTH.
From my QTH, I can't connect very well to a node on a commercial tower which is 1.5 km from my QTH ... they had put a nanostation and aimed it to the city ... so I'm behind the antenna.
Since I already had a network home covering some neighbors, I did just installed a picostation at the commercial tower and aimed it to my QTH ... and then I was able to have access to my private network from the commercial tower.
At my QTH, my node have 10.0.0.1 IP and 172.20.0.100 ( LAN IP ). At the commercial tower, we have 10.0.0.10 and 172.20.0.200 ( LAN IP ).
Link between commercial tower and my qth is 150 Mbps made with a picostation and my bullet at home. My network is on 172.20.0.x so internet is accessible through 172.20.0.1 but I have filtering enabled there.
First situation: I am NOT able to use DTDlink between the two nodes even if they are on same network .... so my guess is that the picostation and the bullet does not share the VLAN information (?) ... so that lead me to the second situation :
Second : I installed a tunnel server at my QTH on 10.0.0.1 and it ip is 172.31.31.1 ( LAN IP is 172.20.0.100 ). I installed a tunnel client on the commercial tower and connected both stations together.
In mesh status, I can see all stations ... but I can't connect to all of them.
Routing : from the station at 16 KM from my QTH ... he is connected on WLAN so he can browse my internal network from his QTH. But from another station in town, which is connected to the commercial tower, we can't browse my network. I don't know if the routing problem is related to the tunnel or to the fact I have an intermittent connection on WLAN from my QTH to the commercial tower ... which maybe mess up with the routing table ?
Also, from the commercial tower, I can't ping 10.0.0.1 ... but I can ping 172.20.0.100 ( I did log in with SSH on the tower and was able to ping the LAN ip ). From a computer behind a node that is connected to that tower, I can't ping either.
Any idea of what I can look into ?
I draw a picture but I can't put it into this message yet... trying to figure that out.
73
VE9MDB - Matt
I have search the forum and I couldn't find my answer... so here is my current situation.
There will be a lots of questions ... and it will get complex. Brace yourself ;) But I need help !
We currently have 7 nodes on our current network.
Two nodes are remote ( 16 km away ) but they can reach my QTH.
From my QTH, I can't connect very well to a node on a commercial tower which is 1.5 km from my QTH ... they had put a nanostation and aimed it to the city ... so I'm behind the antenna.
Since I already had a network home covering some neighbors, I did just installed a picostation at the commercial tower and aimed it to my QTH ... and then I was able to have access to my private network from the commercial tower.
At my QTH, my node have 10.0.0.1 IP and 172.20.0.100 ( LAN IP ). At the commercial tower, we have 10.0.0.10 and 172.20.0.200 ( LAN IP ).
Link between commercial tower and my qth is 150 Mbps made with a picostation and my bullet at home. My network is on 172.20.0.x so internet is accessible through 172.20.0.1 but I have filtering enabled there.
First situation: I am NOT able to use DTDlink between the two nodes even if they are on same network .... so my guess is that the picostation and the bullet does not share the VLAN information (?) ... so that lead me to the second situation :
Second : I installed a tunnel server at my QTH on 10.0.0.1 and it ip is 172.31.31.1 ( LAN IP is 172.20.0.100 ). I installed a tunnel client on the commercial tower and connected both stations together.
In mesh status, I can see all stations ... but I can't connect to all of them.
Routing : from the station at 16 KM from my QTH ... he is connected on WLAN so he can browse my internal network from his QTH. But from another station in town, which is connected to the commercial tower, we can't browse my network. I don't know if the routing problem is related to the tunnel or to the fact I have an intermittent connection on WLAN from my QTH to the commercial tower ... which maybe mess up with the routing table ?
Also, from the commercial tower, I can't ping 10.0.0.1 ... but I can ping 172.20.0.100 ( I did log in with SSH on the tower and was able to ping the LAN ip ). From a computer behind a node that is connected to that tower, I can't ping either.
Any idea of what I can look into ?
I draw a picture but I can't put it into this message yet... trying to figure that out.
73
VE9MDB - Matt
73
VE9MDB
Hi Matthieu,
Why are you not letting AREDN assign these node addresses? Letting AREDN deal with network parameters will greatly simplify this and ensure routing and feature support.
Andre, K6AH
Onto your first question: using a 172.20.*.* Lan means you are in NAT MODE.
Computers on a node in NAT mode can not be directly reached, if you want to directly connect to a PC that computer should be on a node in DIRECT mode and will have a 10.x.y.z IP address.
After that you likely do not have routing setup in your local network with your existing router to forward 10.x.y.z to the mesh node. This is an advanced routing setup and is a bit much to go into. You can reach the mesh node because it's on the same network (172.20.0.x ) but the rest are remote and need routing tables. In addition you also may not have DNS in this setup.
I suggest start simple, be in direct mode and directly attach to the node and work out from there on complex routing setups.