Jump to content

Alexey

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Alexey got a reaction from lanefu in Passing configuration to docker build   
    No more questions  Just fixed BOARD_NAME in /etc/armbian-release, motd now displays correct name.

    PS. great job guys, userpatches concept is just great. Working firmware for the new board in 2 days - that took me 6 months before with Buildroot.
  2. Like
    Alexey got a reaction from lanefu in Passing configuration to docker build   
    Ok, original issue is fixed. I had BOARD_NAME instead of BOARD in my userpatches config. Now ./compile docker myconfig works.

    Thanks a lot, but with the network issue I think I can find a workaround with some little hint from you.

    Actually, what I'm trying to achieve is customizing image. I copied config/boards/lime2.conf  to config/boards/myboard.conf,  renamed the BOARD_NAME="MyBoard" to change the default hostname. BOARDFAMILY and BOOTCONFIG are the same as for Lime2,  it is the nearest compatible board, original Lime2 build works fine.  The desired image should include some pre-installed stuff (Node.js 10x, my app,  dependencies),  I did it with customize-image.sh.  Now setting BOARD=myboard creates the image I need, with the changed hostname and preinstalled software, but the network does not work.  Obviously, some patches are BOARD  -depended, not the board family. Workaround is leaving BOARD as is, and renaming the host in customize-image.sh script.  And here I need a hint - hostnamectl does not work in build time, what is the better approach? 

      
  3. Like
    Alexey got a reaction from TRS-80 in [Solved] Node/npm WebRTC/Webtorrent not working   
    Hi there, 
    after days of researching I have finally found what caused the issue. 
    Checked if STUN is working with my NAT - works fine  (stunclient --mode=full stun.stunprotocol.org reports success).
    Checked if arm7 version of webrtc library is installed ("export TARGET_ARCH=arm" before npm install).
    Compared the debug output of webtorrent (DEBUG=bittorrent-tracker:client webtorrent) of working and non-working setups. Bingo! WebSocketTracker output was missing on malfunctioning system. After analyzing the source code, realized that the only reason why it may happen is different behavior of API functions. Yes, outdated Node.js.
    Solution is upgrade to Node.js 10.0+ as shown here:
    https://joshtronic.com/2018/05/08/how-to-install-nodejs-10-on-ubuntu-1804-lts/

    After upgrade i can seed files with streaming webtorrent, works as a charm. 
     
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines