Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 1,548
» Latest member: laragargett
» Forum threads: 359
» Forum posts: 2,152

Full Statistics

Online Users
There are currently 40 online users.
» 0 Member(s) | 40 Guest(s)

Latest Threads
Ask the Sky Team
Forum: Questions and Answers
Last Post: skyguy
10-08-2019, 07:58 PM
» Replies: 25
» Views: 10,299
UPDATE: MAINTENANCE WORK ...
Forum: Miscellaneous
Last Post: skyguy
10-07-2019, 07:18 PM
» Replies: 2
» Views: 232
Whitelist shows n/a for a...
Forum: Miscellaneous
Last Post: radarlarry1
10-04-2019, 06:14 AM
» Replies: 0
» Views: 47
Skywire node on Windows
Forum: Skywire
Last Post: skyguy
09-30-2019, 09:02 AM
» Replies: 111
» Views: 37,764
Raspberry Pi Sky Miner Se...
Forum: Skywire
Last Post: 4rchim3d3s
09-14-2019, 12:18 PM
» Replies: 138
» Views: 70,350
Skycoin Whitelisting page
Forum: Skycoin Project
Last Post: radarlarry1
09-12-2019, 04:15 AM
» Replies: 2
» Views: 165
Zealot/Enemy (z-enemy) NV...
Forum: CryptoCurrency
Last Post: Devids
08-21-2019, 08:50 AM
» Replies: 1
» Views: 765
Pi Skyminer Setup brickwa...
Forum: Skywire
Last Post: nodejunky
07-17-2019, 04:19 PM
» Replies: 4
» Views: 420
DIY Skyminer on raspberry...
Forum: Skywire
Last Post: DDunn
07-12-2019, 03:30 PM
» Replies: 3
» Views: 590
Raspberry Pi 4: $35 compu...
Forum: Skywire
Last Post: I Am You
07-11-2019, 09:23 AM
» Replies: 1
» Views: 371

 
  DIY Check your node on OLED display
Posted by: mrtom31 - 05-17-2019, 07:45 PM - Forum: Skywire - Replies (2)

Hello,

I wanted to share the little code I made today.

Description:

It uses the API request to check if your node are connected or not and then it display on OLED ssd1306
It should also support ssd1309, ss1325, ss1331, sh1106 if you substitute the name in the code.



Requirements:

  • And OLED SSD1306 on i2c
  • you need latest luma.oled
  • check if your device is available here
Install

Code:
cd ~
git clone https://github.com/mrtom31/SkyDisplay.git
cd SkyDisplay
echo "MyPasswordSkycoin">secret.txt
Change "MyPasswordSkycoin" by ... I let you guess.

Usage
Check if it works first:
Code:
python OLEDSkycoinDisplay.py

Then use
Code:
crontab -e

to setup a schedule and add those lines:
Code:
* 8 * * * /home/pi/SkyDisplay/OLEDSkycoinDisplay.py
* 19 * * * kill $(cat /home/pi/SkyDisplay/pid.txt)

Replace
Code:
/home/pi
with the location where you cloned the repository.


Tell me if you have any issue.

[Image: giphy.gif]

Also it can scroll automatically with delay if you have lot of node. It doesn't show here since I only have 5 nodes.

Print this item

  go install -> gcc can't allocate
Posted by: mrtom31 - 05-08-2019, 11:50 PM - Forum: Skywire - Replies (1)

Code:
/usr/local/go/pkg/tool/linux_arm64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

github.com/skycoin/skywire/cmd/ssh/sshc
github.com/skycoin/skywire/cmd/ssh/sshs
user@node1:~/go/src/github.com/skycoin/skywire/cmd$ free -h
             total        used        free      shared  buff/cache   available
Mem:           481M         78M        294M        644K        108M        392M
Swap:          240M         63M        176M

user@node1:~/go/src/github.com/skycoin/skywire/cmd$ go version
go version go1.9.2 linux/arm64

Hi,
During go install process gcc can't allocate but I have 13GB free disk space.
Idk what's going on.

Print this item

  ArchlinuxARM on OrangePiPrime + skywire
Posted by: moe_narrow - 05-03-2019, 10:23 PM - Forum: Skywire - No Replies

Perhaps some of you have seen me around on telegram @moe_narrow

I don't get e-mails from skywug so you can contact me on telegram if you have questions.

I would like to document how I created ArchlinuxARM images for the OrangePiPrime
(or the general process which works for other boards)

Once you have archlinux on your board; setting up skywire is trvial because I have submitted PKGBUILD scripts for various skycoin repos to the Archlinux User Repos.
This means that all the hard parts are handled by the AUR package manager (such as yay)
Or you can (in just three steps) build and install the package yourself.

The other, major advantage of archlinux is that you can install a current version of golang with the following command:
```
sudo pacman -S go-pie
```

or

```
sudo pacman -S go
```

It's recommended to use go-pie


CREATING THE IMAGE

The hardest part is getting an archlinuxARM image that will boot on your board. The rest is very easy.
The officially supplied images (for archlinux on orangepiprime) do not work.
Perhaps you might have better luck with by default working images for different boards. 

This method is a bit of a Frankenstein method, but it works (eventually).

To start; take a working image which will boot on your board

For the prime, let's start with this armbian image:
https://dl.armbian.com/orangepiprime/Deb...7z.torrent

And then get the archlinuxARM you want to use:
http://fl.us.mirror.archlinuxarm.org/os/...est.tar.gz


I recommend this one, however with the orangePiPrime it seems that I cannot mount USBs with this.
I will try this with the generic armv7 tarball and see if that fixes the USB issues for the prime.

*EDIT*
There are several sources you can use for archlinuxarm which don't work right or you will later observe have some kind of ip conflict because of mac addresses being the same.
This one didn't seem to be the right one for me with the prime for whatever reason. I am going to link to a working image on github; if you are trying to repeat this process; I have gotten it to work before but I don't recall the correct sources.
*EDIT*

For the next step, I use gnome-disks-utility. You can use something else if you wish.

Extract the armbian image and attach it as a disk image using gnome-disks.
Just so you can see what you are looking at


https://ibb.co/hK8mVdM
https://ibb.co/B3bJm70



next, create a new disk image of the same size. Name it whatever you like


https://ibb.co/R2fndqh
https://ibb.co/dcbzk4X
https://ibb.co/Sv6VPNK

Note the location in `/dev` as shown.

https://ibb.co/sCJ5FV9

then, open up a terminal in the directory where you extracted armbian and execute the following:
```
sudo dcfldd if=Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20.img of=/dev/loop1
```
If you do not have dcfldd you can use dd

Click the triangle 'play' button to mount the root filesystem and follow the link that says 'Mounted at' to view the root filesystem.
Either open a terminal in this location or open a file manager with sudo (sudo thunar, sudo nautilus, etc..) in this location.

https://ibb.co/ZKNq6J8

Remove every folder except /boot. Make sure you check for hidden and trash / lost+found files


https://ibb.co/RS17hVg

Now what you want to do is make a copy of ArchLinuxARM-aarch64-latest.tar.gz or whatever archlinuARM you downloaded.


Open the archive (without extracting it) of the copy you wish to modify and delete the /boot folder.

https://ibb.co/7bGBwSJ


Now, to extract the contents into the mounted disk image that you deleted everything but /boot from

YOU MUST BE ROOT FOR THIS (not with sudo)

```
bsdtar -xpf '/path/to/ArchLinuxARM-aarch64-latest-noboot.tar.gz' -C /path/to/mounted/image/rootfs/131e06c6-00b8-4657-8b48-6e6c806305bb/
```


Now if you have done everything correctly, you can unmount the images and you will have an archlinuxARM image you can write to a microsd and which will hopefully boot on your board.

So I will test what I have to make sure I did it right.

The default user:pass is alarm:alarm and root:root

RESULTS

The board boots, but strangely I could not ssh into it!

This happened before and I fixed it by using a different archlinuxarm rootfs. I forget which one, but I have already made a working image for this board.
The image for this posted already on https://github.com/0pcom/skyalarm in the releases.
I will update soon; in case you don't want to go through this whole process and figure out what is missing. However, the above is still useful for reference.

Here is a (mostly) unconfigured image for the orangepiprime:
https://github.com/0pcom/skyalarm/releas...img.tar.xz
sorry it' so big, there are some makedependancies for still installed. Go and yay are already installed.


INITIAL CONFIGURATION

When you have logged in via ssh, the first thing to do is initialize & populate the pacman keyring (as root)

```
pacman-key --init
pacman-key --populate archlinuxarm
```
then update the keyring

```
pacman -S archlinuxarm-keyring
```
then update the filesystem

```
pacman -Syy
pacman -Syu
```

If you get an error about a key; locally sign the key to trust it

```
pacman-key --lsign DE08F924EEE93832DABC642CA8DC761B1C0C0CFC
```

when your system is up to date and you make a user account; it's time to set up skywire.

But first we need an AUR package manager. And you must be a regular user (not root) for some of the following steps.
A wonderful command-line utility for AUR package management which is written in golang is Y.A.Y. (yet another yaourt aur package manager)

yay should be included in the skyalarm image, but lets's assume for a moment that you don't have yay.
What do you do? Here is the simple 3 step process of making a package from the Archlinux User repos.

```
wget https://aur.archlinux.org/cgit/aur.git/p...UILD?h=yay
mv PKGBUILD?h=yay PKGBUILD
makepkg -scif
```

You will be prompted for the sudo password to install yay, once it is built.

When that has taken place, yay will do what you just did for you (from now on).

To install skywire

```
yay -S skywire
```

I have just today updated the PKGBUILD for skywire to include the system.d services.

```
sudo systemctl start skywire-manager
```
starts the node and manager.

```
sudo systemctl start skywire-node
```

starts a node pointed at 192.168.0.2

If you have a different manager IP address for your DIY setup; edit the script at /usr/bin/skywire-node-miner with the IP address of your manager instance.


BUT WAIT, THERE'S MORE!

```
yay -S skywire-mainnet
```
run a node on the mainnet. After installation with the above command; run the setup with
```
skywire-setup
```

Or, run a skycoin node:

```
yay -S skycoin

```

I have also packaged cx, cxo, and the skywire-discovery server.

UPDATING
For now, the package version for skywire is autogenerated at the time of the build.
To update, simply reinstall the package. You will get the latest commits from either master or mainnet.


CONFIGURING LOCAL PACKAGE REPOS

Something you can do for bootstrapping or to update faster is to make a repository for built packages.
They can be built once and installed on every board rather than having to pull the sources from github and build for each board.

To do this, probably the simplest way, use darkhttpd to serve the directory containing your package repo.
Build the package with one board, then put the built package in that directory. I recommend signing the packages you create; then use the repo-add tool to create your package repo

You can configure pacman.conf to include your repo, take a look at skytergos repo on my github and feel free to message me if you have any questions.

Print this item

  Updating or editing whitelist information
Posted by: radarlarry1 - 04-21-2019, 11:51 PM - Forum: Skywire - Replies (1)

Hello all!  I submitted my whitelist application 4 days ago.  I realize now that I did not enter proper architecture.  I think I just said 7 Orange Pi Primes and I don't think I had a wallet at that time.  I do now though.  Is that part of the whitelist application?  I can't remember.  Anyway, I'd like to be able to edit the info in the application to be more precise.  Even location, I only put Las Vegas, NV... not my address.  Am I correct in thinking that if my nodes are successfully whitelisted, it could not happen prior to 1 June. 2019?
Thanks,
Larry B.

Print this item

  Orange Pi Prime miner issues
Posted by: Radarlarrry - 04-17-2019, 09:05 PM - Forum: Skywire - No Replies

When I checked the monitor this morning, all seven nodes were up.  (One bad OPi)  However, in the STARTED column #7 said 10 hours ago, the rest said 38 minutes ago.  Does this indicate 1 thru 6 rebooted 38 minutes prior?  If so, why only 1-6 and not 7?  Is there an error log somewhere so I can see what happened?  Can I tell how long they were offline?
Now it's done it again, 2 hours ago... all except #7.

P.S. I don't have static IPs set for the Pis. Could this be happening when the addresses change? I would set them, but not exactly sure how to do it. The only info I could find on it is for RPi. I also did not do the port changes, as it seems to work fine on the ports as configured. But, what do I know?

Thanks,
Larry B.
[Image: Skyminer-2.jpg]

[Image: Skyminer3.jpg]

Print this item

  Orange : Pi Zero plus or Pi prime?
Posted by: mrtom31 - 04-13-2019, 05:10 PM - Forum: Skywire - No Replies

Hello fellow skycoinnoisseiur,

I am fairly new to this. I want to know before buying anything. Has anyone tried with Orange Pi Zero plus by following the guide :https://skywug.net/forum/Thread-Orange-Pi-Setup-Guide
and just replacing armbian for prime with zero plus ?

Is it safer to buy orang pi prime instead? (knowing that for 8 node it will be way mor expensive)

Thank you for reply,
mrtom

Print this item

  Practical Instructions
Posted by: FreedomDomains - 04-08-2019, 07:39 PM - Forum: Wireless Antennas - Replies (1)

Does anyone have practical instructions, tutorials, building plans, etc .. that could help new people get their antennas up and running?  I am looking for advice on hardware, software, or anything else as long as it is something you have tried and it worked for you.




Directions for installing the TP-Link AC600 USB wifi adapter on Orange Pi Prime running Armbian OS:  

 These directions include compiling a driver for the USB, and it is very important to make sure you have the EXACT linux-headers
 to match the architecture of your board and OS.  If the correct headers are not available anywhere, I would suggest buying a new
 micro sd card, and installing a version of Armbian that does have the correct headers available.  The instructions start there, but
 if you already have Armbian running and can verify that you will be able to install the correct headers you can skip to step 4.

 It is assumed you have the software tools to format the micro sd, to burn the Armbian image onto the sd, ssh to access the board,
 and 7-zip for windows.  I used a windows laptop to download and burn the image and access the ssh into the Orange Pi, but the directions
 would be similar for other OS's.

1.  Go to:

 https://www.armbian.com/orange-pi-prime

 Scroll down to Armbian Stretch section and click on direct download.  A pop up box will ask if you want to download.
 Check and make sure the name of the file ends in "Debian_stretch_next_4.19.20.7z" The 4.19.20 part is important because the
 version of Armbian that you download must be one that has linux-headers available for download for the EXACT same version.

 Click "ok" in the dialog box, and the file will be saved to your downloads folder (this is a large file, may take a few minutes)

 If you are seeing a version more recent than 4.19.20, cancel the download and go to:

 https://dl.armbian.com/orangepiprime/archive

 locate the link: Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20.7z, double click on it and save it to your downloads folder

2.  Go into download folder and locate the file. RIGHT click on it and a menu will come up.
    Select 7-zip > extract to Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20
    A folder will be created with that LONG name.  Click on the folder and locate a file named       "Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20.img"
  You won't do anything with the file quite yet.  You just want to make sure it is there and you can find it.

3. Open the balenaEtcher software (it should be on your desktop with the "show icon")  Click "select image" Navigate to your downloads
  folder, find "Armbian_5.75_Orangepiprime_Debian_stretch_next_4.19.20.img", select it and click "Open"  Make sure that the second option
  in the balenaEtcher screen shows your micro sd card. If everything looks right, go ahead and click "Flash!"  Insert your mico sd into your   Orange Pi.

4. SSH into your Orange Pi Prime as root. The default root password for Armbian is "1234".  You will need to change that to a password of your choice.

  check running processes to see if Network Manager is on the list:

  root@orangepiprime:~# ps -aux
 
  Network Manager interferes with the proper functioning of the wifi driver you are about to install, so it needs to be disabled.
  First you need to add your "eth0" interface to "/etc/network/interfaces":

  root@orangepiprime:~# cd /etc/network
  root@orangepiprime:/etc/network# cp interfaces interfaces.orig
  root@orangepiprime:/etc/network# nano interfaces

  Inside the file you will see:

  auto lo
  iface lo inet loopback

  That should stay there. If you have specified a static IP for the Orange Pi in your
  router, add this stanza, changing the example IP addresses below to the correct ones:

   auto eth0
   iface eth0 inet static
       address 192.168.1.100 ## [static IP of orange pi]
       netmask 255.255.255.0 ## [this will probably stay the same]
       gateway 192.168.1.1 ## [IP address of your router]
       dns-nameservers 75.75.75.75  ## [the dns that your router uses]

  If your Orange Pi does not have static IP (it is assigned by router dhcp), add this stanza

   auto eth0
   allow-hotplug eth0
   iface eth0 inet dhcp

  Save the file.

  Specify your router DNS server(s) in resolv.conf:
  root@orangepiprime:/etc/network# cd ..
  root@orangepiprime:/etc# cp resolv.conf resolv.conf.orig
  root@orangepiprime:/etc# nano resolv.conf

  Inside that file write:

  search lan
  nameserver 75.75.75.75   ## [the dns that your router uses]

  Save the file

  Now you can disable Network Manager and reboot the board:

  root@orangepiprime:/etc# cd ~
  root@orangepiprime:~# systemctl disable network-manager
  root@orangepiprime:~# shutdown
  You should wait a minute or so, and then go ahead and power recycle the Orange Pi.
  SSH back into the Pi and check to make sure that Network Manager does NOT appear on the list of processes:

  root@orangepiprime:~# ps -aux

