Bitx40 CW homebrew

This month I completed the build of a 40m Bitx trx  to take along when on holiday. Output is 5 Watts.

I ordered mine here.

Apart from this you need also need a case.

There is a very active forum on this kit here.

The kit is SSB only, no CW. BUT Jerry – KE7ER – posted his CW mod in the forum so now mine can do CW as well. Thanks Jerry !

The VFO is made around an Arduino Nano and a Si5351A chip, the combo is called Raduino and ready to use.

The Raduino comes with v1.01 installed. On the forum Allard PE1NWL – posted  v1.09 in which he implemented

  • switch between VFO a and B,
  • use RIT,
  • switch between USB and LSB,
  • easily calibrate the VFO for both sidebands.

Thanks Allard !

I also installed an CW audio filter, i ordered this one

After building everything in the box, the unit received o.k. but had no output power.  Transistor Q13 turned out to be defective.

Luckily we have a small electronic parts shop here in Harderwijk with a great selection of all sort of components and a guy who knows his stuff, so a replacement transistor was no problem.





Teun the owner also had a retro handmike in his shopwindow.

For 2 euros you can’t go wrong…

After replacing the tranistor the output power was 5 Watts, enough for most european QSO’s.


All in all it was fun to assemble, and is fun to operate.

Hits: 1008

Ping sweep using command line

FOR /L %i in (1,1,255) do @ping -n 1 172.17.1.%i | find “TTL”

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\llu> FOR /L %i in (1,1,255) do @ping -n 1 172.17.1.%i | find “TTL”
Reply from bytes=32 time=1ms TTL=255
Reply from bytes=32 time=1ms TTL=255
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time=6ms TTL=128
Reply from bytes=32 time=10ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time<1ms TTL=128
Reply from bytes=32 time=1ms TTL=128
Reply from bytes=32 time=2ms TTL=128


Hits: 111

Certificate types PEM, DER, PKCS#7 and PKX(PKCS#12)

PEM Format
PEM is the most common format in which Certificate Authorities (CA) issue certificates. These are more widely used by Unix/Linux users.
If you see “Proc-type” present in a PEM format certificate it means that it is encrypted and these are called as base-64 encoded DER certificates.
The public part of the certificate will be represented in 
Whereas the private part of the certificate will be represented in  “—–BEGIN RSA PRIVATE KEY—–” and “—–END RSA PRIVATE KEY—–“.
PEM format can contain any or all of the client/server certificate, intermediate certificate, root CA and the private key.

  • They are Base64 encoded ASCII files
  • They have extensions such as .pem, .crt, .cer, .key
  • Apache and similar servers uses PEM format certificates

DER Format
DER is a Binary form of ASCII PEM format certificate. All types of Certificates & Private Keys can be encoded in DER format.
This format supports storage of single certificate and does not include private key for the intermediate/root CA.

  • They are Binary format files
  • They have extensions .cer and .der

DER is typically used in Java platform

This format contains only certificate or certificate chain but does not store the private key.
This format is usually used by CA’s to provide certificate chains to users.

PFX Format (PKCS#12)
PFX is a format for storing a server certificate or any intermediate certificate along with private key in one encrypted file. PFX follows Public Key Cryptography Standard(PKCS). The term PFX is used interchangeably with PKCS#12.

Hits: 172

Kerst Boodschap SAQ Grimeton

Elk jaar zend het Very Low Frequency station  in Grimeton Noorwegen een kerstboodschap uit.

Dit jaar kon ik hem niet zelf ontvangen maar wel opnemen van de WebSDR twente.

Klik hieronder om de opname af te spelen:

      saq xmas transmission

Hits: 62

Netscaler Bad performance

Today I looked into a Netscaler VPX Gateway with network issues.

Response was slow and users reported this error when connecting to Citrix backend servers:

“Failed with status 1110″ When Launching Desktops or Apps Through NetScaler Gateway”

I checked the eventlog on the vpx with: shell nsconmsg -K /var/nslog/newnslog -d event  and found a log full of these errors:

2546 245 PPE-0 UP; Last response: Success – Probe to STA server succeeded. Tue Oct 25 06:53:13 2016
2547 484 PPE-0 DOWN; Last response: Failure – TCP connection successful, but application timed out Tue Oct 25 07:01:19 2016

After looking around in the Systems menu I disabled Mac Based Forwarding and enabled TCP Window Scaling  as per CTX121149.

The network issued were gone and no more application time-out failures in the eventlog…

More about Mac Based Forwarding  here.



Hits: 318

Watchguard tcp dump options

About TCP Dump Argumentlogo-small

When you run the TCP dump task, you must specify the interface on which to run the task. You an also include expressions in the task arguments to filter for specific traffic.

To specify the interface, you include the -i argument and the interface name and number.

For example:

– i eth1 — Physical interface #1

-i ath1 — Wireless interface #1

-i br1 — Bridge interface #1

-i la1 — Link aggregation interface #1

To build an expression to filter the traffic from the interface you specify, you can use any of the standard TCP dump keywords and operators. Some of the common keywords and operators are:

host — Only include traffic to or from the specified host IP address.

net — Only show traffic to or from the IP addresses in the specified subnet. For example, for, type 10.0.1.

port — Only show traffic with either a source or destination of the specified port.

portrange — Only show traffic from the specified range of ports.

ip proto — Only show traffic from the specified protocol. For example, for ESP packets, type 50.

src or dst — Use with the keywords host or port to specify the source or destination.

tcp or udp — Use with the keywords port or portrange to specify the protocol.

and / or — Use to combine expressions.

For a complete list of the available keywords, see the PCAP-Filter manpage at

Examples of TCP dump arguments:

-i eth1 host and dst port 80
Show only traffic on interface eth1, to or from with destination port 80.

-i eth0 tcp port 25
Show only traffic on interface eth0, to or from TCP port 25.

-i vlan1024
Show only traffic tagged with VLAN 1024.

-i eth0 udp port 500 or ip proto 50
Show all UDP port 500 or ESP packets for the eth0 interface.

-i eth2 src and dst
Show all traffic from to on the eth2 interface.

Hits: 3549

HP A-Series comware cli

enter config mode:

show running-config:
disp cur

set ntp:
ntp-service enable
ntp-service unicast-peer

check ntp:
disp ntp-service stat

Clock status: synchronized
Clock stratum: 5
System peer:
Local mode: sym_active
Reference clock ID:
Leap indicator: 00
Clock jitter: 0.000198 s
Stability: 0.000 pps
Clock precision: 2^-17
Root delay: 6.37817 ms
Root dispersion: 6.54602 ms
Reference time: db84e749.fba8a28a Thu, Sep 15 2016 9:24:25.983

save config:
s s f (save safely force)

show saved-config:
disp sav

exit terminal:


more examples here

Hits: 255