I’m using a wildcard cert from letsencrypt. Currently there is only one way how to verify that you hold the domain you are requesting cert for: creating TXT record in that domain. You can do it by hand when asked by certbot but you don’t want to do this each 90 days. If you are running your own DNS servers with PowerDNS like me there’s an elegant solution: RFC2136. This allows you to update your zones without writing config files and restarting anything.
Show git log as tree
$ git log --oneline --graph --decorate --all | * 0255f78c (HEAD -> qmtech, my/qmtech) added support for qm_xc6slx16_sdram board | * dae037cf (my/spisingle, spisingle) added spi 1-bit mode, code from litex |/ * 1325aff6 (origin/master, origin/HEAD, master) correctly use result of Record.connect in Converter (#81)
$ git rebase --onto master spisingle qmtech First, rewinding head to replay your work on top of it... Applying: added support for qm_xc6slx16_sdram board $ git log --oneline --graph --decorate --all * 37d2eff0 (HEAD -> qmtech) added support for qm_xc6slx16_sdram board | * 0255f78c (my/qmtech) added support for qm_xc6slx16_sdram board | * dae037cf (my/spisingle, spisingle) added spi 1-bit mode, code from litex |/ * 1325aff6 (origin/master, origin/HEAD, master) correctly use result of Record.connect in Converter (#81)
Push changed branch
$ git push my qmtech -f Counting objects: 7, done. Delta compression using up to 12 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 1.86 KiB | 1.86 MiB/s, done. Total 7 (delta 5), reused 0 (delta 0) remote: Resolving deltas: 100% (5/5), completed with 5 local objects. To https://github.com/danielkucera/misoc.git + 0255f78c...37d2eff0 qmtech -> qmtech (forced update) $ git log --oneline --graph --decorate --all * 37d2eff0 (HEAD -> qmtech, my/qmtech) added support for qm_xc6slx16_sdram board | * dae037cf (my/spisingle, spisingle) added spi 1-bit mode, code from litex |/ * 1325aff6 (origin/master, origin/HEAD, master) correctly use result of Record.connect in Converter (#81)
If you are dealing with network monitoring, you might consider using SMSes because they are completely independent. On the other hand, many monitoring systems don’t support HTTP calls (which is the usual way for sending them) but most of them support sending e-mails. Here I want to describe how to configure your server to receive e-mails and transform them to SMSes. Continue reading E-mail to SMS
My USB 3.0 to VGA adapter arrived a few days ago so I tested the FM transmission example. Continue reading FM transmission test with FL2000
Nothing special, just use undocumented command sh and you are there (I found it out by a mistake):
danman@silverhorse:~$ nmap 10.0.0.138 Starting Nmap 7.60 ( https://nmap.org ) at 2018-03-26 22:54 CEST Nmap scan report for 10.0.0.138 Host is up (0.013s latency). Not shown: 996 closed ports PORT STATE SERVICE 21/tcp open ftp 22/tcp open ssh 23/tcp open telnet 80/tcp open http Nmap done: 1 IP address (1 host up) scanned in 3.14 seconds danman@silverhorse:~$ telnet 10.0.0.138 Trying 10.0.0.138... Connected to 10.0.0.138. Escape character is '^]'. ZyXEL VDSL Router Login: admin Password: admin > help ? help logout exit quit reboot adsl xdslctl xtm brctl cat loglevel logdest virtualserver ddns df dumpcfg dumpmdm meminfo psp kill dumpsysinfo dnsproxy syslog echo ifconfig ping ps pwd sntp snmp sysinfo tftp wlctl arp defaultgateway dhcpserver dhcpcondserv dns lan lanhosts passwd ppp restoredefault route save swversion uptime cfgupdate swupdate exitOnIdle wan rip igmp wlan telnetd natp sysstate sipalgctl celld autoexec fileShare igmp btt ledctl > sh shell Password: admin ~ # ls bin etc linuxrc proc tmp vmlinux.lz data firmware mnt sbin usr webs dev lib opt sys var
If your pod exited with exit code 137 so you see something like this in pod Details page:
Last State Terminated at Jan 7, 2018 5:00:15 PM with exit code 137 (Error)
your pod has been killed with signal 9. Continue reading Openshift: exit code 137
If you tried to add node to your etcd cluster and it failed, your cluster may have lost quorum and will not start again. To recover it you need to create new cluster identity. This is a short howto. Continue reading How to recover containerized etcd in Openshift cluster
Together with some good guys we added support for Kimax U25AWF-H1 WiFi HDD case to LEDE. You can see my pull request here and commit here. This firmware also works on my Blueendless U-35WF. If you have this hardware you can try it. Finally, here are some photos of my devices guts.
If you need to periodically run some job in OpenShift you have several options. Continue reading Cron jobs in OpenShift
If you are interrested in security devices this post may be for you. Recently I’ve found a software which makes a GPG security device out of a STM32. It’s called Gnuk. You just need a compatible board, programmer, flash the firmware and you are ready to go. I was just hoping to find some cheap device to flash to play with it.