5.  You can now install the linux-headers. First check your exact architecture:

  root@orangepiprime:~# uname -a

  the part right after "Linux orangepiprime" should be "4.19.20-sunxi64"

  Update the repositories:

  root@orangepiprime:~# apt-get update  

  Search to make sure that the linux headers you will need are available:
  root@orangepiprime:~# apt-cache search linux-headers
  make sure you find in list:
  linux-headers-next-sunxi64 - Linux kernel headers for 4.19.20-sunxi64 on arm64

  If so, go ahead and install the headers:

  root@orangepiprime:~# apt-get install linux-headers-next-sunxi64

  Go look in /usr/src  now the correct headers should be there:
  root@orangepiprime:~# cd /usr/src
  root@orangepiprime:/usr/src# ls

6. Install some software needed to compile the driver:

   root@orangepiprime:/usr/src# cd ~
   root@orangepiprime:~# apt-get install mercurial bzr libgmp3-dev
   root@orangepiprime:~# apt-get install linux-kbuild-4.19

  The following should be up to date and not need to be installed, but if you want to be sure:
  root@orangepiprime:~# apt-get install binutils bison build-essential curl gcc git make

7. Get the mt7610u driver from github:

  root@orangepiprime:~# git clone https://github.com/FreedomDomains/mt7610u.git

8. Go into the mt7610u folder, copy the Makefile (in case you hose it up) and add a line to specify your symvers file:

  root@orangepiprime:~# cd mt7610u
  root@orangepiprime:~/mt7610u# cp Makefile Makefile.orig
  root@orangepiprime:~/mt7610u# nano Makefile

  Inside the file, scroll down to the "WFLAGS" section (around line 72) and add this line before the WFLAGS declarations:

  KBUILD_EXTRA_SYMBOLS :=/usr/src/linux-headers-4.19.20-sunxi64/Module.symvers  

  Save the file.

  (note that if you have a different architecture, the "linux-headers-4.19.20-sunxi64" part may be different. If in doubt,
   go into "/usr/source" to see the exact name of the directory)

9. Before compiling, the header scripts need to be compiled. Leave current directory and go into headers directory, and
  type "make scripts"

  root@orangepiprime:~/mt7610u# cd ~
  root@orangepiprime:~# cd /usr/src/linux-headers-4.19.20-sunxi64
  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64# make scripts

  If you are using the same architecture I used, you will get some errors including:

  scripts/kconfig/conf  --syncconfig Kconfig
  net/Kconfig:89: can't open file "net/wireguard/Kconfig"
  scripts/kconfig/Makefile:69: recipe for target 'syncconfig' failed

  You need to have Kconfig disregard the wireguard, which is not present. Go to "net" folder, copy Kconfig file (just in case):

  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64# cd net
  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64/net# cp Kconfig Kconfig.orig
  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64/net# nano Kconfig  

  on line 89 comment out:
  ## source "net/wireguard/Kconfig"

  Save file.

   Go back to the main headers folder, and "make scripts" again  (should work this time):

  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64/net# cd ..
  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64# make scripts

10.  Now it's time to go into the mt7610u driver folder and "make":

  root@orangepiprime:/usr/src/linux-headers-4.19.20-sunxi64# cd ~
  root@orangepiprime:~# cd mt7610u
  root@orangepiprime:~/mt7610u# make

  If you get errors about "redeclaration of enumerators, etc ..." that's because "mt7610u/include/rtmp.h"
  has declared variables which are also declared in headers, so those need to be commented out:

  root@orangepiprime:~/mt7610u# cd include
  root@orangepiprime:~/mt7610u/include# cp rtmp.h rtmp.h.orig
  root@orangepiprime:~/mt7610u/include# nano rtmp.h

 inside the file starting around line 5722  comment out this whole enum stanza:

/*  enum ieee80211_radiotap_type {

   IEEE80211_RADIOTAP_TSFT = 0,
   IEEE80211_RADIOTAP_FLAGS = 1,
   IEEE80211_RADIOTAP_RATE = 2,
   IEEE80211_RADIOTAP_CHANNEL = 3,
   IEEE80211_RADIOTAP_FHSS = 4,
   IEEE80211_RADIOTAP_DBM_ANTSIGNAL = 5,
   IEEE80211_RADIOTAP_DBM_ANTNOISE = 6,
   IEEE80211_RADIOTAP_LOCK_QUALITY = 7,
   IEEE80211_RADIOTAP_TX_ATTENUATION = 8,
   IEEE80211_RADIOTAP_DB_TX_ATTENUATION = 9,
   IEEE80211_RADIOTAP_DBM_TX_POWER = 10,
   IEEE80211_RADIOTAP_ANTENNA = 11,
   IEEE80211_RADIOTAP_DB_ANTSIGNAL = 12,
   IEEE80211_RADIOTAP_DB_ANTNOISE = 13

}; */

  Save the file. Go back to "mt7610u" folder and try again (should work this time):

  root@orangepiprime:~/mt7610u/include# cd ..
  root@orangepiprime:~/mt7610u# make
 

11. Install the firmware:
.
  root@orangepiprime:~/mt7610u# make installfw    

 (this will copy the firmware into your "/lib/firmware" directory.  these are the .bin files)

12. Copy the kernel module into the proper directory:

  root@orangepiprime:~/mt7610u# cp mt7610u.ko /lib/modules/4.19.20-sunxi64/kernel/drivers/net/wireless/

13. Enable the module:

  root@orangepiprime:~/mt7610u# cd ~
  root@orangepiprime:~# depmod 4.19.20-sunxi64    
       
