This may be normal, but>>>>

I have one NS5 setup as the gateway on my MESH, that node is connected to a NS2 via vlans defined on 108t switch. The switch is connected to my home lan. Both of these nodes can access the internet. The NS5 also has the VPN coded added from K5DLQ, not used yet.

I added a Rocket5, it see the MESH and displays the status. I can navigate to the other nodes. It does not have internet access, even though the NS5 is a gateway.

Is this the new norm, or do I need to fix something??? If it is normal, is there a way around it?

Happy 2015

73 de Mike/K3MMB

Please reset the gateway node without any additions (VPN code) and try agaim please. This can be done by flashing the node OR by holding the reset button for 15 seconds.

I know the VPN code has progressed a lot and is looking good, but it is still a work in progress. It therefore would be helpful to see if the issue exists without changes from the official build, If the issue exists still when gateway does not have the VPN code we can look at it further, otherwise if it does work after a fresh flash it is likely a VPN code issue and Darryl would be best equipped to work with you to solve the issue.

Thanks Conrad,

I reset the NS5 stripping VPN code. No difference. The two stations connected via the 108T switch still have access to the internet. The NS5 connected over the MESH can only access the other nodes. I tried two different netbooks (1 windows and one Linux) but no workie with internet.

73 de Mike K3MMB

Well since we ruled out the VPN code it comes down to running the steps:

1) What Version of the mesh firemware?

2) On the remote node have you configured a static IP for the WAN interface as this could interrupt the routing when the interface is not plugged in.

3) On your remote node what does it show for Default Gateway on the mesh status screen?

4) On your remote node olsr status screen do you see a route for 0.0.0.0?

(if you don't see the above we can stop here)

4) Running a traceroute from a PC plugged in to the remote node what is the path ? Does it die out a specific node or location?

Those questions should give is a good starting point to look at what is going on and figure it out from there. 

1) What Version of the mesh firmware? Current Production V3

2) On the remote node have you configured a static IP for the WAN interface as this could interrupt the routing when the interface is not plugged in. Negative

3) On your remote node what does it show for Default Gateway on the mesh status screen? None

4) On your remote node olsr status screen do you see a route for 0.0.0.0?Search all screens found no route to 0.0.0.0 ---- route not found on other nodes either, but the NS5 and NS4 connected through the switch has the home network gateway IP listed.

(if you don't see the above we can stop here)

4) Running a traceroute from a PC plugged in to the remote node what is the path ? Does it die out a specific node or location?

Hope this helps

73 de Mike/K3MMB

Ok, sounds like the gateway node isn't advertising the route.

The obvious question at this point is to be sure Mesh Gateway is checked on the gateway node and it's been saved and restarted.

After that it usually is because the Internet is unreachable, but could be because some filtering is in place Between your gateway  node and the Internet. Log in (telnet or ssh if directly connected) to the gateway node and try pinging the following addresses:

71.42.236.91

71.42.236.90

8.8.8.8

8.8.4.4

if none of them respond than either the node doesn't have Internet access or some filtering is blocking pings, in either case that would cause the route not to actually be advertised over the mesh. 

If you do get a ping response than check /etc/config/olsr on the gateway node and be sure it has the olsr_dyn_gw plugin listed (it should if mesh GW is checked on the gateway node)

Tried the pings... did not work config.olsr was correct, 

this configuration of comcast firewall was in place

Typical Security (Medium)

Glad it works now.

i don't see anything in what is listed that says why it would of been blocked but I'm guessing it is a rule they did not mention in the list.

I'll add that to my mental notes about Comcast routers.

Sometime it is just evil

the comcast modem model is Model: TG862G

System software is eMTA & DOCSIS Software Version: 7.6.86L

I left the IP six security set high, so the change only was for IP4

Hope this will help in the future.

now I have bricked another node... I will post it in another topic... how could you have more fun that this?????

73 de Mike/K3MMB