lampra

Members
  • Content Count

    73
  • Joined

  • Last visited

About lampra

  • Rank
    Advanced Member

Recent Profile Visitors

706 profile views
  1. Just updated to v5.73 and no handshakes are reported from wireguard though the connections are up and running. Does anyone else experiences the same issue? root@cubietruck:~# systemctl status wg-quick@wg0 ● wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0 Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2019-01-30 00:34:12 EET; 1h 34min ago Docs: man:wg-quick(8) man:wg(8) https://www.wireguard.com/ https://www.wireguard.com/quickstart/ https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8 Process: 1034 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, status=0/SUCCESS) Main PID: 1034 (code=exited, status=0/SUCCESS) Jan 30 00:34:05 cubietruck systemd[1]: Starting WireGuard via wg-quick(8) for wg0... Jan 30 00:34:09 cubietruck wg-quick[1034]: [#] ip link add wg0 type wireguard Jan 30 00:34:09 cubietruck wg-quick[1034]: [#] wg setconf wg0 /dev/fd/63 Jan 30 00:34:09 cubietruck wg-quick[1034]: [#] ip address add 10.200.200.1/24 dev wg0 Jan 30 00:34:10 cubietruck wg-quick[1034]: [#] ip link set mtu 1420 up dev wg0 Jan 30 00:34:12 cubietruck systemd[1]: Started WireGuard via wg-quick(8) for wg0. root@cubietruck:~# wg interface: wg0 public key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX= private key: (hidden) listening port: XXXXXX peer: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX= endpoint: XXX.XXX.XXX.XXX:XXXXXX allowed ips: 10.200.200.11/32 transfer: 10.84 KiB received, 10.79 KiB sent persistent keepalive: every 24 seconds peer: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX= endpoint: XXX.XXX.XXX.XXX:XXXXXX allowed ips: 10.200.200.4/32 transfer: 2.23 KiB received, 804 B sent persistent keepalive: every 24 seconds peer: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX= endpoint: XXX.XXX.XXX.XXX:XXXXXX allowed ips: 10.200.200.3/32 transfer: 1.19 KiB received, 3.20 KiB sent persistent keepalive: every 24 seconds root@cubietruck:~# wg show wg0 latest-handshakes XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX= 0 YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY= 0 ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= 0
  2. lampra

    VPN Server Questions

    You could simply use systemctrl stop ethervpn (i think thats the service name check with top or htop) and then systemctrl disable ethervpn and that is it. If you want to completely wipe the installation then go to /user/local and delete the vpnserver folder and also delete the /etc/init.d/vpnserver file and you are done!
  3. lampra

    Remote reboot with ssh unresponsive

    ok thank you. By the way, On a similar installation on cubietruck I see that kernel sysrq(-trigger) is not present. Do you know if this is the intended kernel build behaviour?
  4. lampra

    Remote reboot with ssh unresponsive

    No, i use telnet just to check that port 22 is open
  5. Hi, Updated to 5.70 next on Opi pc and after 2 days I cant login via ssh and i get: ssh_exchange_identification: Connection closed by remote host Some times ssh login just hangs. As I am not near the machine, is there any way to remotely reboot the Opi pc without ssh access? ps: I am sure that the machine is working as wireguard is working fine and I can ping the machine as well as telnet port 22!
  6. lampra

    Installation of Wireguard

    I don't know why, but I had similar issues with wireguard on cubietruck and on opi pc. It was mostly a matter of headers in my case. Even with armbian config I was not able to install the headers some times and on other occasions DKMS was not able to install wireguard. My workarounds are: 1. check manually apt (eg apt-cache search linux-headers-xxxx) for the correct header package (stable or next or whatever) for your board and kernel from armbian repo and manually install them. Then try to install wireguard with dkms. 2. If this does not work, install the headers, get the source of wireguard (check the wireguard webpage for manual installation) make & and make install and this should work even if you encounter erros during make. This is really trivial, just two commands as root!!
  7. Hi, I have a quectel ec 20 4g modem and I want to install it on espressobin. There seems to be some low cost solderless products like this or this. Is there any suggestion for SIM Card adapter?
  8. lampra

    EspressoBIN - static IP address

    I recently came across the same issue with systemd-resolved after upgrading an old laptop to bionic. I just disabled systemd-resolved and installed unbound. Maybe this is bionic specific (works fine on debian stretch for me).
  9. Well the module is compiled and installation finishes but when I am trying to use wireguard it fails and the output seems to point to wrong or missing kernel headers # wg-quick up wg0 [#] ip link add wg0 type wireguard RTNETLINK answers: Operation not supported Unable to access interface: Protocol not supported What i noticed is that after installation, a new folder is created in /lib/modules/ where wireguard.ko is placed $ ls /lib/modules/ 4.17.7 4.17.7-mvebu64 $ ls /lib/modules/4.17.7/extra/ wireguard.ko
  10. Compilation from source also not working:
  11. Am I missing something? I tried to install wireguard in the prebuild images but i failed using the linux-headers-next-mvebu64 package. Today I compiled a mainline image with headers installed but I still fail to install wireguard. Here is the log I have read in this that we need to call make scripts. Here is the output Edit: Diagnostics
  12. lampra

    EspressoBIN - static IP address

    Did you stop network-manager and checked the /etc/network/interfaces file contents? what is the output of these commands:
  13. lampra

    EspressoBIN - static IP address

    Well, rather than nano you can use vi witch works for me when connecting with minicom (ubuntu) from the usb.
  14. lampra

    EspressoBIN - static IP address

    networkctl is telling you that there is no br0 so this will not work. In the eth0 file is there something wrong? or this is because of copy & paste? lines 1-17/17 (END) lines 1-17/17 (END) * Make sure that the contents of the files and the files in /etc/systemd/network/ are exactly as in my previous post * Remove all the .txt files from /etc/systemd/network/ (You could also start from a fresh install and only change the contents of the 10-br0.network file) * Stop, disable and remove NetworkManager (systemctl stop NetworkManager && systemctl stop NetworkManager-wait-online && systemctl disable NetworkManager && systemctl disable NetworkManager-wait-online && apt remove --purge network-manager && apt autoremove) * use systemd-resolved for name resolution (systemctl enable systemd-resolved && ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf) Ejoy!! Edit: make sure that the /etc/network/interfaces file contents are exactly these: auto lo iface lo inet loopback
  15. lampra

    EspressoBIN - static IP address

    By the way, for your tests you can have an 99-failover.network file with dhcp settings for the bridge in the /etc/systemd/network/ folder so if everything else fails, you will at least obtain an ip from the dhcp server (so no need to plug in the usb)