-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not getting through. #117
Comments
Yes the other peers are only on the mesh net. You can reach them only via another cjdns node (e.g. your main node). There is a feature in cjdns called iptunnel, which allows for your mesh-only node to access internet through another internet-connected node that functions as a gateway. We will soon incorporate that into the prototype script, but @darkdrgn2k is currently running a gateway, maybe he can give details on how to hop on if you want to test.
Feel free to hop on to https://chat.tomesh.net/#/room/#tomesh:tomesh.net for support questions. |
As @benhylau mentioned there is "INTERNET" on CJDNS. CJDNS has its own "INTERNET" called hyperborea that is currently mostly peered over the internet ( see http://fc00.org ) You need to find some one to peer with thats already connected. There is the "illusion" of internet by the use of the ACCESS POINT but all that does it provide you with internet through your existing internet bypassing CJDNS altogether. This illusion breaks the second you unplug your internet from the node. To actually get route your internet to your node over CJDNS you have to use IPTUNNEL that will "tunnel" the internet over CJDNS to your node. This requires a SERVER/CLIENT setup similar to a VPN. This is done as usually there is a COST associated with the internet and you don't want just anyone using your pipe! Server Side (node that HAS internet) in your cjdroute.conf
Next restart your cjdroute once restarted you need to config your server with a NAT, ROUTE and IP ADDRESS
NOTE you must run the above each time cjdroute starts so you may want to add it to your /etc/rc.local CLIENT SIDE again in cjdroute
then restart your cjdroute (killall cjdroute) and if you do an ifconfig you should see tun0 get the ip address assigned to it in the server And you now have interent access on your node |
So that was the DIY solution. If your already peered to hyperborea and want quick internet access come by let us know ill show you how to connect to my test node :) |
@paappraiser For example, you can have the "main" node with internet act as a server. Then the other nodes can be iptunnel clients, by pinning the gateway server address as @darkdrgn2k described. Now if you have
That tells the nat to stop routing through |
Excellent write up!.. ill keep you updated. |
@paappraiser any update on this issue? |
Hi- Sorry for the lack of update. I ordered a bunch of compatible wifi modules from China and they just came in the other week. I will be working on this again |
Perhaps the writeup can be moved to some sort of general docs folder and the issue closed? |
Question answered. |
Fresh install stretch.
All nodes and peers communicate to each other perfectly. Connect to main node connected to LAN(internet) internet is connected and fine. Connect to any other peer and no internet.
Been running into problems with stretch.
Do I have to turn off "WITH_WIFI_AP" on the peers?
Sorry if noob question, wifi is my nemesis.
The text was updated successfully, but these errors were encountered: