GitHub-Mirror/tomeshnet-prototype-cjdns-pi
1
0
Fork 0
mirror of https://github.com/tomeshnet/prototype-cjdns-pi synced 2025-10-05 23:52:49 +02:00
Code Issues Releases Wiki Activity
Files
master
tomeshnet-prototype-cjdns-pi/docs/TROUBLESHOOT.md
darkdrgn2k 799c91a45f [WIP] - New release v0.5.0-rc.1 to master (#390) 
Yggdrasil IPTunnel now does not change config files
    Yggdrasil IPtunnel drop in service adjustment
    Yggdrsail IPTunnel supports IPv6 and routed IPv6
    Yggdrsail version bump
    Support for x86 and x64
    Profile selection menu format changed in Dialog
    Rewritten and simplified board detection
    IPFS Improvments #284
    CJDNS now module
    Prototype can run without CJDNS now
    Better docs
    Grafan database now can be removed when uninstalling
    Moved network config to interface.d model
    Removed Network Manager
    Added Modules.md
    Added confSet function and implemented confget/confset config files
    NodeJS now shared module
    NodeJS version bump
    MESH_NAME now a config
    Added ipv6 netcat option
    Localized Patch Foo in TOMESH repo to prevent version conflicts and outage
    Added support for PI4
    Added support for Buster
    Fixed ETH0 vs BR0 issue on espressoBIN
    Prometheus version bump
    Raspberry Pi Watch Dog Timer
2020-03-26 13:55:24 -04:00

2.9 KiB
Raw Permalink Blame History

Wireless Meshing

Below are a few things you should look at when diagnosing connections. These can help identify bad configurations or other errors.

IBSS

  • iw dev - do all the devices have matching BSSID and Channels
  • iw wlan0 station dump does it show stations
    • If they do then the peering between nodes is working
    • If they do not show up, this may just mean the drive does not report properly. For example the onboard Pi driver will not yield any results
  • sudo /usr/bin/mesh-adhoc - does it return any errors
    • If yes run sudo bash -x /usr/bin/mesh-adhoc - Thiw will help identify where the error occurs
  • If you set an IP address on wlan0 on both sides, can it ping in the clear
    • On Pi-1 run ifconfig wlan0 10.10.10.1/24
    • On Pi-2 run ifconfig wlan0 10.10.10.2/24
    • On Pi-1 run ping 10.10.10.1
    • On Pi-2 run ping 10.10.10.2
    • Does it say request timeout or does the ping succeed?

Mesh Point

  • iw dev - do all the devices have matching BSSID and Channels
  • cat /usr/bin/mesh-mesh - does the JOIN line have the correct mesh name
  • iw wlan0 station dump - does it show the stations
  • sudo /usr/bin/mesh-point - does it return any errors
    • If es run sudo bash -x /usr/bin/mesh-point - - This will help identify where the error occurs
  • If you set an IP address on wlan0 on both sides, can it ping in the clear
    • On Pi-1 run ifconfig wlan0 10.10.10.1/24
    • On Pi-2 run ifconfig wlan0 10.10.10.2/24
    • On Pi-1 run ping 10.10.10.1
    • On Pi-2 run ping 10.10.10.2
    • Does it say request timeout or does the ping succeed?

IPTunnel - Internet Exit Over Yggdrasil/CJDNS

  • Can client node ping CJDNS/Yggdsaill address of exit node
  • Can the exit node access the internet
  • Can the client node ping an IP address (not DNS)
    • IE: ping 1.1.1.1

IPTUNNEL - cjdns

  • Is IPTunnel installed (/usr/local/sbin/cjdns-setup exists)
  • Is the cjdns.iptunnel.server/client filename correct and on the correct device
  • Are the keys correct (ends in a k)
  • Does tun0 have an IPv4 IP address on server
  • Does tun0 have an IPv4 address on client
  • Can you ping the IPv4 addresses across the tunnel
  • Does the MASQUERADE line in iptables -L -v -n -t nat exist
  • Does MASQUERADE line in iptables -L -v -n -t nat show the right out interface

IPTUNNEL - yggdrasil

  • Is IPTunnel installed (/usr/local/sbin/yggdrasil-setup exists)
  • Is the yggdrasil.iptunnel.server/client filename correct and on the correct device
  • Are the keys correct (64 character alpha numeric)
  • Does ygg0 have IPv4 address on client
  • Can you ping the IPv4 addresses from the server
  • Does MASQUERADE line in iptables -L -v -n -t nat exist
  • Does masquerade line in iptables -L -v -n -t nat show the right out interface
  • check if routes have been added to yggdrasil
    • sudo yggdrasilctl getsourcesubnets - should be all your routes
    • sudo yggdrasilctl getroutes - should be 0.0.0.0 and ::/0