14. Time to reboot and go back in:

   root@orangepiprime:/etc/modprobe.d# cd ~
   root@orangepiprime:~# shutdown

   SSH back into board and enable mt7610u:

   root@orangepiprime:~# modprobe mt7610u  
   (IMPORTANT don't add the .ko)

  Check which modules are active:

  root@orangepiprime:~# lsmod

 should show mt7610u in list

15. Get the configuration file in the right place (/etc/Wireless/RT2870STA/RT2870STA.dat):
   Make directories:

   root@orangepiprime:~# cd /etc
   root@orangepiprime:/etc# mkdir Wireless
   root@orangepiprime:/etc# cd Wireless
   root@orangepiprime:/etc/Wireless# mkdir RT2870STA

  Go back to "mt7610u" folder and copy the .dat file into the path you just made:

   root@orangepiprime:/etc/Wireless# cd ~
   root@orangepiprime:~# cd mt7610u
   root@orangepiprime:~/mt7610u# cp RT2870STA.dat /etc/Wireless/RT2870STA/
 
16. Make the config file for wpa_supplicant:

   root@orangepiprime:~/mt7610u# cd ~
   root@orangepiprime:~# cd /etc/wpa_supplicant
   root@orangepiprime:/etc/wpa_supplicant# nano wpa_supplicant.conf

   inside the file write:

   country=US    ## If outside US, use your country two digit code
   ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
   update_config=1

   network={
       ssid="mywifi"    ## use your actual router SSID
       key_mgmt=NONE
mode=0
scan_ssid=1
   }

  Save the file.

17. Shutdown the router:

   root@orangepiprime:/etc/wpa_supplicant# shutdown
   Completely shut off power supply, let the router rest a minute or two, then connect power and SSH back in.

18. Start up wpa_supplicant:

   root@orangepiprime:~# wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf

  you should see the lines:
  wlan0: Trying to associate with 09:00:f0:78:6e:5c (SSID='MyWifi' freq=2462 MHz)
  wlan0: Associated with 09:00:f0:78:6e:5c
  wlan0: CTRL-EVENT-CONNECTED - Connection to 09:00:f0:78:6e:5c completed

The usb stick should light up green

19. Don't do or type anything on this screen (it will break the connection)
   Start a new putty session to connect (or if you use something like Tmux even better)

   From the new session, check the active interfaces:

   root@orangepiprime:~# ifconfig
   
   you should now see the interface "wlan0" besides the "eth0" and "lo"

   Check the active processes to make sure wpa_supplicant is running:

   root@orangepiprime:~# ps -aux

   If you have trouble getting wpa_supplicant running you can add the -dd flag to get debug information:

   wpa_supplicant -dd -Dnl80211 -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf

20. To make sure your Orange Pi Prime is connected to your router wifi, use "iw":

   root@orangepiprime:~# iw dev

   You should see something like:

      You should see something like:

  phy#0
       Interface wlan0
               ifindex 3
               wdev 0x1
               addr f7:de:42:8d:1e:6a
               ssid mywifi
               type managed
               txpower 12.00 dBm

   The "iw" commands can be used to scan and join other hotspots as well as a ton of other functionalities.  
   If you want to learn more, a good place to start is:  

      https://wireless.wiki.kernel.org/en/user...ntation/iw

Print this item

  Second node doesn't connect to master node
Posted by: Stosh15x - 04-08-2019, 12:33 AM - Forum: Skywire - Replies (7)

Hello Everyone,

I am having an issue where my second node will not connect to the master node. When I try to connect the second node there seems to be a conflict and the master node will start to disconnect and reconnect. 

I followed https://skywug.net/forum/Thread-Raspberr...TNET-READY and then realized that the commands to start the nodes were incorrect according to the GitHub so I then used https://github.com/skycoin/skywire as my guide.

I have no issues with the master node running by itself and connecting to it through the web. So I am not quite sure what is going on with the second node. I imagine I am missing something simple but I cannot seem to figure it out through either guides I followed.

Hardware: 
2x Raspberry Pi 3 B+

Network: 
Master Node - 192.168.86.11
Second Node - 192.168.86.12


Masternode Commands:

Code:
nohup $GOPATH/bin/skywire-manager -web-dir ${GOPATH}/src/github.com/skycoin/skywire/static/skywire-manager > /dev/null 2>&1 &sleep 3

nohup $GOPATH/bin/skywire-node -connect-manager -manager-address :5998 -manager-web :8000 -discovery-address discovery.skycoin.net:5999-034b1cd4ebad163e457fb805b3ba43779958bba49f2c5e1e8b062482904bacdb68 -address :5000 -web-port :6001 > /dev/null 2>&1 &cd /

Second Node Commands:

Code:
nohup $GOPATH/bin/skywire-node -connect-manager -manager-address 192.168.86.11:5998 -manager-web 192.168.86.11:8000 -discovery-address discovery.skycoin.net:5999-034b1cd4ebad163e457fb805b3ba43779958bba49f2c5e1e8b062482904bacdb68 -address :5000 -web-port :6001 > /dev/null 2>&1 &cd /

Print this item

Photo Looking for bandwidth donation
Posted by: magicstone1412 - 03-26-2019, 02:22 PM - Forum: Skywire - No Replies

I have opened my miner for community using. But I do not know what the reason is, sometimes my miner drop in connection. Therefore, I worry if the new comers come to my site and wanna try socks 5 features, they can not use it and have a bad impression about skywire. Could someone please open your miner and donate your bandwidth to my site by connecting to duckdns.org and send me your information. I am really appreciate your donation.

Your information will be apprear as the below location on http://www.skywirex.com

[Image: pu5UKwl.png]

Print this item

  DIY Skyminer Using Orange Pi 3 ?
Posted by: Zensublime - 03-01-2019, 08:34 PM - Forum: Questions and Answers - No Replies

Im new to building a Skyminer myself.
I came across a post explaining how to make your own Skyminer using the same orange pi Prime boards used in the official Skyminer.
My question is, Would I be at much of an advantage going with the newer orange pi 3 ? Is the software installs the same?
The specs are a bit better on the 3, and only around $6 more for each.
Id like my build to be a little more future proof if possible.
I haven't been able to find any information regarding this.
I appreciate your time in advance!

Print this item