Referring to the below image.
Devices within the mesh network 10.9.177.x can see/access devices within the 172.22.18.x. However, devices within the 172.22.18.x cannot see/access devices within the 10.9.177.x. I know its a routing issue.
Is there a way to set up routing so that devices within the 172.22.18.x can see/access devices within the 10.9.177.x without using port forwarding?
--
Bob, W7REJ
You are here
Node LAN to Home LAN Connectivity
Sun, 01/08/2017 - 22:29
#1
Node LAN to Home LAN Connectivity
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
I understand the original question? and there is not a simple answer... only a few things to think about.
1 do computers on your lan need to access to specific servers on your mesh lan? If so then you can setup port forwarding on your mesh gateway/node and foreword the specific ports. Then you have access.
2 Ive never heard of some one successfully (not saying someone has done it) Adding default routes to your home router.may or may not be possible. If your router for 172.0.0.0 is open wrt based you should not have problems setting it up.ip based routes betwen LAN and MESH LAN. YOu will have to setup DNS to use the mesh name space. Thisis a unique setup and configuration your your hardware. NAT is not best suited to do this.
I just keep 2 Ethernet cables by my laptop, and when I need to work on the mesh i plug in. Other wise I monitor my gateway's status page of my LAN.
I'm not totally inept regarding computers and networking (DNS, etc.). I already know the node's address is W7REJ-Base01 and I already know what the IP address and I already tried just the IP address and port. I'm fully aware that the web gui links me to the olsrd status page based on the DNS name of the node. The only difference in the address bar is the port number. (w7rej-base01.local.mesh:8080 vs w7rej-base01.local.mesh:1978). It stands to reason that if I can get to the node interface using its name and port 8080 that I should be able to get to the OLSR page using 1978 with port forwarding set and the ports open in my workstation's firewall.
You said "do computers on your lan need to access to specific servers on your mesh lan? If so then you can setup port forwarding on your mesh gateway/node and foreword the specific ports. Then you have access." Did I not say "Ok, set port forwarding and I can now get to the node interface and to the collectd-web on the linux box"? I think that means I already know about and have set port forwarding.
I'm just looking for any explanations as to why I can get to the main node on port 8080 but can't get to the OLSR page on port 1978 when both ports are forwarded and I have the ports open in Windows firewall on my work station. Maybe I'm a little lazy and want the convenience of being able to get to the node interface from my workstation without taking my laptop to the node.
If anyone has a helpful response to that specific question it would be appreciated.
--
Bob, W7REJ
--
Bob, W7REJ
The simple explanation to why you can get to the node:8080 and not the node:1978 is that the node's firewall is restricting access to port 1978 from the WAN interface.
to temporarily test this:
go to the node and execute: /etc/init.d/firewall stop
try to access via your node's wan:1978
go to the node and execute: /etc/init.d/firewall start
try to access via your node's wan:1978
(port 8080 is explicitly allowed over the WAN interface in the firewall rules)
--
Bob, W7REJ
Hello Bob, I also have a Mikrotik router. I setup my Aredn node LAN to give out 5 DHCP address. (10.38.204.113) Configured a 2nd port on the Mikrotik for DHCP. Mikrotik IP>DHCP Clint> Add a new DHCP for the port you want. I'm using TWC on port 1 WAN. Aredn on port 9. So I have 2 WAN ports. You need to change the Default Route Distance to greater then 2 on the port for Aredn. My LAN (Home) network uses a DNSMASQ dns server on the LAN. That points to the Mikrotik router that uses the Aredn node's dns server. Now when I lookup a local.mesh address it all works. I'll play around with the DNS. "port forwarding" at a later time.
Ports
1) WAN TWC (DHCP)
2-5) LAN1 Switched (192.168.10.0/23)
6-8) LAN2 Switched (192.168.20.0/24)
9-10) Aredn Switched DHCP (10.38.204.113/29)
9) Default Route Distance to greater then 2. Checked Use Peer DNS
MikroTik will add the 10.0.0.0/8 to the routing table automatically.
Play with the firewall rules. So Aredn can't access your LAN work.
David
KE6UPI